Moveset shapeshifting replaces the boss’s whole active package with another authored package: locomotion, targeting, attacks, reactions, and recovery change together. Clear transition rules let one encounter revisit learned opponents without becoming an unreadable bag of moves.

Open boss builder
Commit the colossus packageThe colossus package signals a heavy stance, releases one expanding slam from 0.55 to 1.35 seconds, and completes its own recovery before transformation.
Follow three complete packages through two explicit transformations Kern completes a radial colossus attack, transforms into a long-lane serpent package, then transforms again into an oracle package that releases a three-way fan. Boss Player

The colossus package signals a heavy stance, releases one expanding slam from 0.55 to 1.35 seconds, and completes its own recovery before transformation.

Implementation checklist

Define each form’s package id, entry and exit conditions, transition cue, minimum tenure, attack eligibility, geometry, movement, vulnerabilities, cooldown ownership, shared health and status, deterministic sequence, rollback, and telemetry.

Core checks

Three questions for the mechanic

  • What belongs to one moveset package?

    Treat locomotion, target selection, attacks, hit reactions, hurtboxes, vulnerabilities, effects, and recovery as one versioned contract. A form may share health and status with the encounter, but it should not inherit incompatible local timers or animation state.

  • How is a transformation scheduled?

    Choose deterministic conditions such as elapsed tenure, health bands, a fixed sequence, or an authored weighted table. Finish or cancel the outgoing action explicitly, signal the handoff, then enable the next package only after its rig, collision, and cues are ready.

  • What persists across forms?

    Classify every value as encounter-wide or form-local. Preserve health, progression, ownership, and approved status effects; reset or translate cooldowns, targets, spawned entities, weak points, and pending events according to a documented handoff table.

Design mistakes

  • The boss shuffles signature attacks without form identity

    A random attack salad removes the learned relationship between pose, movement, geometry, and response. Keep a package active long enough to read and practice, and reserve cross-package combinations for explicitly authored exceptions.

  • A hidden handoff leaks the previous form’s state

    Old hitboxes, projectiles, targets, or cooldown callbacks can fire after the new rig appears. Give every transition an id, cancel or transfer owned events once, and test backward seeking, latency, death, interruption, reload, and rollback at both boundaries.

Tuning

Tune the attack

  • Give every form an entry, active loop, and exit

    A package is more than an attack list. Specify its entry pose, movement model, legal actions, signature pressure, recovery cadence, exit lock, and fallback if an animation or target is unavailable.

  • Keep shared state deliberately small

    One health bar and encounter progress can make the transformations feel like the same boss. Local cooldowns and entities usually belong to their package; translating everything across forms creates invisible dependencies and balance surprises.

  • Measure the sequence as well as each form

    Record formId, packageVersion, transitionId, reason, tenure, entry and exit time, action ids, canceled events, carried statuses, damage taken per form, repeat frequency, and failures to reach a valid recovery before handoff.

Arena

  • Kern turns one rune body into three remembered foes

    The elemental widens into a colossus for a stone-shaking slam, uncoils into a serpent’s lane, then raises an oracle crown and casts three rays. Each silhouette completes its own rhythm before the next rune takes hold.

Player upgrades

  • Reduce the form set without breaking the contract

    Offer a fixed sequence, longer minimum tenure, stronger transition cues, persistent form icons, and an option that removes one package. Announce geometry through shape, sound, text alternatives, and haptics rather than color alone.

Do not confuse this with

  • Whole-package replacement, not an ordinary phase or copied loadout

    A phase can change encounter goals while keeping the same action system. Shapeshifting replaces the active moveset contract itself. A loadout mirror derives a package from player data; this mechanic selects complete authored packages, often borrowed from other opponents.

Bosses that use this mechanic

Learn more

Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub