Resource steal changes a hit from simple damage into an ownership transition. A fair implementation names the affected resource, caps the loss, creates each dropped unit once, keeps every pickup visible and attributable, and gives the player a reachable reclaim decision before the boss converts captured units into a declared benefit.
Kern marks a fixed 96-unit siphon at 0.30 s. Tavi clears the full radius before the 0.98 s resolve, so all six runes remain in the ledger and no pickup is created.
Autoplay is disabled by reduced motion. Scrub across 0.30, 0.86, 0.98, 1.82, 2.64, 3.08, 3.48, 3.90, 4.42, and 5.34 seconds to inspect avoidance, the bounded drop, reclaim, capture, benefit, and reset.
Define the eligible resource, loss formula and cap, protected minimum, pickup identities, spawn geometry, ownership transitions, reclaim and capture radii, expiry, boss benefit, pause and checkpoint behavior, co-op authority, and tests that conserve the ledger across simultaneous collection.
Choose one named resource and calculate requested loss separately from applied loss. Clamp against the current amount and any protected minimum, decide whether temporary, premium, quest, or accessibility resources are eligible, and emit one drop event only after authoritative contact.
Give each pickup a stable id and one owner state: player, world, boss, or expired. Define spawn clearance, magnetism, collection radius, simultaneous claims, latency reconciliation, and expiry so retries and duplicate collision callbacks cannot clone or erase value.
Declare the boss benefit before the race begins, cap its stacks or duration, and preserve a useful response when recovery is impossible. Test the final conservation equation, checkpoint restoration, phase transitions, death, disconnection, and collection on the same simulation tick.
An unexplained deduction reads as a bug or hidden tax. Trace the marked hit into a visible burst, preserve token identities, and show whether the value is reclaimable, destroyed, or already owned by the boss.
Losing a scarce resource, missing its reclaim window, and granting uncapped healing or damage can create a one-hit downward spiral. Bound each layer, provide a protected floor, and tune the race against ordinary movement rather than a mandatory mobility upgrade.
Record requested loss, applied loss, world pickups, reclaimed units, captured units, expired units, and the boss benefit revision. A simple conservation assertion catches duplicate pickups, late callbacks, save-load errors, and host migration disagreements.
Angles, distance, obstacles, hazards, magnet speed, and lifetime determine whether reclaim is a real choice. Place pickups so one ordinary route can recover something while collecting everything carries visible positional risk.
Track avoid rate, requested and applied loss, time to first reclaim, reclaim share, boss capture share, expired value, benefit uptime, deaths after loss, protected-floor activation, and repeated same-token claims.
The runes land as separate stones instead of vanishing into a number. Tavi grabs the nearest one, while two answer Kern's pull and orbit the elemental as a brief shield, turning ownership into a readable physical event.
Combine inventory slots, token shapes, trails, collection sounds, text, and controller feedback. Offer a smaller loss, protected minimum, longer lifetime, stronger player magnet, slower boss capture, automatic partial recovery, or a no-steal mode, and state those assists before combat.
Spending begins with the player's chosen action, while a resource drain may simply delete value. Resource steal creates an externally caused ownership event and may place value back into contestable space. If the boss benefits, that capture is a second explicit rule rather than an assumed consequence of damage.
Ultra Greed can make Isaac drop coins, then collect those same arena objects to heal. The shared pickup geometry turns one loss into a race: a coin remains legible as value while its eventual owner changes the encounter state.
Exception includes attacks that remove rings while the encounter also drains the shared ring timer. Because rings are both protection and time, the loss signal must distinguish a discrete boss hit from the steady global countdown.
Mark of Kaz'rogal drains mana on repeated ticks and detonates a target that cannot pay. The consequence depends on the authoritative resource ledger, so tick order, insufficient-resource handling, and party readability matter as much as the amount removed.
Found an inaccuracy or have a suggestion for this page? Propose an edit on GitHub