Triggered Abilities

Interactions · intermediate

A triggered ability is an ability that watches for a game event and, when the event happens, puts itself on the stack. They start with when, whenever, or at.

How they work

1. The trigger condition occurs.
2. The next time anyone gets priority, the ability is put on the stack (if multiple triggers happened, the active player puts theirs on first, then each opponent in turn order).
3. Targets are chosen as the trigger goes on the stack.
4. Players get priority and can respond.
5. The trigger resolves.

"When this dies" example

• I sacrifice Solemn Simulacrum. Trigger: "When Solemn Simulacrum dies, you may draw a card."
• Sacrifice happens -> Simulacrum dies (state-based action moves it to graveyard).
• Next priority window -> the trigger goes on the stack.
• I choose to draw (or not).
• Players have priority. They can cast a spell to mess with my draw step somehow, but they can't undo the trigger going on the stack.
• Trigger resolves -> I draw a card.

"Triggers stay on the stack even if their source dies"

This is critical. Once a triggered ability is on the stack, removing the source doesn't remove the trigger. Killing the Goblin Rabblemaster in response to its attack trigger doesn't undo the goblin token -- the token is created when the trigger resolves, regardless of whether Rabblemaster is still around.

Intervening "if" clauses

Some triggers have "if" in their text: "Whenever a creature you control dies, if it had power 4 or greater, draw a card." The condition is checked twice: once when the trigger would trigger (creature must die), and once when the trigger resolves (had power 4 or greater).

If the condition fails on resolution, the trigger does nothing. (See [603.4].)

Common pitfalls

• Stacking multiple triggers: Active player puts theirs on first; opponents in turn order. Opposite of normal stack order.
• Missed triggers: In casual Commander, if you forget to put your trigger on the stack and an opponent didn't notice either, the trigger is generally considered "missed." Strict rules tournaments have specific procedures (the IPG covers this).
• Combat triggers in the wrong window: "Whenever this attacks" triggers in the declare attackers step, not the beginning of combat.

[603]