Threat generator

Three questions for the mechanic

• Can the source be identified before the first emission?

  Show where the node lands, that it persists, its warm-up, and the paths it can fill. A placement cue is not a damaging hitbox; distinguish it from the flying motes.

• Does the cadence leave a reachable route?

  Measure ordinary travel from the worst legal start to a corridor clear of every path, including the full player radius. Test the first release and all later overlapping motes, not merely the first shot.

• What ends production and clears the arena?

  Set a finite release count or lifetime, a maximum number of live threats, and a cleanup rule for timeout, destruction, and phase change. Remove hitboxes when their visible motes expire.

Design mistakes

• An unannounced source begins firing

  A new object and a new projectile arrive on the same frame, leaving no time to read their relationship. Give placement and warm-up separate beats.

• The generator floods every exit

  Repeating a fair shot can create an unfair overlap. Simulate the maximum live count and check the whole-body route through every release.

• Threats outlive their visible cause

  If the node disappears but keeps spawning, or a faded mote still collides, the visual rule breaks. Tie rendering, collision, and cleanup to the same state.

Tune the attack

• Model the source and emissions separately

  Store the node's socket, activation delay, interval, count, lifetime, and optional health. Give each emitted object its own origin, velocity, radius, and expiry; never infer damage from the node graphic alone.

• Budget simultaneous threats

  Calculate how many motes can coexist from interval and flight time, then cap that count. Check whether their swept discs intersect every ordinary escape route, including movement during a later boss attack.

• Make cancellation explicit

  In this demonstration the source expires after three emissions and the remaining motes finish their flights. If the player can destroy it, decide whether existing motes persist, vanish, or change path, and signal that rule.

• Escalate one budget at a time

  Increase release count, shorten interval, or vary paths only while the new schedule stays learnable. A moving or independently aiming source requires its own cue and clearance test.

Arena

• What the mechanic communicates

  Kern fixes a small rune stone into the arena. It glows before each emission, sends out three separate sparks, then goes dark; the quiet interval belongs to Kern's recovery.

Player upgrades

• Adapt it to the player verbs

  Ordinary movement is enough to leave the shown trajectories. A sword strike could optionally break a reachable node, but test approach time, range, source health, and what happens to motes already in flight; that shortcut is not required here.

Do not confuse this with

• Keep the mechanic distinct

  A generator's defining rule is repeated creation of independent threats. A turret is a fixed attacker whose firing direction is the main problem; a summon introduces another combatant; a lingering hazard is one area that stays active rather than new objects appearing over time.