A loadout mirror reads chosen weapons, spells, items, stats, or deck entries at one explicit moment, then gives the boss a deterministic package derived from that snapshot. It reflects player expression without requiring the boss to execute arbitrary inventory data live.
From 0.32 to 1.14 seconds, three lines connect Tavi’s sword, ward, and ember slots to Kern. The capture happens once at 1.14 seconds under one stable snapshot id.
Autoplay is disabled by reduced motion. Scrub across 0.32, 1.14, 2.18, 2.62, 3.42, 4.12, 5.28, and 5.42 seconds to inspect the snapshot.
Define the snapshot trigger, eligible slots, canonical ids, copied values, normalization, invalid-item fallback, multiplayer owner, post-snapshot changes, phase lifetime, save and rollback behavior, telegraph, counterplay, and telemetry.
List eligible slots and canonical ids: weapon family, upgrade tier, spell tags, item charges, passives, stats, or deck entries. Exclude presentation-only data and define a safe authored fallback for every unsupported or empty value.
Map snapshot data to a bounded package instead of executing arbitrary player content directly. Normalize damage, range, cooldowns, status strength, resources, and animation requirements so every accepted combination remains readable and fair.
Choose one capture event and one lifetime: encounter entry, transformation, summon, or phase start. Give it a stable id, deep-copy the values, ignore duplicate callbacks, and explicitly decide whether loadout changes, death, multiplayer handoff, reload, or rollback can replace it.
If the boss copies raw power once and the player can immediately re-equip, preparation collapses into inventory cheese. Lock loadout changes briefly, normalize the copy, preview the captured package, or make every supported build create useful counterplay.
Polling current equipment during attacks creates races, animation gaps, multiplayer disagreement, and save-state bugs. Resolve attacks from an immutable snapshot and treat a resnapshot as a new, clearly signaled event.
Translate canonical tags such as heavy, ranged, guard, fire, or healing into tested boss actions. Never assume a player animation, projectile, item script, or resource model is safe to reuse as boss logic.
Show the selected slots before capture, confirm the lock with a distinct cue, and keep the copied package visible when practical. Players should be able to connect a later boss action to the build choice that produced it.
Record snapshotId, ownerId, eligible input ids, normalized output ids, capture count, rejected values, fallback use, resnapshot count, phase, and the id of every copied action. Test empty, duplicated, modded, disabled, networked, and restored inventories.
A pale scan crosses Tavi’s sword, ward, and ember charm. Kern carves those three signs into stone; even after Tavi reaches for a new kit, the elemental swings with the pattern it already learned.
Provide a pre-fight summary of eligible slots, an icon for the captured package, color-independent slot shapes, and an option that maps builds to a small fixed set. Avoid reaction-time pressure during inventory changes and announce any intentional resnapshot.
Loadout adaptation selects a counter package after classifying the player, while a loadout mirror preserves selected input from the player’s build. A player-controlled boss transfers agency; this mechanic transfers bounded data.
From 0:13, the silver tear assumes the player’s form and fights with the captured equipment and abilities. The example makes the snapshot highly personal, but also exposes the need to define how entry-time equipment and later changes are handled.
At 36:46, Doppelganger appears with the copied character package. Its documented room-entry equipment snapshot can be manipulated by unequipping first and re-equipping afterward, a clear warning about snapshot timing and degenerate preparation.
From 2:10, Pinocchio’s copied combat pages are visible in the deck-driven battle. Copying a librarian’s bookshelf demonstrates that the mirrored payload can be a set of authored actions rather than physical weapons or character stats.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub