Kill-order inheritance turns target choice into a phase-design decision. Each boss has an identity and an authored successor package. When one falls, the survivor receives a readable transfer and commits to a different move. The player must be able to infer the branch before its new threat becomes active.
Tavi strikes the left body at 1.05 seconds. Its rune crosses to the surviving right body from 1.25 to 1.58, authorizing a stone wave rather than quietly adding damage. The wave is signaled before release.
Reduced motion disables autoplay. Scrub through 0.40, 1.05, 1.40, 1.80, 2.20, 2.75, 3.15, 3.65, 4.00, 4.30, 4.75, 5.20, and 5.80 seconds.
Define pair identities, first-defeat authority, both possible packages, inheritance timing, new telegraphs and hit geometry, health policy, simultaneous-defeat tie handling, one-grant limit, victory conditions, retry reset, accessibility, and branch telemetry.
Give the two bodies stable identities and record the first authoritative defeat, not the first hit or a visual death animation. Map each possible survivor to a named attack package. Resolve same-frame defeats deliberately; if both die, finish the pair rather than inheriting from a nonexistent survivor.
Draw a transfer from the fallen source to the living recipient, then give the recipient a distinct anticipation pose and threat preview. Do not make the move active during the transfer. Derive its collision from the shown wave ring or lance lane and include the player's entire body in clearance tests.
Grant exactly one package per pair and attempt ID. Clear pending transfers and the selected package on retry; keep completion separate from inheritance. Test both orders with low- and high-damage builds, simultaneous kills, repeated events, reconnects, and a player standing at each proposed safe route.
A hidden multiplier makes target order feel like a trap. Give each survivor a visibly different move shape, signal, response and recovery, and show why the fallen body's rune matters.
If both defeat callbacks race, both packages can be applied or victory can be delayed. Use stable boss and attempt IDs, define same-frame priority, make the grant idempotent, and cancel pending transfer when the pair is truly finished.
Compare total time, damage exposure, arena space, healing opportunity, and learning load on each branch. Different is more useful than simply easy versus hard; both paths should be viable without a required build.
Keep the fallen body, recipient, and rune path on screen long enough to read. Start the warning after the transfer; an inherited beam must not hit a player before its lane is visible. Use shape and pose as well as color and sound.
Record source, survivor, package, attempt, grant count, and final outcome. Reproduce either branch by seeking, reset to the same baseline, and test a simultaneous defeat and duplicate network event without carrying an old package forward.
When Tavi fells the left echo, its round seal enters Kern and a wave rolls across the floor. The covenant rewinds for a second trial. When Kern falls first, his sharp seal moves to the echo, which draws a straight rune lance instead.
Avoid a branch that demands a particular damage type or travel speed. Give equivalent audio, text and shape cues, a visible safe route for the whole player body, and an explicit retry marker before showing the opposite order.
Enrage usually scales one actor after a threshold. Kill-order inheritance maps the fallen actor's identity to a specific successor package. A related order-conditioned reaction can change the survivor without literally transferring a power; label that variant clearly.
In this 2D turn-based pair, Chubs enrages if Nubs dies first, while Nubs prepares a one-turn Nuke after Chubs dies first. This is an order-conditioned survivor reaction, not literal power absorption; the two outcomes still show why branch signaling matters.
Defeating either member selects the other for a second phase. Ornstein takes Smough's power and grows if Smough falls first; Smough imbues his hammer with Ornstein's lightning if Ornstein falls first. The transition makes the chosen order explicit.
After both first-phase demons fall, the one slain last returns as the Demon Prince. Which one fell last determines whether the prince receives a meteor or laser special attack, so the ordered identities select the final move package.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub