CR / RELEASE 2026-07-24
Rule 370.1.a
An event is the singular moment that results from a Game Action being performed or from a Game Object changing state. Example: The moment that results from a unit being killed is an event that can be referenced by game effects, or even skipped entirely. Example: The moment that results from a unit becoming Mighty is an event that can be referenced by game effects, or even skipped entirely.
Rule hierarchy
Direct children
370.1.a.1Modifying or replacing an event is the same as modifying or replacing that Game Action or change in state that generated that event. Example: Zhonya’s Hourglass reads in part “If a friendly unit would die, kill this instead. Heal that unit, exhaust it, and recall it.” A unit’s death being replaced by Zhonya’s Hourglass is the same as the kill action that caused that death not occurring. Example: A card reads in part “The next time an enemy unit would become Mighty this turn, banish it instead. Its controller plays a 3 [M] Mech unit token to its location.” A unit becoming Mighty being replaced by this effect means the unit never became Mighty—no effects that trigger on units becoming Mighty will trigger.370.1.a.2An event can occur simultaneously with other events only when those events are all the result of the same Game Action or change in state occurring. Example: A spell reads in part “Kill up to two units at battlefields.” When that spell resolves, the units targeted are killed simultaneously because their deaths result from the same game action. Example: A spell reads in part “Kill a friendly unit. If you do, kill an enemy unit with no more Might than it.” When that spell resolves, the units are not killed simultaneously. There are two kill game actions being performed in the instructions of the spell. The friendly unit is killed first, followed by the enemy unit.