Part break

Three questions for the mechanic

• Which attack belongs to the part?

  Give the launcher its own break state and make the beam depend on that state. Before 2.88 s, its 1.95–2.20 s shot is dangerous across the marked lane. At 3.78 s the same firing pose must not produce a beam, even though Kern and other attacks could remain active.

• Can an ordinary hit reach it?

  The component needs a readable silhouette, independent hit area, and a post-shot opening within Tavi's sword reach. Show the cut at 2.88 s, detach the complete launcher, and stop accepting hits on its empty mount. Test short-range and slower builds before requiring a special attack.

• How does the new state persist?

  Let the broken state last through a visible attempted repeat so the player can verify the consequence. This loop deliberately reassembles the launcher at 5.35 s; a real encounter may keep it gone for the rest of the fight. If repair exists, show it before attack permission returns.

Design mistakes

• The part breaks but its attack still happens

  Removing art while leaving the beam in the attack table contradicts the rule. Drive spawning and hit detection from the same attached-state flag as the visible component.

• A hidden repair restores the danger

  A beam from an empty mount feels like a bug. If the part can return, animate the reattachment and delay attack permission until that motion is complete.

Tune the attack

• Separate part health from boss health

  Define whether damage to the launcher also damages Kern. The illustrated cut disables one attack; it does not require the boss to become globally vulnerable or lose a fixed percentage of health.

• Preserve a useful fight

  Removing a weapon should alter the decision space, not erase every threat. Keep another legible attack or movement response after the break, and retune pacing so the remaining encounter is neither trivial nor stalled.

• Audit every state transition

  Test the final frame before the 2.88-second break, the first frame after it, the 3.78-second attempted shot, and the 5.35-second repair. The sprite, effect, damage check, and audio cue must switch together.

• Escalate by component choice

  Later, two breakable weapons can offer different reductions in pressure. Reveal what each part controls, prevent simultaneous target clutter, and decide whether players may ignore every optional break.

Arena

• An arm that loses its weapon

  The launcher's bright rune and beam share one visual motif. The loose plate lands on the arena floor instead of vanishing, while the exposed mount remains on Kern's arm. A tiny failed spark at the second firing pose makes the disabled attack observable without replaying a dangerous beam.

Player upgrades

• Support the established attack verbs

  Place a required part within the reach and timing of the player's ordinary kit, or expose it through a known movement route. Ranged attacks may break it earlier, but should not be the only unannounced solution. In a multiplayer or build-diverse game, decide who owns the detached loot and whether damage from different types contributes equally to part health.

Do not confuse this with

• A broken part changes capability

  A weak point changes damage by hit location; it need not remove an attack. Situational immunity changes whether body hits work under a condition. Here the boss remains hittable throughout, but an independent arm component is removed and its beam cannot fire until the part is repaired.