Pulse beam

Three questions for the mechanic

• Can the lane and rhythm be read before the first pulse?

  Show both endpoints, the complete width, pulse count, on time, off time, and first activation together. Use a countdown, repeated flashes, or audio beats that share the same phase as collision.

• Does the beam truly switch off between pulses?

  Drive light, sound, damage, and collision from one pulse schedule. A dim or absent beam must not retain a hidden damaging segment, and each new pulse must occupy the lane that was announced.

• Can the intended response finish inside a pause?

  Measure the player’s full body across the complete lane, including acceleration and input latency. Leave enough inactive time to cross, block, or reposition without requiring an unstated dash or invulnerability window.

Design mistakes

• The rhythm starts before it can be learned

  An immediate first pulse turns cadence into a reaction check. Preview at least one complete beat or provide a distinct start cue before collision activates.

• The visual pause is still dangerous

  Lingering collision during a dark beat breaks the mechanic’s central promise. End damage on the same frame the active beam disappears, apart from any separately signalled aftereffect.

• Every pulse silently changes the lane

  Retargeting between beats converts a rhythm problem into repeated aim tracking. Lock the lane for the sequence or telegraph each changed lane as a new commitment.

Tune the attack

• Store one pulse schedule

  Represent lane endpoints, width, start time, pulse count, on duration, off duration, and recovery once. Derive animation, audio, collision, and UI timing from that shared state.

• Test cadence at gameplay speed

  A readable still frame does not prove the rhythm works. Record earliest and latest safe crossing times, then test them at target frame rate, camera distance, and input latency.

• Preserve phase across feedback channels

  Light peaks, sound accents, controller feedback, and damage should identify the same active beat. Offset feedback creates false early or late openings even when each channel looks polished alone.

• Escalate one timing variable at a time

  Later variants can add a pulse, shorten pauses, or alternate two lanes. Keep the learned cadence or clearly introduce a new one instead of changing count, phase, and geometry simultaneously.

Arena

• What the mechanic communicates

  The repeated discharge makes Kern feel like a runic machine that stores and releases energy in deliberate cycles. Tavi reads that machine-like cadence and turns a dangerous line into a timed crossing.

Player upgrades

• Adapt it to the player verbs

  Basic movement needs a pause long enough to cross the beam width. A dash can support shorter gaps, while block, reflect, or phase abilities may answer an active pulse; state whether those verbs stop one beat or the whole sequence.

Do not confuse this with

• Keep the mechanic distinct

  A pulse beam alternates active and inactive states on one committed lane. A straight beam is one continuous emission, a scanning beam moves its lane across the arena, and rotating beams continuously change angle. Preserve the fixed lane and readable cadence.