Beginner Series
What 'Resolves Top-Down' Means in Practice
You know the stack resolves last-in-first-out. Here's what that actually looks like across the trickier situations — ordering your own triggers, holding priority, and reading an opponent's line.
Resolves first ↴
TOP OF STACK
Opponent's protection spell
CAST SECOND
Your removal spell
CAST FIRST
Their protection spell resolves before your removal ever gets the chance.
"Top-down" is easy to say and easy to misapply once multiple things stack up at once — especially when several of your own triggers happen at the same time, or when you're deciding whether to respond to your own spell.
The core idea never changes: whatever was added to the stack most recently resolves first. The tricky part in practice is that you control the order when multiple things you control would go on the stack simultaneously — so "top-down" isn't just something that happens to you, it's a tool you actively use.
The stack doesn't just tell you what happens first — knowing you control the order of your own simultaneous triggers is what turns "top-down" from a rule you follow into a rule you use.
— why this is worth a second, deeper look after learning the stack basics
The core resolution rule is 405.5; ordering simultaneous triggers you control comes from rule 603.3b.
Comprehensive Rules · Rule 405.5
"Whenever all players pass in succession, the spell or ability on top of the stack resolves — or, if the stack is empty, the phase or step ends."
Comprehensive Rules · Rule 603.2c
"An ability triggers only once each time its trigger event occurs. However, it can trigger repeatedly if one event contains multiple occurrences."
When a player controls two or more abilities triggering at the same time, that player chooses the order they go on the stack — meaning the ability they want to resolve first should be the last one they put on the stack.
Ordering your own triggers on purpose
You control two "whenever a creature dies, draw a card" effects, and three of your creatures die simultaneously to a board wipe.
All six triggers are yours to order. Since order rarely matters when the effects are identical, this example gets interesting when the effects differ — say, one trigger deals damage and one gains life.
If you want the damage to happen with the most information available, you'd put the damage trigger on the stack last, so it resolves first.
Reading an opponent's response
You cast removal on their creature. They respond with a protection spell targeting that same creature.
Because their spell was added second, it resolves first — the creature gains protection before your removal ever resolves.
Your removal then fizzles: an illegal target when it tries to resolve, since protection makes it un-targetable.
How to take advantage of it
Order your own triggers for maximum information. When effects differ, put the one that most changes your decision-making last, so it resolves first and informs the rest.
Don't assume a spell will resolve as cast. Since anything can be added on top of your spell before it resolves, treat every spell on the stack as "pending" rather than "done" until it actually resolves.
Use holding priority to build a guaranteed sequence. If you need two of your own effects to resolve in a specific order with nothing in between, cast or activate them without passing priority at all.
Cards & commanders that spotlight stack ordering
Protection effects
Cards that exploit top-down resolution defensively, undoing a spell that's already on the stack targeting you.
Simultaneous-trigger payoffs
Cards that reward carefully ordering multiple triggers you control at once.
Keep the table on the same page.
TurnZero tracks life, turns, and moments so nobody's re-litigating what happened three plays ago.
Create Free Account