Kern marks one lane, locks its direction, then releases three rune bolts at separate instants. Tavi clears it with ordinary movement and stays out until the third passes. Each bolt has its own travelling hitbox; the dotted guide does no damage. The last bolt's exit ends the response and starts recovery.

Open boss builder
Mark the laneKern raises the emitter and draws a dotted, harmless guide along the future lane. The direction locks before any bolt is released.
Count the three releases Kern marks a fixed diagonal lane, then fires three separate rune bolts along it. Tavi moves sideways before the first arrives, waits outside the lane until the third exits, and returns after recovery. Boss Player

Kern raises the emitter and draws a dotted, harmless guide along the future lane. The direction locks before any bolt is released.

Implementation checklist

Tune the tell, lock, release spacing, projectile speed, full-body clearance, and opening after the last shot.

Core checks

Three questions for the mechanic

  • What announces the whole burst?

    Show the emitter and the shared lane before the first release. Use a distinct lock cue so later bolts cannot silently retarget. A dotted guide is informational, not a damage region.

  • Can every shot be counted?

    Give each bolt a visible origin, release pulse, spacing, travel, and collision circle. Keep the interval long enough to read separate shots but short enough that they form one attack.

  • When is it safe to return?

    Measure the player's complete collision shape against every active bolt. Make sideways clearance possible before the first arrival, and keep the opening closed until the final bolt has passed.

Design mistakes

  • Three shots appear simultaneously

    If all bolts spawn together, the mechanic reads as a volley or spread. Release times, recoil, and audio beats must be separate.

  • A later shot secretly re-aims

    A shared fixed-lane tell becomes false if the second or third bolt follows Tavi. Retargeting can be a valid variant, but it needs a new cue and a different response budget.

  • Recovery starts after the first bolt

    Tavi may re-enter a lane that still contains the next shot. Track all live projectiles and begin the useful opening only after the final one clears.

Tuning

Tune the attack

  • Expose cadence as a parameter

    Store release count, intervals, velocity, bolt radius, and flight lifetime separately. A faster cadence changes overlap and available movement time even if the aiming rule stays fixed.

  • Test the complete route

    Check slow movement, nearby walls, starting near the lane edge, and an early return. Collision uses every bolt's radius plus the player radius, not the center of a decorative trail.

  • Keep the source legible

    Attach each release to Kern's visible emitter and pulse the pose once per shot. Do not let a visual trail or guide imply an extra damaging surface.

Arena

  • What the mechanic communicates

    Kern's rune socket charges once and spits three stones in rhythm. The repeated source makes the count learnable; Tavi's sideways movement makes the persistent lane clear.

Player upgrades

  • Adapt it to the player verbs

    Ordinary lateral movement must clear the first bolt and sustain safety through the third. A dash may shorten the route, while a guard can be an alternate response if it has a clear cost; neither is silently required.

Do not confuse this with

  • Keep the mechanic distinct

    A single shot has one release. A volley launches several projectiles together. Burst fire spaces multiple releases over time from one announced source; this example does not re-aim between them.

Bosses that use this mechanic

Learn more

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