Subgame: Difference between revisions
Jump to navigation
Jump to search
>Murgatroid99 m (formatting) |
>Murgatroid99 (Added a missing rule) |
||
| Line 12: | Line 12: | ||
**'''715.4.''' All objects in the main game and all cards outside the main game are considered outside the subgame (except those specifically brought into the subgame). All players not currently in the subgame are considered outside the subgame. | **'''715.4.''' All objects in the main game and all cards outside the main game are considered outside the subgame (except those specifically brought into the subgame). All players not currently in the subgame are considered outside the subgame. | ||
***'''715.4a''' Some effects can bring cards into a game from outside of it. If a card is brought into a subgame from a main game, abilities in the main game that trigger on objects leaving a main-game zone will trigger, but they won’t be put onto the stack until the main game resumes. | ***'''715.4a''' Some effects can bring cards into a game from outside of it. If a card is brought into a subgame from a main game, abilities in the main game that trigger on objects leaving a main-game zone will trigger, but they won’t be put onto the stack until the main game resumes. | ||
***'''715.4b''' A player's main-game counters aren't considered part of the subgame, although the player will still have them when the main game resumes. Similarly, any counters a player gets during a subgame will cease to exist when the subgame ends. | |||
**'''715.5.''' At the end of a subgame, each player takes all cards he or she owns that are in the subgame other than those in the subgame command zone, puts them into his or her main-game library, then shuffles them. This includes cards in the subgame’s [[exile]] zone. Except as specified in rules 715.5a–c, all other objects in the subgame cease to exist, as do the zones created for the subgame. The main game continues from the point at which it was discontinued: First, the spell or ability that created the subgame finishes resolving, even if it was created by a spell card that’s no longer on the stack. Then, if any main-game abilities triggered while the subgame was in progress due to cards being removed from the main game, those abilities are put onto the stack.{{CR Example|If a card was brought into the subgame either from the main game or from outside the main game, that card will be put into its owner’s main-game library when the subgame ends.}} | **'''715.5.''' At the end of a subgame, each player takes all cards he or she owns that are in the subgame other than those in the subgame command zone, puts them into his or her main-game library, then shuffles them. This includes cards in the subgame’s [[exile]] zone. Except as specified in rules 715.5a–c, all other objects in the subgame cease to exist, as do the zones created for the subgame. The main game continues from the point at which it was discontinued: First, the spell or ability that created the subgame finishes resolving, even if it was created by a spell card that’s no longer on the stack. Then, if any main-game abilities triggered while the subgame was in progress due to cards being removed from the main game, those abilities are put onto the stack.{{CR Example|If a card was brought into the subgame either from the main game or from outside the main game, that card will be put into its owner’s main-game library when the subgame ends.}} | ||
***'''715.5a''' At the end of a subgame of a Planechase game, the face-up plane card or phenomenon card is turned face down and put on the bottom of its owner’s planar deck. Then each player moves his or her planar deck from the subgame command zone to the main-game command zone and shuffles it. | ***'''715.5a''' At the end of a subgame of a Planechase game, the face-up plane card or phenomenon card is turned face down and put on the bottom of its owner’s planar deck. Then each player moves his or her planar deck from the subgame command zone to the main-game command zone and shuffles it. | ||
Revision as of 15:41, 16 October 2014
Template:Navigation CR Lua error in Module:CR at line 549: Unknown error, multiple lookups .