Status buildup separates exposure from consequence. Each qualifying contact adds to a readable gauge, safe time may let that value decay, and the authored effect is applied exactly once when the threshold is crossed, creating a risk decision before ordinary damage, control loss, or defeat occurs.

Open boss builder
Apply partial buildup, then show delayed decayTavi enters Kern's radial field and receives 38 buildup at 0.72 s. Leaving the field stops new exposure, but the gauge holds until its 1.08 s decay delay and then falls to 14 by 1.72 s, making the grace period and recovery rate separately visible.
Enter Kern's rune field, let one exposure decay, then cross the threshold Four rune stones anchor Kern’s filled exposure field while Tavi enters and leaves it. The solid gauge above the arena rises after contact, partly decays away from the field, then reaches its threshold on two further contacts. Stone shackles appear beside Tavi for one status effect. When the gauge clears, a solid shield beside Tavi marks brief immunity and blocks another contact. Boss Player

Tavi enters Kern's radial field and receives 38 buildup at 0.72 s. Leaving the field stops new exposure, but the gauge holds until its 1.08 s decay delay and then falls to 14 by 1.72 s, making the grace period and recovery rate separately visible.

Implementation checklist

Define which contacts add buildup, the per-source amount, threshold, decay delay and rate, effect payload and duration, cleansing rules, resistance scaling, reapplication immunity, stacking ownership, UI priority, and the tests that keep buildup, effect, and ordinary health damage from becoming one ambiguous system.

Core checks

Three questions for the mechanic

  • What accumulates, and what does not happen before the threshold?

    Give every source a stable status id and explicit buildup amount. Decide whether blocks, invulnerability, shields, weak hits, overlapping zones, or repeated ticks contribute. Keep partial buildup free of the final payload unless a separate escalating-warning rule is intentional; otherwise the gauge lies about when the consequence begins.

  • How can the player manage the gauge before it fills?

    Tune the delay before decay, decay per second, cleansing cost, resistance modifier, and safe-space availability together. Test one isolated contact, a planned combo, overlapping sources, and the slowest legal movement speed. The player needs enough signal to decide whether to leave, cleanse, guard, or accept the risk.

  • What exactly happens on crossing, clearing, and reapplication?

    Use one authoritative threshold comparison and reserve one effect id when it crosses. Specify whether excess buildup is discarded, carried, or converted; when the gauge clears; whether the effect can refresh; and how long immunity lasts. Test simultaneous final hits, cleanse-on-crossing, phase changes, death, rollback, and repeated network messages.

Design mistakes

  • The gauge looks full before the effect is authoritative

    Rounding, delayed replication, or a decorative animation can show 100 while the server still considers the target below threshold. Derive fill, threshold flash, effect event, and accessibility announcement from the same resolved value and sequence number.

  • Decay and immunity are invisible exceptions

    If buildup pauses, falls, clears, or ignores a new hit without a distinct cue, the system appears inconsistent. Expose delay, direction, cleansing, resistance, and immunity separately, and log the reason every contribution was applied, reduced, or rejected.

Tuning

Tune the attack

  • Separate buildup from the applied effect

    Store current buildup, last exposure time, threshold, effect state, effect timer, and immunity timer as separate fields. The gauge may decay while no effect exists; the active effect may continue while buildup is already zero. This boundary prevents accidental refreshes and supports clear telemetry.

  • Balance frequency, amount, and recovery as one rhythm

    A small amount from a rapid source can be more demanding than one large, slow pulse because it repeatedly postpones decay. Measure time to threshold under intended and worst-case overlap, time needed to recover after one mistake, safe uptime lost, and how resistance changes those values.

  • Choose an effect proportional to avoidability

    A hard stun or instant defeat needs stronger advance information, more reliable counterplay, and safer overlap rules than a brief damage-over-time effect. Scale consequence with field coverage, source tracking, contact frequency, arena constraints, and the cost of cleansing rather than with theme alone.

  • Make ownership and stacking deterministic

    For multiple bosses, summons, hazards, or players, decide whether contributions share one gauge, create separate gauges, or select a dominant source. Resolve simultaneous threshold crossings once, preserve the credited source, and keep co-op UI and rollback from applying duplicate effects.

Arena

  • Runes stain the sword before they bind its bearer

    Kern's first pulse leaves a few glowing marks on Tavi's gauge, and retreat lets them fade. Returning too soon lets two later pulses complete the rune pattern. Only then do the shards close around Tavi, making accumulation, threshold, and consequence three readable story beats.

Player upgrades

  • Offer redundant warning and adjustable recovery

    Pair the gauge with shape, icon, sound, caption, and controller feedback at important bands. Allow larger UI, reduced flashes, independent effect audio, and a clear numeric or segmented alternative. Difficulty options may increase decay, reduce buildup, lengthen immunity, or automate cleansing without hiding the underlying rule.

Do not confuse this with

  • A thresholded secondary state, not ordinary health or a posture break

    Health usually changes immediately when damage resolves. A posture gauge commonly rewards sustained player pressure by opening the boss to a finisher. Status buildup instead records exposure on a target and withholds its separate payload until a threshold is crossed; that payload may harm, constrain, transform, or defeat either side.

Bosses that use this mechanic

Learn more

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