Contents

Comprehensive Rules

700 Statuses, Stacks, and Immunity

How statuses are stored, how they expire, and what Relentless actually stops.

700.1Status shapes

  1. 700.1aA timed status is on or off, with a timer: Stun, Freeze, Blind, Prismbreak, Entrap.
  2. 700.1bA stacking status is a count: Burn, Venom, Maim, Haywire, Feral, Interest, Insurance.
  3. 700.1cHallow is an instance status: each application is its own entry and several run side by side. Roost uses the same machinery but collapses to exactly one entry, so a second Roost raises the existing per-tick amount instead of adding a parallel heal.
  4. 700.1dCrush and Smash are not statuses. They are timed stat and tier reductions with a matching on-card indicator.
  5. 700.1eDread is tracked as its own stack family rather than as a status, but it counts as a negative status for cards that read one.

700.2Reapplication

  1. 700.2aStun replaces its remaining duration. A shorter Stun over a longer one shortens it.
  2. 700.2bFreeze adds a flat 4 seconds. Blind adds a flat 2 seconds. Prismbreak adds a flat 3 seconds.
  3. 700.2cStacking statuses add to their count, subject to their cap.
  4. 700.2dSmash adds duration but never a second tier reduction.
  5. 700.2eCrush applications are independent timed reductions, each lasting its own 2 seconds.

700.3Application gates

  1. 700.3aA status is refused if the recipient is Dormant, dead, or an untargetable object, unless it is a clear-status effect.
  2. 700.3bA status is refused if the recipient is Entrapped, unless it is Entrap itself or the effect explicitly allows application through Entrap.
  3. 700.3cA status is refused if the recipient has Relentless and the status is one Relentless blocks.
  4. 700.3dMaim and Smash ignore status immunity, so the Relentless gate does not stop either of them.
  5. 700.3eA boss break mechanic may apply a negative status through immunity.

700.4What Relentless blockspage

Relentless is the game's immunity keyword. "Status immunity" on a card means Relentless, so a line that reads "Ignores status immunity" resolves through this table. This is the complete list.

EffectBlocked by Relentless?Why
StunBlockedNegative status.
FreezeBlockedNegative status.
BlindBlockedNegative status.
PrismbreakBlockedNegative status.
BurnBlockedNegative status.
VenomBlockedNegative status.
HaywireBlockedNegative status.
FeralBlockedNegative status.
InterestBlockedNegative status.
DreadBlockedExplicit check before stacks are added.
CrushBlockedTimed Armor reduction.
SmashNot blockedSmash ignores status immunity.
Piercing RoarBlockedPower reduction.
Crippling ScreamBlockedSpeed reduction.
RepossessBlockedArmor reduction.
Boss Power drainBlockedStat reduction.
MaimNot blockedMaim ignores status immunity.
CullNot blockedCull never consults Relentless.
EntrapNot blockedRemoval effect, deliberately exempt.
InsuranceNot blockedNot a negative status.
RoostNot blockedBeneficial.
HallowNot blockedBeneficial.
BloodlustNot blockedA condition, not a status.
DamageNot blockedRelentless is not damage immunity.
Harvest recipientsExcluded earlierRelentless units leave the pool before selection.
  1. 700.4aRelentless blocks the application, not the effect that is already present. A unit that gains Relentless while Burning keeps its Burn.
  2. 700.4bRelentless also does not remove an existing Crush; it only refuses new ones.

700.5Clearing

  1. 700.5aA clear effect names one status family and removes it. Clear effects are the only category that resolves against a Dormant unit.
  2. 700.5bClearing a stacking status may remove a specific number of stacks rather than all of them — Haywire's own resolution removes exactly one.
  3. 700.5cDeath clears combat statuses. Relentless suppression is the deliberate exception and survives death and revival.