If you’ve ever had a game stall out on the phrase “i respond,” congrats, you’ve met the real final boss of Commander night: priority. This is MTG priority explained the way people actually experience it, with shortcuts, assumptions, and the occasional “wait, you can’t do that” that somehow lands like a personal insult.
Priority isn’t just rules trivia. It’s the system that decides who is allowed to do something right now. And once you understand it, half the “gotcha” moments at the table stop being mysterious and start being… preventable. Not always. People will still fight. But at least you’ll know why.
What priority is (in human language)
Priority is the game’s talking stick.
- If you have priority, you can cast spells (usually), activate abilities, and take certain special actions.
- If you don’t have priority, you can absolutely want to respond. That’s nice. The stack does not care.
The main reason priority exists is simple: Magic needs an orderly way to let players act between game events, especially once spells and abilities are piled onto the stack like a Jenga tower built by someone who “doesn’t really play blue.”
If you want the bigger picture on the stack itself, this pairs nicely with our guide: MTG Timing Guide.
The rhythm: act, pass, act, pass… resolve
Here’s the part that clears up most arguments:
Spells and abilities only resolve when every player passes priority in succession.
Not “when the caster is done reading the card.”
Not “when the table kind of nods.”
Not “when someone says ‘sure.’” (We’ll get there.)
The loop looks like this:
- Someone gets priority.
- They either do something (cast/activate/etc.) or pass.
- If they do something, that object goes on the stack, and priority continues.
- If everyone passes one after another, the top thing on the stack resolves.
- After it resolves, priority comes back again.
That’s why priority feels like “permission” and why “i respond” has to happen before the table has passed all the way around.
Why “i respond” actually means something
When someone says “i respond,” what they should mean is:
“Before we let that spell or ability resolve, I’m taking an action while it’s still on the stack.”
That implies two things:
- There is something on the stack to respond to.
- The game is currently in a priority window where you can legally act.
Where it goes sideways is when the table has already done a soft-fast-forward like:
- Player A: “Cast Doom Blade targeting your thing.”
- Player B: “Resolves.”
- Player C: “Ok.”
- Player D: “Cool.”
- Player B: “Wait i respond!”
At that point, the table has basically said “we all passed.” The object resolves. You don’t get to time travel because you remembered your trick late. That’s not “tight play,” that’s “rewinding because we’re friends,” which is a totally valid casual policy, but it is not a rules argument.
Passing priority vs “I’m thinking”
Here’s a subtlety that matters:
- Passing priority is an in-game choice.
- Thinking is a real-life activity that does not stop the rules engine.
In practice, most tables treat hesitation as “I might do something,” which is socially polite and mechanically fuzzy. If you want fewer fights, the cleanest table habit is:
- Say “hold on, I may have a response” (meaning: do not assume I’m passing).
- Or say “no response” / “I pass” (meaning: you can keep moving).
It feels awkward the first few times. Then it saves you from the “I thought you passed” spiral.
Holding priority: yes, you’re allowed to do that
“Holding priority” (also called “maintaining priority”) is when you cast a spell or activate an ability and then immediately do another thing before anyone else gets a chance to respond.
Common reasons:
- You want to cast a spell and then activate something before opponents can remove it.
- You want to stack multiple effects in a specific order.
- You are a Storm player and your hobby is paperwork.
Example:
- “Cast Lightning Bolt targeting you. Hold priority, cast Reverberate copying Bolt.”
That’s legal because after you cast a spell, you typically get priority again. You’re not “cheating a response window.” You’re using the rules as written.
The catch is this: people assume you pass unless you say you’re holding priority. Which leads us to…
The shortcut problem: everyone assumes you passed (until you don’t)
Most games are played using shortcuts. Nobody wants a table where every action is:
“I have priority. Do you have priority? Do you pass priority? Do you pass priority? Do you pass priority?”
That’s not Magic, that’s a customer service phone tree.
So we shortcut. And the most common shortcut is:
If you cast a spell and don’t say anything else, the table assumes you’re passing priority so someone can respond.
Most of the time, that’s fine. The problem is when you meant to hold priority, didn’t say so, and then try to do it after someone reacts.
If you want to hold priority, be explicit:
- “Cast this, hold priority…”
- “Before anyone responds…”
- “Still in my main phase with priority…”
Yes, it sounds a little judge-y. But it prevents the much worse outcome where three people argue about what you “obviously meant.”
Priority in Commander: it goes around the table, not just back and forth
In two-player Magic, priority is a ping-pong match: active player, non-active player, repeat.
In multiplayer, priority passes in turn order. That means in a four-player pod, after the active player passes, it goes to the next player, then the next, then the next.
This matters because:
- A spell doesn’t resolve until everyone passes.
- One person’s “no response” is not a group vote.
- The player right after you can respond even if the player across the table said “sure.”
If you’ve ever seen someone try to rush a spell through because “you said it resolves,” this is why that doesn’t work. You are not the Supreme Court of the stack.
“Go to combat?” is not a single moment
Combat has multiple steps, and priority exists in them. The biggest table argument is usually about which moment someone meant when they said “combat.”
Common fight:
- Active player: “Combat?”
- Someone: “Sure.”
- Active player: “Ok declare attackers…”
- Someone else: “Wait, at beginning of combat I tap your creature.”
They are not being annoying. They are using a real window.
To keep combat clean, try phrasing like:
- “Move to beginning of combat. Any actions?”
- “Ok, declare attackers.” (after the table has had a chance)
If you want a full breakdown of where those windows actually are, here’s the companion piece: MTG Combat Step Breakdown: Attacks, Blocks, Damage, Tricks.
The “go / your turn” shortcut that causes end step drama
Another classic:
- Active player: “Go.”
- Non-active player: “End step, I cast this.”
- Active player: “No, I meant I’m done, it’s your turn.”
In tournament policy, phrases like “go” and “your turn” are treated as shortcuts that generally move the game toward the end step (and then the next turn), with room for responses in the end step. Casual tables often do something similar by habit.
The practical takeaway is simple:
- If you say “go,” you are basically inviting “end step shenanigans.”
- If you don’t want end step shenanigans, don’t say “go” like you’re slamming a car door.
Say what you mean:
- “Pass to end step, then I want to do something.”
- “I’m passing the turn.” (and accept the end step window exists)
- Or if you really mean “I am done and nobody gets to do anything,” well… good luck with that.
The cleanest way to avoid priority fights
You don’t need to narrate priority like a rules audiobook. You just need a few consistent phrases.
Use these at the table
- “Hold priority” when you intend to stack multiple actions before responses.
- “Any responses?” when you actually mean “I’m passing and giving you a window.”
- “In response” only when something is on the stack and you are acting before it resolves.
- “Beginning of combat?” instead of the vague “combat?”
- “End step?” instead of “go” if you want to be clear about timing.
Don’t use these if you want peace
- “It resolves?” (when you actually mean “do you have anything?”)
- “Sure” (when you actually mean “I’m thinking, don’t move on”)
- “Ok” (the most dangerous word in Commander)
A quick aside: other games solve this differently (and it’s kind of nice)
If you’ve played Android: Netrunner, you’ve seen a cleaner version of this: paid ability windows, clear checkpoints, and fewer moments where someone tries to rewind three decisions because they “forgot” their trigger.
Magic is older, broader, and held together by a mix of precise rules and social shortcuts. Priority is the part where those two realities collide. Usually right into someone’s face.
The real moral of MTG priority explained
Most priority fights are not about rules knowledge. They’re about assumptions.
- One player is playing “strict windows.”
- Another is playing “table vibe.”
- Both think the other is being unreasonable.
- The stack continues to sit there like a bored accountant.
If you want fewer blowups, make the shortcut explicit. Magic lets you be clear. It just does not force you to be clear.
And that’s why “i respond” actually means something.
