400. General 편집
400.1. A zone is a place where objects can be during a game. There are normally seven zones: library, hand, battlefield, graveyard, stack, exile, and command. Some older cards also use the ante zone. Each player has his or her own library, hand, and graveyard. The other zones are shared by all players.
400.2. Public zones are zones in which all players can see the cards' faces, except for those cards that some rule or effect specifically allow to be face down. Graveyard, battlefield, stack, exile, ante, and command are public zones. Hidden zones are zones in which not all players can be expected to see the cards' faces. Library and hand are hidden zones, even if all the cards in one such zone happen to be revealed.
400.3. If an object would go to any library, graveyard, or hand other than its owner's, it goes to its owner's corresponding zone.
400.4. Cards with certain card types can't enter certain zones.
400.4a If an instant or sorcery card would enter the battlefield, it remains in its previous zone.
400.4b If a plane, vanguard, or scheme card would leave the command zone, it remains in the command zone.
400.5. The order of objects in a library, in a graveyard, or on the stack can't be changed except when effects or rules allow it. The same is true for objects arranged in face-down piles in other zones. Other objects in other zones can be arranged however their owners wish, although who controls those objects, whether they're tapped or flipped, and what other objects are attached to them must remain clear to all players.
400.6. If an object would move from one zone to another, determine what event is moving the object. If the object is moving to a public zone, all players look at it to see if it has any abilities that would affect the move. Then any appropriate replacement effects, whether they come from that object or from elsewhere, are applied to that event. If any effects or rules try to do two or more contradictory or mutually exclusive things to a particular object, that object's controller -- or its owner if it has no controller -- chooses which effect to apply, and what that effect does. (Note that multiple instances of the same thing may be mutually exclusive; for example, two simultaneous "destroy" effects.) Then the event moves the object.
400.7. An object that moves from one zone to another becomes a new object with no memory of, or relation to, its previous existence. There are seven exceptions to this rule:
400.7a Effects from spells, activated abilities, and triggered abilities that change the characteristics of a permanent spell on the stack continue to apply to the permanent that spell becomes.
400.7b Prevention effects that apply to damage from a permanent spell on the stack continue to apply to damage from the permanent that spell becomes.
400.7c If an ability of a permanent requires information about choices made as that permanent was cast as a spell, including what mana was spent to cast that spell, it uses information about the spell that became that permanent as it resolved.
400.7d Abilities that trigger when an object moves from one zone to another (for example, "When Rancor is put into a graveyard from the battlefield") can find the new object that it became in the zone it moved to when the ability triggered, if that zone is a public zone.
400.7e Abilities of Auras that trigger when the enchanted permanent leaves the battlefield can find the new object that Aura became in its owner's graveyard if it was put into that graveyard at the same time the enchanted permanent left the battlefield. It can also find the new object that Aura became in its owner's graveyard as a result of being put there as a state-based action for not being attached to a permanent. (See rule 704.5n.)
400.7f If an effect grants a nonland card an ability that allows it to be cast, that ability will continue to apply to the new object that card became after it moved to the stack as a result of being cast this way.
400.7g A resolving spell or activated ability can perform actions on an object that moved from one zone to another while that spell was being cast or that ability was being activated, if that object moved to a public zone.
400.8. If an object in the exile zone is exiled, it doesn't change zones, but it becomes a new object that has just been exiled.
400.9. If a face-up object in the command zone is turned face down, it becomes a new object.
400.10. An object is outside the game if it isn't in any of the game's zones. Outside the game is not a zone.
400.10a Cards in a player's sideboard are outside the game. See rule 100.4.
400.10b Some effects bring cards into a game from outside of it. Those cards remain in the game until it ends.
400.10c Cards outside the game can't be affected by spells or abilities, except for characteristic-defining abilities printed on them (see rule 604.3) and spells and abilities that allow those cards to be brought into the game.
400.11. Some effects instruct a player to do something to a zone (such as "Shuffle your hand into your library"). That action is performed on all cards in that zone. The zone itself is not affected.
401. Library 편집
401.1. When a game begins, each player's deck becomes his or her library.
401.2. Each library must be kept in a single face-down pile. Players can't look at or change the order of cards in a library.
401.3. Any player may count the number of cards remaining in any player's library at any time.
401.4. If an effect puts two or more cards on the top or bottom of a library at the same time, the owner of those cards may arrange them in any order. That library's owner doesn't reveal the order in which the cards go into his or her library.
401.5. If a spell or ability causes a card to be drawn while another spell is being cast, the drawn card is kept face down until that spell becomes cast (see rule 601.2h). The same is true with relation to another ability being activated.
401.6. Some effects tell a player to play with the top card of his or her library revealed, or say that a player may look at the top card of his or her library. If the top card of the player's library changes while a spell is being cast, the new top card won't be revealed and can't be looked at until the spell becomes cast (see rule 601.2h). The same is true with relation to an ability being activated.
401.7. If an effect causes a player to play with the top card of his or her library revealed, and that particular card stops being revealed for any length of time before being revealed again, it becomes a new object.
401.8. If an effect causes a player to put a card into a library "Nth from the top," and that library has fewer than N cards in it, the player puts that card on the bottom of that library.
402. Hand 편집
402.1. The hand is where a player holds cards that have been drawn. Cards can be put into a player's hand by other effects as well. At the beginning of the game, each player draws a hand of seven cards. (See rule 103, "Starting the Game.")
402.2. Each player has a maximum hand size, which is normally seven cards. A player may have any number of cards in his or her hand, but as part of his or her cleanup step, the player must discard excess cards down to the maximum hand size.
402.3. A player may arrange his or her hand in any convenient fashion and look at it as much as he or she wishes. A player can't look at the cards in another player's hand but may count those cards at any time.
403. Battlefield 편집
403.1. Most of the area between the players represents the battlefield. The battlefield starts out empty. Permanents a player controls are normally kept in front of him or her on the battlefield, though there are some cases (such as an Aura attached to another player's permanent) when a permanent one player controls is kept closer to a different player.
403.2. A spell or ability affects and checks only the battlefield unless it specifically mentions a player or another zone.
403.3. Permanents exist only on the battlefield. Every object on the battlefield is a permanent. See rule 110, "Permanents."
403.4. Whenever a permanent enters the battlefield, it becomes a new object and has no relationship to any previous permanent represented by the same card, except for the cases listed in rule 400.7. (This is also true for any objects entering any zone.)
403.5. Previously, the battlefield was called the "in-play zone." Cards that were printed with text that contains the phrases "in play," "from play," "into play," or the like are referring to the battlefield. Cards that were printed with that text have received errata in the Oracle card reference.
404. Graveyard 편집
404.1. A player's graveyard is his or her discard pile. Any object that's countered, discarded, destroyed, or sacrificed is put on top of its owner's graveyard, as is any instant or sorcery spell that's finished resolving. Each player's graveyard starts out empty.
404.2. Each graveyard is kept in a single face-up pile. A player can examine the cards in any graveyard at any time but normally can't change their order. Additional rules applying to sanctioned tournaments may allow a player to change the order of cards in his or her graveyard.
404.3. If an effect or rule puts two or more cards into the same graveyard at the same time, the owner of those cards may arrange them in any order.
405. Stack 편집
405.1. When a spell is cast, the physical card is put on the stack (see rule 601.2a). When an ability is activated or triggers, it goes on top of the stack without any card associated with it (see rules 602.2a and 603.3).
405.2. The stack keeps track of the order that spells and/or abilities were added to it. Each time an object is put on the stack, it's put on top of all objects already there.
405.3. If an effect puts two or more objects on the stack at the same time, those controlled by the active player are put on lowest, followed by each other player's objects in APNAP order (see rule 101.4). If a player controls more than one of these objects, that player chooses their relative order on the stack.
405.4. Each spell has all the characteristics of the card associated with it. Each activated or triggered ability that's on the stack has the text of the ability that created it and no other characteristics. The controller of a spell is the person who cast it. The controller of an activated ability is the player who activated it. The controller of a triggered ability is the player who controlled the ability's source when it triggered, unless it's a delayed triggered ability. To determine the controller of a delayed triggered ability, see rules 603.7d-f.
405.5. When all players pass in succession, the top (last-added) spell or ability on the stack resolves. If the stack is empty when all players pass, the current step or phase ends and the next begins.
405.6. Some things that happen during the game don't use the stack.
405.6a Effects don't go on the stack; they're the result of spells and abilities resolving. Effects may create delayed triggered abilities, however, and these may go on the stack when they trigger (see rule 603.7).
405.6b Static abilities continuously generate effects and don't go on the stack. (See rule 604, "Handling Static Abilities.") This includes characteristic-defining abilities such as "[This object] is red" (see rule 604.3).
405.6c Mana abilities resolve immediately. If a mana ability both produces mana and has another effect, the mana is produced and the other effect happens immediately. If a player had priority before a mana ability was activated, that player gets priority after it resolves. (See rule 605, "Mana Abilities.")
405.6d Special actions don't use the stack; they happen immediately. See rule 115, "Special Actions."
405.6e Turn-based actions don't use the stack; they happen automatically when certain steps or phases begin. They're dealt with before a player would receive priority (see rule 116.3a). Turn-based actions also happen automatically when each step and phase ends; no player receives priority afterward. See rule 703.
405.6f State-based actions don't use the stack; they happen automatically when certain conditions are met. See rule 704. They are dealt with before a player would receive priority. See rule 116.5.
405.6g A player may concede the game at any time. That player leaves the game immediately. See rule 104.3a.
405.6h If a player leaves a multiplayer game, objects may leave the game, cease to exist, change control, or be exiled as a result. These actions happen immediately. See rule 800.4a.
406. Exile 편집
406.1. The exile zone is essentially a holding area for objects. Some spells and abilities exile an object without any way to return that object to another zone. Other spells and abilities exile an object only temporarily.
406.2. To exile an object is to put it into the exile zone from whatever zone it's currently in. An exiled card is a card that's been put into the exile zone.
406.3. Exiled cards are, by default, kept face up and may be examined by any player at any time. Cards "exiled face down" can't be examined by any player except when instructions allow it.
406.4. Exiled cards that might return to the battlefield or any other zone should be kept in separate piles to keep track of their respective ways of returning. Exiled cards that may have an impact on the game due to their own abilities (such as cards with haunt) or the abilities of the cards that exiled them should likewise be kept in separate piles.
406.5. An object may have one ability printed on it that causes one or more cards to be exiled, and another ability that refers either to "the exiled cards" or to cards "exiled with [this object]." These abilities are linked: the second refers only to cards that have been exiled due to the first. See rule 607, "Linked Abilities."
406.6. If an object in the exile zone becomes exiled, it doesn't change zones, but it becomes a new object that has just been exiled.
406.7. Previously, the exile zone was called the "removed-from-the-game zone." Cards that were printed with text that "removes [an object] from the game" exiles that object. The same is true for cards printed with text that "sets [an object] aside." Cards that were printed with that text have received errata in the Oracle card reference.
407. Ante 편집
407.1. Earlier versions of the Magic rules included an ante rule as a way of playing "for keeps." Playing Magic games for ante is now considered an optional variation on the game, and it's allowed only where it's not forbidden by law or by other rules. Playing for ante is strictly forbidden under the Magic : The Gathering Tournament Rules http://www.wizards.com/WPN/Events/Rules.aspx
407.2. When playing for ante, each player puts one random card from his or her deck into the ante zone after determining which player goes first but before players draw any cards. Cards in the ante zone may be examined by any player at any time. At the end of the game, the winner becomes the owner of all the cards in the ante zone.
407.3. A few cards have the text "Remove [this card] from your deck before playing if you're not playing for ante." These are the only cards that can add or remove cards from the ante zone or change a card's owner.
407.4. To ante an object is to put that object into the ante zone from whichever zone it's currently in. The owner of an object is the only person who can ante that object.
408. Command 편집
408.1. The command zone is a game area reserved for certain specialized objects that have an overarching effect on the game, yet are not permanents and cannot be destroyed.
408.2. Emblems may be created in the command zone. See rule 113, "Emblems."
408.3. In the Planechase, Vanguard, Commander, and Archenemy casual variants, nontraditional Magic cards and/or specially designated cards start the game in the command zone. Each variant has its own rules regarding such cards. See section 9, "Casual Variants."