If you've ever been confused about why your opponent can "respond" to your spell, or why a counterspell stops a creature from entering the battlefield, or how two instant-speed effects interact when they're cast at the same time — you're bumping into the stack. It's the system Magic uses to organize and resolve everything that happens in the game.

The good news: the stack follows one rule, and once that rule clicks, every weird interaction in Magic makes sense. The bad news: most explanations overcomplicate it with rules jargon. This one won't.

Whether you're playing kitchen-table Commander or sitting down for your first competitive format, the stack works the same way everywhere. Learn it once, and it applies to every game of Magic you'll ever play.

What the Stack Actually Is

Picture a stack of plates. When you cast a spell, you put a plate on top. When your opponent responds, they put another plate on top of yours. When it's time to resolve, you take plates off the top — the most recent one resolves first.

That's the stack. It's an invisible zone where spells and abilities wait to resolve. Nothing happens instantly in Magic — every spell goes on the stack first, and every player gets a chance to respond before it resolves. Only when all players pass without adding anything does the top item actually happen.

This is why a creature spell isn't a creature yet while it's on the stack — it's still a spell. It becomes a creature only after it resolves and enters the battlefield. And that distinction matters: you can counter a creature spell, but you can't counter a creature that's already on the battlefield.

The One Rule: Last In, First Out

The stack resolves from top to bottom — the last thing added is the first thing to resolve. In computer science this is called LIFO (last in, first out), and it's the single rule that governs the entire system.

Here's a simple example:

Order	What Happens	Stack (top → bottom)
1	You cast Lightning Bolt targeting an opponent.	Lightning Bolt
2	Opponent casts Counterspell targeting your Bolt.	Counterspell → Lightning Bolt
3	All players pass. Top of stack resolves.	Counterspell resolves → Bolt is countered
4	Stack is now empty. Bolt never resolved.	(empty)

The Counterspell went on top of the Bolt, so it resolved first. By the time the game gets to the Bolt, it's already been countered — it goes to the graveyard without effect. If no one had responded, the Bolt would have resolved normally and dealt its damage.

Priority: Whose Turn to Act?

Priority is the system that determines who gets to add something to the stack. You can only cast spells or activate abilities when you have priority — and you can't interrupt someone mid-sentence.

• The active player gets priority first. At the start of each step or phase, and after any spell or ability resolves, the active player (whose turn it is) gets priority. They can cast a spell, activate an ability, or pass.
• Priority passes around the table. When you cast a spell, you get priority again (you could respond to your own spell), and then priority passes to each opponent in turn order. Each player can respond or pass.
• When all players pass in succession, the top item resolves. This is the key: nothing resolves until everyone has passed on the current top of the stack. Then the top item resolves, the active player gets priority again, and the cycle continues until the stack is empty.

A Turn Walked Through, Step by Step

Here's what priority looks like during a typical main phase, slowed down to show the system working:

Step	Action	Who Has Priority
1	Main phase begins. Active player gets priority.	You
2	You cast a creature spell. It goes on the stack.	You (again — you can respond to your own spell)
3	You pass. Priority goes to opponent A.	Opponent A
4	Opponent A passes. Priority goes to opponent B.	Opponent B
5	Opponent B passes. All players passed — creature resolves and enters the battlefield.	You (priority resets)

If Opponent A had cast a counterspell at step 4 instead of passing, the process would restart from step 2 with the counterspell on top. Everyone would need to pass on the counterspell before it resolved — and anyone could respond to the counterspell with their own spell first.

Five Scenarios That Click Once You Know the Stack

• 1. "I'll kill your creature in response to your Equipment." Your opponent casts an Equip ability (which uses the stack). You respond with a removal spell targeting the creature. Your removal resolves first (LIFO), the creature dies, and the Equip ability fizzles because its target is gone. Your opponent wasted their mana.
• 2. "In response to your board wipe, I'll sacrifice everything." Someone casts Wrath of God. An Aristocrats player responds by sacrificing all their creatures to a sac outlet, triggering death effects. The sacrifices resolve first (they're above the Wrath on the stack). By the time Wrath resolves, those creatures are already in the graveyard — they don't die to the wipe, and all the death triggers already happened.
• 3. "Counterspell war." You cast a game-winning spell. Opponent A counterspells it. You counter their counterspell. Opponent B counters your counter. Each of these goes on the stack in order, and they resolve top-down. The last counter to be cast (Opponent B's) resolves first — and its target is your counter, not the original spell. If it resolves, your counter is gone, which means Opponent A's counter is still there, which means your original spell gets countered.
• 4. "I'll pump my creature before your damage resolves." Someone casts Lightning Bolt targeting your 3/3. You respond with Giant Growth (+3/+3). Growth resolves first, your creature is now a 6/6. Then Bolt resolves, deals 3 damage. Your 6/6 survives with 3 damage marked. Without the stack, you'd have lost your creature.
• 5. "I'll draw before my own spell resolves." You cast a sorcery, then — while it's on the stack — activate an ability that draws you a card. The draw resolves first (LIFO). This is occasionally useful to find a card before you have to make a choice during your sorcery's resolution. You get priority after casting your own spell, so you can respond to it.

Triggered Abilities and the Stack

Triggered abilities — anything that starts with "when," "whenever," or "at" — also use the stack. When a trigger condition is met, the ability goes on the stack the next time a player would receive priority, and it can be responded to like any spell.

This matters because triggers don't happen "immediately." When a creature with an enters-the-battlefield ability resolves and hits the field, its ETB trigger goes on the stack — and opponents can respond before it resolves. If you play a creature that draws you a card on entry, an opponent can respond to the ETB trigger with removal. You still get the draw (the trigger is already on the stack, independent of the creature), but you might lose the creature before you can use whatever you drew.

If multiple triggers happen at the same time, the active player puts theirs on the stack first (in any order), then each other player in turn order. Since LIFO means the last triggers added resolve first, the non-active players' triggers resolve before the active player's.

Things You Can't Respond To

Not everything uses the stack. A few actions happen without any player getting a chance to respond:

• Playing a land. Lands are placed directly onto the battlefield — they don't use the stack and can't be countered. (Landfall triggers from the land entering do use the stack, though.)
• Mana abilities. Tapping a land for mana or activating Sol Ring doesn't use the stack. You can't "counter" someone tapping a land. This is why you can always tap your lands for mana in response to something — the mana ability resolves instantly.
• State-based actions. A creature with 0 toughness dies, a player at 0 life loses — these are checked automatically and don't use the stack. You can't respond to a creature dying from lethal damage; it just happens.
• Split second. A handful of cards have "split second," which means no player can cast spells or activate non-mana abilities while it's on the stack. Krosan Grip is the most common example — it destroys an artifact or enchantment, and no one can respond. This is the closest Magic gets to "truly instant."

Stack Nuances in Commander

The stack works identically in Commander as in any other format, but multiplayer adds complexity:

• More players = more responses. In a four-player Commander game, three people can respond to your spell before it resolves. This makes control strategies harder because you can't counter everything — but it also means someone else might counter the threat for you.
• Holding priority matters more. When you cast a spell, you can "hold priority" and cast another spell before passing. This is how combo decks chain multiple spells — casting the combo pieces back to back before opponents can respond to the first one. In casual play, just say "hold priority" clearly so there's no confusion.
• Politics happen on the stack. In Commander, the stack is where deals happen. "If you don't counter that, I'll remove it next turn" or "I'll counter it if nobody else will" — these negotiations happen in the priority window. Understanding the stack lets you negotiate from a position of knowledge.

Common Stack Mistakes

Stack FAQ

• Can I respond to my own spell? Yes. After you cast a spell, you receive priority again before it passes to opponents. You can cast another instant, activate an ability, or hold priority to cast something else on top of your own spell.
• Does combat damage use the stack? No — not anymore. In very old rules (pre-2010), combat damage used the stack and could be responded to. Under current rules, combat damage is dealt simultaneously and doesn't use the stack. You can still cast instants during the declare blockers step, before damage is dealt.
• What happens if a spell's target becomes illegal? If a spell's only target is illegal when it tries to resolve (the creature was sacrificed, the player left the game), the spell "fizzles" — it goes to the graveyard without doing anything. It was still cast, though, so "cast" triggers still fired.
• Can I tap a creature for mana in response to a kill spell? If the creature has a mana ability (tapping for mana), yes — mana abilities don't use the stack and can be activated even while another spell is resolving. You'll get the mana, but the creature still dies when the kill spell resolves.
• How deep can the stack get? There's no limit. In theory, dozens of spells and abilities can be on the stack at once. In practice, stack sizes of 3–5 are common in interactive Commander games. Combo turns can put 10+ items on the stack in a chain.

© GEEKYDOMAIN.COM | Strategy Powered by Data