Action-reactive punish

Three questions for the mechanic

• Which player actions may start a response?

  Use a small explicit eligibility table—heal, item, cast, summon, reload, or another committed verb—and listen to an authoritative action-started event after the animation and cost are accepted. Do not infer intent from raw input, a menu selection, or a queued command that has not entered gameplay state.

• When is the boss allowed to answer?

  Gate the response by boss state, distance, line of sight, phase, cooldown, priority, and one response id per action id. Snapshot the target at a readable commit point, then let movement, cancellation, interruption, cover, or another taught verb resolve the threat under normal combat rules.

• Where is the guaranteed safe opportunity?

  Mark recoveries, staggers, transitions, cover states, or limited-range positions where the response cannot begin. Test that every eligible action has at least one practical window and that the counter cannot pre-empt, cancel, or chain out of the boss animation that was meant to create it.

Design mistakes

• The boss responds before the action is visible

  Reacting on button press or command queue makes the boss appear to know a decision the world has not shown. Observe accepted gameplay state, add a distinct response tell, and keep target tracking rules consistent with comparable attacks.

• Every opening is secretly unsafe

  If the response ignores recovery, stagger, cooldown, range, or line of sight, the intended resource action becomes a trap rather than a timing decision. Protect authored windows in encounter logic and add regression tests for them.

Tune the attack

• Make the causal chain inspectable

  Name actionId, actionType, observedAt, responseId, responseType, availability result, rejection reason, target snapshot, cooldown start, and resolution. This turns a suspicious-feeling behavior into a sequence designers and players can reason about.

• Tune pressure, not guaranteed damage

  The response can force a cancel, delay completion, spend space, or demand a quick defense without being unavoidable. Its tell and travel time should be tested from the latest practical cancel frame, not only from idle movement.

• Instrument denied and protected actions

  Record eligible action attempts, accepted responses, rejection reasons, action completion, cancel frame, player position, hit or avoidance result, response latency, cooldown, boss state, safe-window success, duplicate events, rollback, reload, and abandonment after repeated denials.

Arena

• Kern reads the spell, not Tavi’s hands on the controls

  When Tavi raises the healing rune in open ground, Kern’s chest mark echoes it, fixes a point on the floor, and launches a stone dart. Later, Kern’s arms are still buried after a heavy swing; the same rune appears over Tavi, but Kern’s crossed response mark stays dark until recovery ends.

Player upgrades

• Expose trigger, lock, and safe window

  Use a distinct sound and shape for the observed action, response queue, and target lock; preserve them without flashes or camera shake. Offer longer response lead, a clearer cooldown cue, stable subtitles, generous cancellation, and at least one low-execution safe window.

Do not confuse this with

• A conditional response, not prediction or a passive aura

  Predictive aim estimates future position from movement. Counter stance answers contact during an advertised defensive state. Action-reactive punish starts a selected attack because an eligible player action entered committed state, so its central contract is when that event may be observed and answered.