Beginner Series

How the Stack Works

The last thing added is the first thing that happens. Once that one idea clicks, counterspells, combat tricks, and trigger chains stop feeling like chaos and start feeling like a puzzle you can read.

Beginner

Resolves first ↴

TOP OF STACK

Opponent's Counterspell

CAST SECOND

Sol Ring

CAST FIRST

Last in, first out — the Counterspell resolves before the Sol Ring ever does.

Basics

▾

The basics

Nothing in Magic happens the instant you cast it. Every spell and ability gets put on "the stack" first — a waiting line — and only resolves once everyone has had a chance to respond.

The stack works last in, first out (LIFO), like a pile of plates: whatever gets added most recently is the first thing to come back off. That's why you can cast a spell in response to a spell — your response jumps to the top and resolves before the thing it's responding to.

"Priority" is just Magic's word for "you get first dibs on doing something before this resolves." Every player has to pass priority, in order, before anything on the stack actually happens.

— the one sentence that unlocks the whole mechanic

The official rule

The stack is defined in rule 405 of the Comprehensive Rules; how it resolves is covered in rule 405.5 and section 608.

Comprehensive Rules · Rule 405.1

"When a spell is cast, the physical card is put on the stack. When an ability is activated or triggers, it goes on top of the stack without any card associated with it."

Comprehensive Rules · Rule 405.2

"The stack keeps track of the order that spells and/or abilities were added to it. Each time an object is put on the stack, it's put on top of all objects already there."

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."

Examples

Counterspell in response

You cast Sol Ring. It goes on the stack. You pass priority.

Your opponent casts Counterspell, targeting your Sol Ring. Counterspell goes on top of the stack.

Both players pass priority with nothing left to add — the top of the stack resolves first: Counterspell resolves, countering Sol Ring.

Sol Ring never resolves. It never even hit the battlefield — it goes straight to the graveyard as a countered spell.

A trigger chain

Two of your creatures have “whenever a creature enters, draw a card” triggers. You cast a creature spell and it resolves.

Both triggers happen at the same time, but you (the controller) choose the order they go on the stack.

Whichever trigger you put on the stack second resolves first — so the stack doesn't just apply to spells, it applies to your own triggered abilities too.

How to take advantage of it

Reading the stack well is one of the biggest skill gaps between new and experienced players.

Don't respond to your own stuff unless you need to. If nothing threatens your spell, passing priority immediately gets it to resolve faster and gives opponents less information.

Hold priority when you need to. If you want to cast a second spell before your first one resolves — say, to make sure a target is still legal or to bait a counterspell — you can respond to your own spell instead of passing.

Order your own triggers deliberately. When you control multiple simultaneous triggers, put the one you want to resolve first on the stack last — this matters constantly in decks full of "enters the battlefield" value creatures.

Watch what opponents leave up. Untapped mana during your turn is a signal — a good player plays around a possible response instead of walking into it.