Triggered Abilities

"When", "whenever", "at" — plus intervening-if and ordering a pile of simultaneous triggers.

The rule is CR 603. Stacking order is 603.3b, intervening-if is 603.4, zone-change triggers are 603.6, and the look-back-in-time exceptions are 603.10.

A triggered ability is written "[When / Whenever / At] [trigger condition], [effect]." Those three words are the tell. Learn to spot them, because the alternatives are different kinds of ability with different rules: "as long as" is static, "instead" and "skip" are replacement effects, and neither of those ever touches the stack.

Triggering and doing are two different things

When the game state matches the trigger condition, the ability triggers automatically — and does nothing at all. It waits. It goes on the stack the next time a player would receive priority, and only does its effect when it resolves.

That gap is the whole reason triggers are interactive. It's also why an ability that triggers during the untap step waits until upkeep, and why several triggers from one event all go on the stack together.

Control is fixed at trigger time: the ability is controlled by whoever controlled its source when it triggered. Later changes to that source don't follow it onto the stack — the ability there is its own object with just that text.

Ordering: the free skill

When several of your own abilities trigger at once, you choose the order they go on the stack, freely, every time. Since the stack resolves top-down, the one you put on last resolves first. Draw before sacrifice, counter before damage — deliberate ordering often decides the turn.

Across players it's APNAP: the active player's abilities go on lowest, then each other player in turn order. Lowest means last to resolve, so the non-active player's trigger resolves first.

There is a subtlety in how the pile is stacked. It happens in two passes:

1. Each player, in APNAP order, puts on the abilities whose trigger condition is not another ability triggering.
2. Each player, in APNAP order, puts on everything remaining — i.e. the abilities that trigger off other abilities triggering.

The second pass lands on top, so those "whenever an ability triggers" effects resolve first.

Intervening "if"

An ability reading "At the beginning of your upkeep, if you control three or more artifacts, draw a card" has an intervening "if" clause, and the condition is checked twice: once for the ability to trigger at all, and again as it resolves. Fail either check and nothing happens.

Practically: an opponent can destroy your third artifact in response, and the draw simply fails. This only applies to a condition sitting between the trigger event and the effect — a condition written inside the effect is a different thing entirely.

Things that look like triggers but aren't

"This permanent enters tapped." "This creature enters with two +1/+1 counters." "As this enters, choose a colour." None of these are triggered abilities — they're static abilities generating replacement effects. They modify the entering event itself rather than reacting to it, so there is nothing on the stack and nothing to respond to. The land is never briefly untapped; it simply arrives tapped.

Enters-the-battlefield triggers see everything that arrived

When an event puts one or more permanents onto the battlefield, all permanents on the battlefield — the newcomers included — are checked for abilities that trigger.

So if two creatures each with "whenever a creature enters, gain 1 life" arrive simultaneously, you get four triggers: each ability sees both arrivals, its own included. This is why simultaneous token-making and "whenever a creature enters" payoffs multiply so aggressively.

Zone changes: looking forward and looking back

A zone-change trigger that wants to do something to the object looks for it in the zone it moved to. If it isn't there any more, the parts that needed it simply don't happen — the ability still resolves. This is the standard answer to a recursive threat: exile it from the graveyard while its own return trigger is on the stack.

Some triggers look back in time instead, using the game state as it was immediately before the event: leaves-the-battlefield abilities, sacrifice triggers, abilities watching a card leave a graveyard, and phase-out triggers.

That's why a board wipe destroying your "whenever a creature you control dies, draw a card" enchantment and all your creatures simultaneously still draws you cards — the enchantment died at the same instant, and looking back, it sees everything that left alongside it.

Two more corners

• A modal trigger has its mode announced when it's put on the stack, so opponents know what they're responding to. A mode with no legal targets can't be chosen, and with no legal mode at all the ability leaves the stack.
• A state trigger watches a game state rather than an event ("when you control no creatures, …"). It triggers as soon as the state matches, and won't trigger again until it has resolved, been countered, or otherwise left the stack — otherwise a persistently true condition would loop forever.

30 questions in this track, checked against the 2026-06-19 Comprehensive Rules.

Rules covered: 101.4, 104.3a, 117.5, 405.4, 603.1, 603.2, 603.3, 603.3a, 603.3b, 603.3c, 603.4, 603.5, 603.6, 603.6a, 603.6d, 603.7, 603.8, 603.9, 603.10, 603.10a, 603.11, 607, 614.1c, 614.12, 700.2.