A debuff handoff assigns one harmful state to one player and lets it move to another through an explicit contact rule. A visible owner and countdown make the deadline legible; a reachable pass and brief return immunity prevent both unavoidable damage and accidental ping-pong.

Open boss builder
Mark the first carrierAt 0.70 seconds the boss applies one volatile rune to player 1. Its three-second countdown starts; without a pass it would burst at 3.70 seconds for 80 damage.
Pass a volatile rune between two players The boss marks player 1 with one ticking rune. Two players walk together and the rune visibly moves to player 2 at contact. They separate, then meet again after temporary return immunity ends, passing the rune back before expiry. The countdown restarts on each valid pass and an explicit retry clears the state. Player 1Player 2 Boss Player

At 0.70 seconds the boss applies one volatile rune to player 1. Its three-second countdown starts; without a pass it would burst at 3.70 seconds for 80 damage.

Implementation checklist

Specify acquisition, exclusive ownership, transfer radius, timing, duration reset, return immunity, expiry damage, invalid recipients, and authoritative event IDs.

Core checks

Three questions for the mechanic

  • What owns the effect?

    Give the debuff one stable owner ID, one expiry timestamp, and an explicit acquisition event. Display the owner and remaining time in a way that can be read without color. Define whether the boss can retarget, copy, cleanse, or reapply the state; none of those happen in this demo.

  • When is contact a valid pass?

    Here the two player anchors must be within 76 scene units, both alive, the receiver not immune, and the source still before expiry. Resolve ownership atomically once per transfer ID. A pass restarts the three-second timer and protects the former carrier from receiving the rune for one second.

  • What happens at the deadline?

    A missed pass deals 80 damage to the current owner once, not to everyone in range. Test early contact, a second collision during immunity, duplicate callbacks, dead or absent recipients, simultaneous contacts, late passes, and reset. Log owner and expiry before and after each event.

Design mistakes

  • Letting touch immediately bounce the state back

    Continuous overlap may produce many contact callbacks. Apply return immunity and deduplicate event IDs so a single meeting creates exactly one ownership change.

  • Resetting the clock without changing owner

    A timer reset on any collision hides failed handoffs. Confirm a legal receiver and commit the owner change before restarting the countdown; otherwise preserve the old deadline.

Tuning

Tune the attack

  • Budget normal movement

    Tune countdown, arena spacing, movement speed, collision radius, and post-pass separation together. The route should work without a hidden dash or invulnerability requirement.

  • Make ownership unambiguous

    Use one rune glyph attached to the current carrier, a numeric countdown, and a short transfer streak. The old carrier's immunity ring should look different from the live debuff.

  • Test event authority

    Record encounter ID, pass ID, source, receiver, positions at contact, expiry before and after, immunity until, and result. Replaying or seeking a frame must not add extra passes or damage.

Arena

  • A rune that must keep moving

    The boss sends a single volatile rune toward the first player. Two players cross a small gap to exchange it, step apart while the old carrier is protected, then meet for a deliberate return pass before the new deadline.

Player upgrades

  • Keep the route and exclusions readable

    The same rule can use touch, a directed cast, or a marked tile, but the selected transfer range and excluded receivers must be explicit. In this contact variant, ordinary walking reaches both exchanges with time to separate.

Do not confuse this with

  • Passing a state is not splitting damage

    Only one player carries the live rune at a time; proximity changes ownership rather than making both players share one hit. A tank swap instead changes who the boss targets with future attacks, while a handoff moves a timed status itself.

Bosses that use this mechanic

Learn more

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