The Stack, Priority, and Timing: What New Commander Players Get Wrong

Commander is the most popular Magic format, but also the most casual. That combination creates a problem: players learn Commander first, skip the structured rules enforcement of competitive formats, and develop habits that make them easy prey at higher-power tables.

The single biggest gap? Understanding the stack, priority, and timing.

If you've ever said "okay, my spell resolves" and gotten blown out by an instant in response, this guide is for you.

What Is The Stack?

The stack is Magic's system for resolving spells and abilities in last-in, first-out (LIFO) order. Think of it like a stack of plates: the last plate you put on top is the first one you take off.

When you cast a spell or activate an ability, it goes on the stack. Before it resolves, every other player gets a chance to respond. Their responses go on the stack on top of your spell. Those responses resolve first, then your original spell resolves.

Example:

1. Alice casts Lightning Bolt targeting Bob's creature.
2. Bob casts Heroic Intervention in response.
3. Stack (top to bottom): Heroic Intervention → Lightning Bolt
4. Heroic Intervention resolves first, giving Bob's creatures indestructible and hexproof.
5. Lightning Bolt resolves, but can't target the creature anymore (hexproof).

Bob's creature survives. Alice's Bolt fizzles because its target became illegal.

Priority: Who Gets To Act When?

Priority determines whose turn it is to cast spells or activate abilities. You can't do anything in Magic without priority.

Here's how priority works:

1. Active player gets priority first. After you cast a spell, play a land, or move to a new step/phase, you get priority.
2. Priority passes clockwise. Once you pass priority (by saying "okay" or doing nothing), the next player gets it.
3. Everyone must pass for something to resolve. A spell or ability on the stack doesn't resolve until all players pass priority in succession.
4. Active player gets priority again after something resolves. When a spell or ability resolves, the active player gets priority before anything else can happen.

Critical mistake new players make: Saying "okay, my spell resolves" immediately after casting it. That's not how it works. Your spell goes on the stack, you pass priority, and every other player gets a chance to respond before it resolves.

Common Priority Mistakes

Mistake #1: Not Holding Priority

You cast Sol Ring. You want to tap it for mana immediately.

Wrong: "I cast Sol Ring, tap it for

."

Sol Ring is on the stack. It hasn't resolved yet. You can't tap it for mana.

Right: "I cast Sol Ring." (Pass priority, let it resolve.) "Sol Ring resolves. I tap it for

."

Exception: You can hold priority by explicitly saying "holding priority" after casting a spell. This lets you cast another spell or activate an ability before anyone else can respond.

Example: "I cast Deflecting Swat, holding priority. I tap Sol Ring for

, then cast Counterspell targeting your removal spell."

Mistake #2: Responding To Your Own Spell By Accident

You cast a creature. Opponent 1 passes. Opponent 2 says "before it resolves, I cast Swords to Plowshares."

New players often panic and try to "save" their creature by casting another spell. But your creature is still on the stack. You can't target it with your own Heroic Intervention — it's not on the battlefield yet.

When you can interact with your own spell: When you hold priority (see above) or when you have an ability that counters spells (like Mana Drain or Pyroblast).

Mistake #3: Assuming Instant Speed Means "Any Time"

Instants and abilities with "instant speed" can be cast "whenever you could cast an instant." That sounds like "any time," but it's not.

You can only cast instants when:

1. You have priority, AND
2. The stack is empty (for playing lands), OR
3. You're responding to something on the stack.

You cannot cast an instant in the middle of another spell or ability resolving. Resolution does not use the stack.

Example:

• Opponent casts Wrath of God.
• You cast Teferi's Protection in response.
• Wrath resolves. Your creatures phase out, dodging the Wrath.
• You cannot cast another instant "during" Wrath of God's resolution. Wrath destroys creatures, then is put into the graveyard. No one gets priority during this process.

Mistake #4: Not Responding At The Right Time

When an opponent casts a big spell, new players often wait to see if anyone else will counter it. This is fine in casual pods, but at higher-power tables, this hesitation gives information away.

Better habit: If you're going to interact, do it immediately. If you pass priority, you've signaled you have no answer (or you're bluffing).

Advanced tactic: If you're not the next player in priority order, you can wait to see if the next player responds first. If they pass, you can still respond. This is called "priority order fishing" and it's why interaction is strongest when you're sitting after the threat player.

The Stack In Multiplayer: Who Responds First?

In Commander (and all multiplayer formats), priority passes in turn order starting with the active player.

Example scenario:

• Turn order: Alice → Bob → Charlie → Dana
• Alice (active player) casts Expropriate.
• Priority order:
  1. Alice (active player) passes priority first.
  2. Bob gets priority next (clockwise).
  3. Charlie gets priority after Bob passes.
  4. Dana gets priority last.

Why this matters: Bob has to decide whether to counter Expropriate before seeing if Charlie or Dana will. Dana, sitting last in priority, gets to see everyone else's responses before deciding. This is why sitting after the scariest player at the table is an advantage.

Politics tip: If you're early in priority and you have a counterspell, you can bluff by passing priority. If the next player counters, you saved your counterspell. If no one counters, you can still respond when priority comes back around (if the spell is still legal to counter).

Timing: When Can You Actually Do Things?

Magic has a strict turn structure. You can only cast sorceries and most permanents during your main phases when the stack is empty.

You can cast instants and activate abilities (unless they say otherwise) whenever you have priority.

Key moments where priority matters:

Beginning of Combat

This is a step, not a phase. When you move from your main phase to combat, you must explicitly say "moving to combat." At this point:

• All players get priority.
• Instants and abilities can be cast/activated.
• You cannot declare attackers yet.

Why this matters: If an opponent taps down your creatures "before you attack," they do it in the Beginning of Combat step. You can't declare attackers yet. By the time you reach the Declare Attackers step, your creatures are already tapped.

Shortcut mistake: Saying "attack with everything" without passing through Beginning of Combat. Technically, you've shortcut to Declare Attackers, and your opponent can back up and tap your creatures in Beginning of Combat.

Best practice: Always say "moving to combat" and pause. If no one responds, then declare attackers.

End of Turn

Everyone gets priority during the End Step. This is when you cast instants "at the end of your turn" (like Fact or Fiction or Blue Sun's Zenith).

Why cast spells on your own end step instead of your main phase? Two reasons:

1. You hold up mana for interaction during opponents' turns. If no one does anything scary, you cast your draw spell at the end of your turn.
2. You draw cards with a full hand size buffer before your next turn starts.

Triggered Abilities Use The Stack

Triggered abilities (abilities that start with "when," "whenever," or "at") go on the stack just like spells. Players can respond to them.

Example:

• You attack with a creature that has "whenever this creature attacks, draw a card."
• The triggered ability goes on the stack during the Declare Attackers step.
• An opponent can cast Swords to Plowshares targeting your creature in response to the trigger.
• The creature dies, but you still draw a card (the trigger already went on the stack).

Common mistake: Assuming triggered abilities resolve instantly. They don't. They use the stack.

Advanced: Split Second and Can't Be Countered

Some spells have abilities that mess with the normal stack rules.

Split Second

Sudden Spoiling has split second. While it's on the stack, no one can cast spells or activate abilities (with a few exceptions like mana abilities and turning face-down creatures face up).

Split second does NOT mean "can't be countered." It just means no one can respond to it. If you cast Counterspell in response to the spell before it's on the stack, Counterspell resolves first and counters it.

Example:

1. Opponent casts Krosan Grip (split second) targeting your Rhystic Study.
2. You cannot cast another instant in response.
3. You cannot activate Rhystic Study's ability.
4. Krosan Grip resolves and destroys Rhystic Study.

Workaround: If you have priority and suspect a split second spell is coming, you can activate abilities or cast spells before they cast it. This is why holding priority is powerful.

This Spell Can't Be Countered

Boseiju, Who Endures has "this spell can't be countered." It goes on the stack normally, and players can respond to it, but counter spells like Counterspell or Mana Drain won't work.

What you CAN do:

• Change its target (e.g., Redirect, Deflecting Swat).
• Counter the spell that tutored for it or cast it (if applicable).
• Let it resolve and remove the permanent it puts onto the battlefield.

"Can't be countered" only stops counter spells. It doesn't stop interaction entirely.

Putting It All Together: A Real Game Scenario

Let's walk through a complex stack interaction:

Turn order: Alice → Bob → Charlie → Dana
Active player: Alice

1. Alice casts Kodama of the East Tree (legendary creature).
2. Alice passes priority. Bob passes. Charlie passes. Dana passes.
3. Kodama resolves and enters the battlefield.
4. Alice plays a land. Kodama's triggered ability goes on the stack ("whenever another permanent enters the battlefield under your control, if it wasn't put onto the battlefield with this ability, you may put a permanent card with equal or lesser mana value from your hand onto the battlefield").
5. Alice passes priority.
6. Bob casts Swords to Plowshares targeting Kodama (holding priority), then activates Commander's Plate to give another creature protection from white (using the mana from the Swords).
7. Priority passes. No other responses.
8. Commander's Plate ability resolves (creature gets protection from white).
9. Swords to Plowshares tries to resolve, but its target (Kodama) is gone — Bob targeted Kodama, not the creature with protection. Swords fizzles.
10. Kodama's trigger resolves. Alice puts Avenger of Zendikar onto the battlefield.
11. Avenger's ETB trigger goes on the stack ("create a 0/1 Plant token for each land you control").
12. Alice passes priority.
13. Charlie casts Cyclonic Rift overloaded. This goes on the stack above Avenger's trigger.
14. Cyclonic Rift resolves first. Avenger and all other nonland permanents Alice controls are returned to her hand.
15. Avenger's trigger is still on the stack. It resolves, but Avenger is no longer on the battlefield. The trigger creates Plant tokens equal to the number of lands Alice controlled when the trigger went on the stack (not when it resolves).

Lesson: The stack lets you disrupt permanents before their abilities resolve, but triggered abilities remember information from when they triggered, not when they resolve.

TL;DR: Stack Rules You Must Know

1. Last in, first out. The stack resolves top to bottom.
2. Priority passes clockwise. Active player first, then each opponent in turn order.
3. Spells don't resolve until everyone passes. Don't assume your spell resolves immediately.
4. Hold priority to chain spells/abilities. Say "holding priority" out loud.
5. You can only cast instants when you have priority. Not during another spell's resolution.
6. Triggered abilities use the stack. You can respond to them just like spells.
7. Beginning of Combat exists. Don't shortcut directly to attackers.
8. End Step priority exists. Use it to draw cards or activate abilities at the last possible moment.

---

Master the stack, and you'll turn losing boardstates into winning plays. Ignore it, and you'll keep getting blown out by players who know better.