Chain explosions

Three questions for the mechanic

• Can the player read the whole order before the first blast?

  Show every center, full radius, propagation direction, interval, and first ignition. Numbering, a traveling rune, or staged audio can express order, but all channels must agree with the collision schedule.

• Does collision move with the visible detonation?

  Drive light, sound, damage, and hit testing from one active-node index. An upcoming marker must not hurt early, and a dark completed node must not retain an invisible damaging circle.

• Is the wake a reliable response space?

  Test the player’s full body, acceleration, and input latency between adjacent radii. Keep enough separation or delay for the intended movement verb to enter the previous node before the chain catches it.

Design mistakes

• The order is revealed one explosion at a time

  Late markers turn a route-reading problem into repeated surprise reactions. Preview the complete chain or clearly declare that later branches are a different mechanic.

• Several invisible nodes remain dangerous

  Hidden overlap makes the safe wake dishonest. If two blasts intentionally overlap, show both active volumes and test the resulting gap with the player’s full body.

• The chain outruns every supported response

  A visually clear sequence can still be impossible. Tune interval, spacing, and radius against ordinary movement before offering dash-only or invulnerability-based variants.

Tune the attack

• Store the chain as ordered nodes

  Give each node a center, radius, start offset, active duration, and completion state. Derive the preview path, current blast, collision, audio, and recovery from that single list.

• Separate travel rhythm from blast duration

  The interval controls how quickly danger advances; active duration controls overlap. Tune them independently so cadence can accelerate without silently widening the dangerous footprint.

• Test every handoff

  Measure the route from node zero to one as carefully as the final transition. Camera framing, arena edges, or another mechanic may invalidate a handoff that is safe in isolation.

• Escalate by reshaping the route

  Later variants can bend, fork, reverse, or accelerate a learned chain. Change one property at a time and announce any branch before the player commits to following the wake.

Arena

• What the mechanic communicates

  Kern appears to pass runic force from stone to stone, making the arena behave like a deliberate fuse. Tavi survives by reading that transfer and stepping into the cooling wake.

Player upgrades

• Adapt it to the player verbs

  Basic movement needs generous spacing and intervals. A dash permits tighter handoffs, while block, parry, or teleport can interrupt or skip a node; state whether that response affects one blast or the remaining chain.

Do not confuse this with

• Keep the mechanic distinct

  Chain explosions are discrete zones with a committed order. A marked-area strike resolves one zone, a shockwave moves as one continuous front, and a mine waits as a persistent triggerable object. Preserve the ordered handoff between separate blasts.