The Stack (For New Players)

Guides · beginner

When you cast a spell, it doesn't happen instantly. It goes onto a list called the stack. Other players have a chance to respond before it resolves.

In a single sentence

The stack is "I'm doing X" -- "okay, I'm doing Y in response" -- "okay, I'm doing Z in response" -- and then the things resolve in reverse order, last one first.

A simple example

I cast Lightning Bolt to kill your 4/4 creature.

You don't have an instant in hand to save it. The Bolt resolves, your creature dies.

A response example

I cast Lightning Bolt to kill your creature.

You cast Counterspell to counter my Bolt.

I have nothing else. Counterspell resolves first (it was added second to the stack, so it resolves first). My Bolt is countered and goes to my graveyard. Your creature is fine.

A double-response example

I cast Lightning Bolt.

You cast Counterspell.

I cast Veil of Summer which reads "Draw a card. Until end of turn, you and permanents you control gain hexproof from blue and from black."

Now Veil resolves first. My spells gain hexproof from blue. Counterspell tries to resolve next -- but its target (my Bolt) now has hexproof from blue, so its target is illegal. Counterspell is countered by the rules. Then my Bolt resolves -- your creature dies, and I drew a card from Veil.

When does the stack matter?

Mostly when:

• Someone is trying to remove your creature (instant-speed)
• You're casting a counterspell
• A combat trick is happening
• A triggered ability triggers and someone wants to mess with it

Tips for casual play

• It's totally normal to ask "Wait, what's on the stack right now?" Casual tables expect this.
• "In response" means "before that resolves." Speak up before the spell resolves.
• If someone passes priority and you didn't realize there was something to respond to, in casual play it's fine to say "wait, can I respond?" Most tables will allow it.

Going deeper

See the Stack & Priority tab for more detail and worked examples.