If you’ve ever said “in response” and then immediately realized you’re not 100% sure what you’re responding to, congratulations: you are playing Magic: The Gathering correctly.
MTG timing rules are the invisible traffic lights of the game. They decide who’s allowed to do something, when they’re allowed to do it, and why your “wait, before damage” moment was either a brilliant save or a beautifully confident misplay.
This is the hub article. If you learn the loop here, everything else (combat tricks, counterspells, triggers, “can I do this in upkeep?”, Commander pile-ons) becomes way less mystical and way more predictable.
And yes, predictable is still fun. It’s just fun with fewer arguments.
The core idea: the game runs on a loop
Magic looks chaotic, but the engine is basically this repeating pattern:
- Something happens (a step begins, a spell is cast, damage is dealt, a creature dies, etc.)
- The game cleans up anything that can’t legally stay that way (state-based actions)
- Any triggered abilities that triggered get put on the stack
- Someone gets priority
- Players add things to the stack or pass
- If everyone passes in a row, the top thing on the stack resolves
- Repeat until the stack is empty, then move forward in the turn
If you only remember one thing from this page, remember this:
You can only cast spells and activate most abilities when you have priority.
Everything else is just the details of how priority moves around.
What “priority” actually means
Priority is simply: permission to take actions.
When you have priority, you can usually:
- Cast an instant (and spells with flash)
- Activate activated abilities
- Take certain special actions (more on those later)
When you don’t have priority, you mostly watch. Sometimes you watch bravely. Sometimes you watch while holding up two blue mana and pretending you’re relaxed.
Who gets priority first?
In any step or phase where players get priority, the active player (the person whose turn it is) gets priority first.
Then priority passes to the next player in turn order (important in Commander), and so on.
Priority does not mean “my thing resolves now”
Casting a spell puts it on the stack. It does not resolve immediately. It resolves only after all players pass priority in a row while it’s on top of the stack.
If your table ever needs a reality check, this is the one.
If you want a deeper stack-only explanation, this pairs nicely with:
MTG: How the Stack Works (and Why Your Spell Didn’t Resolve)
The “before you get priority” cleanup: SBAs, then triggers
This part is the hidden mechanic that explains a ton of timing confusion:
Before any player gets priority, the game does two things:
- Checks state-based actions (SBAs)
- Puts triggered abilities on the stack (if any triggered)
Then, and only then, priority is given.
State-based actions: the game enforcing reality
State-based actions are things the game does automatically, without using the stack. Examples:
- Creatures with lethal damage die
- Creatures with 0 or less toughness die
- A player with 0 life loses
- The legend rule applies
- Auras fall off illegal targets
Players do not “respond to SBAs.” They happen, the game stabilizes, then you get priority.
Triggers: they trigger now, but they wait to be placed
Triggered abilities do not usually jump onto the stack the instant their event happens. They get put on the stack the next time a player would get priority, after SBAs have been checked.
This is why a creature can die to lethal damage and then you see “when this dies” triggers go on the stack right after. The trigger condition happened, then SBAs cleaned up, then triggers were placed, then priority happened.
That ordering is not a suggestion. It’s the engine.
How passing priority actually works
Here’s the part that causes 90% of “wait, I had a response” moments.
The basic rule
When a player has priority, they either:
- Take an action (cast/activate), which usually keeps the stack growing
- Or pass
Priority passes around the table.
If everyone passes in sequence, the top item on the stack resolves.
Then (important), the active player gets priority again, and the cycle repeats.
The big practical implication
If your opponent casts a spell and you want to respond, you are responding while that spell is on the stack.
If you let everyone pass and it resolves, that window is gone.
Yes, even if you “meant to.” The game is not psychic. It’s barely even friendly.
Turn structure: where the real timing windows live
A lot of timing questions are secretly “which step are we in?”
Beginning phase
- Untap step: no one gets priority (almost always)
- Upkeep step: players get priority
- Draw step: active player draws, then players get priority
Main phase
Players get priority. You can cast sorceries, creatures, planeswalkers, etc. only when the stack is empty and you have priority (and it’s your main phase).
Combat phase
Combat isn’t one blob. It’s several steps, and most of them have a “turn-based thing happens” moment followed by a priority window.
If combat timing is your personal nemesis, bookmark this too:
MTG Combat Step Breakdown: Attacks, Blocks, Damage, Tricks
The most commonly missed windows:
- After attackers are declared (before blockers)
- After blockers are declared (before damage)
- After first strike damage (before regular damage), when applicable
- After combat damage (before end of combat ends)
Ending phase
- End step: players get priority
- Cleanup step: usually no priority… unless something happens that forces it
This is where “damage wears off,” “until end of turn” ends, and players discard down to hand size.
If something triggers during cleanup or a state-based action happens that needs handling, the game can create another cleanup step. Magic is polite like that. It cleans until the mess stops happening.
Trigger timing details that matter in real games
“At the beginning of” triggers
“At the beginning of upkeep/end step/combat” triggers trigger at that moment, then they get put on the stack before priority is given in that step.
So yes, you can respond to them, because once they’re on the stack, priority happens like normal.
APNAP ordering in multiplayer
In multiplayer (especially Commander), triggers controlled by the active player go on the stack first, then the next player in turn order, and so on. Players choose the order of their own triggers, but the overall order is governed by turn order.
This matters because the stack resolves top-down, so the triggers added last will resolve first.
Triggered vs activated vs static, in one sentence each
- Triggered: starts with when/whenever/at. Happens because something happened.
- Activated: written “Cost: Effect.” Happens because someone chose to do it.
- Static: just “is/has” text that’s always true while it applies.
If you can classify the ability, timing questions get way easier.
The exceptions that make people think the rules are fake
Special actions
Some things don’t use the stack and don’t require priority in the normal way. Examples include:
- Playing a land (during your main phase, with priority, stack empty)
- Turning a face-down creature face up (morph/disguise) as a special action
- Certain “take this action any time you could cast an instant” special cases (rules get specific here)
The important vibe: special actions are the game’s way of saying “this doesn’t belong on the stack, but it still has timing rules.”
Casting spells during resolution
Normally, no one can cast spells or activate abilities while another spell or ability is resolving.
If an effect explicitly says you may cast something as part of resolution, you do it during resolution, and the original spell/ability keeps resolving afterward. Players don’t get a normal priority pass in the middle unless the rules say so.
This is why “you can’t respond in the middle of resolving this” is usually correct, even if it makes someone sad.
Tournament shortcuts vs kitchen table assumptions
In real play, people don’t pass priority verbally after every micro-action, because we have jobs and families and would like to finish the game this century.
So Magic has shortcuts. The big one:
When a player casts a spell, it’s generally assumed they are passing priority unless they say they’re holding it.
That’s not a “gotcha.” It’s how games function at human speed.
The healthy habit
If you want to act in a specific window, say so clearly:
- “In your upkeep, before you draw…”
- “After attackers, before blocks…”
- “With that trigger on the stack…”
- “Hold priority, cast this, then respond with…”
You don’t need judge-level phrasing. You just need a timestamp.
A practical MTG timing rules cheat sheet
Here’s a quick mental checklist you can run mid-game:
- Is something resolving right now? If yes, you usually can’t do anything until it finishes.
- Is there an object on the stack? If yes, you can respond when you get priority.
- Did something just happen? If yes, remember: SBAs happen first, then triggers go on the stack, then priority.
- Are we in combat? Name the step. Combat is a whole staircase, not one room.
- Multiplayer? Triggers stack in turn order (APNAP). The last player’s triggers resolve first.
And yes, you will still forget sometimes. Magic is a large game. It contains multitudes. Mostly triggered abilities.
Wrap-up: learn the loop, win the arguments
If you understand:
- What priority is
- That SBAs and triggers happen before priority
- That the stack resolves only after everyone passes
- That steps matter
…then you understand the core of MTG timing rules.
Everything else is just applying those rules to increasingly unhinged board states.
When you’re ready, the next “spoke” articles to link into this hub are priority deep-dives, SBAs, replacement effects, and combat timing windows. This page is the map. Those are the neighborhoods where everyone gets lost.
