Rule evolution
Rule 117.5
Previously numbered 115.5, 116.5.
Earliest archived Rules release: 2009-10-01 · 0 wording revisions · 2 renumberings
Earliest archived Rules release115.5Details
Each time a player would get priority, the game first performs all applicable state-based actions as a single event (see rule 704, "State-Based Actions"), then repeats this process until no state-based actions are performed. Then triggered abilities are put on the stack (see rule 603, "Handling Triggered Abilities"). These steps repeat in order until no further state-based actions are performed and no abilities trigger. Then the player who would have received priority does so.
Renumbered
115.5→ 116.5DetailsPreviously
1. Game Concepts
115. Timing and PriorityThen
1. Game Concepts
116. Timing and PriorityEach time a player would get priority, the game first performs all applicable state-based actions as a single event (see rule 704, "State-Based Actions"), then repeats this process until no state-based actions are performed. Then triggered abilities are put on the stack (see rule 603, "Handling Triggered Abilities"). These steps repeat in order until no further state-based actions are performed and no abilities trigger. Then the player who would have received priority does so.
Renumbered
116.5→ 117.5DetailsPreviously
1. Game Concepts
116. Timing and PriorityThen
1. Game Concepts
117. Timing and PriorityEach time a player would get priority, the game first performs all applicable state-based actions as a single event (see rule 704, “State-Based Actions”), then repeats this process until no state-based actions are performed. Then triggered abilities are put on the stack (see rule 603, “Handling Triggered Abilities”). These steps repeat in order until no further state-based actions are performed and no abilities trigger. Then the player who would have received priority does so.