Loadout adaptation makes an encounter branch from equipment rather than ignore it. Kern reads one sword rune at a fixed snapshot: Reach selects a straight thrust; Burst selects a radial pulse. Tavi sees the copied mark before either threat commits and keeps an ordinary escape. Snapshot, mapping, feedback, and fallback must be explicit.

Open boss builder
Snapshot the reach runeAt 0.62 s Kern scans Tavi's equipped Reach rune. The copied arrow appears at 1.08 s, and a straight lane announces the selected thrust. Tavi begins a full-body sidestep before the package commits.
Compare two loadout snapshots and their deterministic boss packages A sword-bearing player carries an arrow-shaped reach rune, which a stone boss scans and copies before drawing a straight attack lane. The player sidesteps it. In a second test the equipped mark becomes a circle; the boss copies that circle and previews a radial pulse, while the player moves beyond its edge. Boss Player

At 0.62 s Kern scans Tavi's equipped Reach rune. The copied arrow appears at 1.08 s, and a straight lane announces the selected thrust. Tavi begins a full-body sidestep before the package commits.

Implementation checklist

Define the loadout snapshot, whitelist, package mapping, copied-state feedback, valid response, and reset rule.

Core checks

Three questions for the mechanic

  • What is sampled, and at which moment?

    Read a documented, narrow subset of the loadout at a stable boundary: arena entry, phase start, or an explicit scan. Kern samples only Tavi's equipped sword rune, not inventory order or hidden stats. Freeze the result through the package so menu changes and network updates cannot rewrite an attack already announced.

  • How does each loadout map to behavior?

    Use a finite table with a visible output. Reach always selects one previewed thrust lane; Burst always selects one previewed ring. Show the copied rune on Kern before wind-up, cap the package strength independently of item level, and provide a baseline for unknown or blacklisted equipment. Test identical snapshots for identical results.

  • Does every branch preserve a useful response?

    Adaptation should reshape the problem, not veto the player's build. Tavi can clear Reach laterally and Burst by moving beyond the radius with the same ordinary movement verb. Keep timings and geometry independently tunable, then compare the hardest valid loadouts so no branch removes all safe space or requires unequipping to proceed.

Design mistakes

  • The boss rereads equipment every frame

    Live reevaluation can swap hitboxes after their warning or react to a menu change mid-swing. Capture an immutable snapshot, display when it was taken, and delay any later equipment change until the next declared sampling point.

  • Adaptation becomes a hard counter

    If the boss simply becomes immune to the equipped build, player expression collapses into inventory punishment. Prefer a changed threat or bounded advantage with ordinary counterplay, and define exclusions for combinations that would heal, loop, or make the boss untouchable.

Tuning

Tune the attack

  • Drive the branch from data

    Map normalized loadout tags to package ids in one table. Animation, AI selection, damage geometry, copied icon, accessibility text, and tests should consume the same resolved id rather than repeat conditionals with different answers.

  • Separate snapshot from execution

    The scan resolves first, then Kern signals and executes the chosen package. Log snapshot time, accepted tags, selected package, and reset time so a replay can reproduce the branch without inspecting the player's current inventory.

  • Define a safe baseline

    Empty, unknown, DLC, disabled, or multiplayer-mixed loadouts need a deterministic default. The baseline must still have a readable response and should not be stronger than a recognized package merely because content data was missing.

  • Test combinations, not only items

    Cover duplicate tags, two equipped weapons, hot-swaps at the snapshot frame, consumables, summons, copied cooldowns, multiplayer ownership, save migration, rollback, phase transition, death, and a loadout that contains only blacklisted effects.

Arena

  • A stone archive that learns one rune

    Kern needs only a thin scan beam and one copied glyph above the chest. An arrow becomes a long straight lane; a circle becomes a floor pulse. The same stone body and two simple marks make the selected branch readable without recreating the player's entire inventory.

Player upgrades

  • Honor Tavi's chosen sword rune

    Both test runs use the sword Tavi already carries. The rune changes Kern's package but never disables the sword or demands a menu exploit. Games with larger inventories can normalize many items into a few encounter tags while preserving the player's chosen identity.

Do not confuse this with

  • A loadout-derived branch, not resistance alone

    Damage-type resistance changes the amount received from an attack type. Absorption converts eligible input into a resource. Loadout adaptation takes a declared equipment snapshot and selects a broader behavior package that may change attacks, defenses, or available states while retaining explicit counterplay.

Bosses that use this mechanic

Learn more

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