Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
MagicCompRules_20121001.rtf
Скачиваний:
0
Добавлен:
01.03.2025
Размер:
2.57 Mб
Скачать

306. Planeswalkers

306.1. A player who has priority may cast a planeswalker card from his or her hand during a main phase of his or her turn when the stack is empty. Casting a planeswalker as a spell uses the stack. (See rule 601, “Casting Spells.”)

306.2. When a planeswalker spell resolves, its controller puts it onto the battlefield under his or her control.

306.3. Planeswalker subtypes are always a single word and are listed after a long dash: “Planeswalker — Jace.” Each word after the dash is a separate subtype. Planeswalker subtypes are also called planeswalker types. Planeswalkers may have multiple subtypes. See rule 205.3j for the complete list of planeswalker types.

306.4. If two or more planeswalkers that share a planeswalker type are on the battlefield, all are put into their owners’ graveyards as a state-based action. This is called the “planeswalker uniqueness rule.” See rule 704.

306.5. Loyalty is a characteristic only planeswalkers have.

306.5a The loyalty of a planeswalker not on the battlefield is equal to the number printed in its lower right corner.

306.5b A planeswalker is treated as if its text box included, “This permanent enters the battlefield with a number of loyalty counters on it equal to its printed loyalty number.” This ability creates a replacement effect (see rule 614.1c).

306.5c The loyalty of a planeswalker on the battlefield is equal to the number of loyalty counters on it.

306.5d Each planeswalker has a number of loyalty abilities, which are activated abilities with loyalty symbols in their costs. Loyalty abilities follow special rules: A player may activate a loyalty ability of a permanent he or she controls any time he or she has priority and the stack is empty during a main phase of his or her turn, but only if none of that permanent’s loyalty abilities have been activated that turn. See rule 606, “Loyalty Abilities.”

306.6. Planeswalkers can be attacked. (See rule 508, “Declare Attackers Step.”)

306.7. If noncombat damage would be dealt to a player by a source controlled by an opponent, that opponent may have that source deal that damage to a planeswalker the first player controls instead. This is a redirection effect (see rule 614.9) and is subject to the normal rules for ordering replacement effects (see rule 616). The opponent chooses whether to redirect the damage as the redirection effect is applied.

306.8. Damage dealt to a planeswalker results in that many loyalty counters being removed from it.

306.9. If a planeswalker’s loyalty is 0, it’s put into its owner’s graveyard. (This is a state-based action. See rule 704.)

307. Sorceries

307.1. A player who has priority may cast a sorcery card from his or her hand during a main phase of his or her turn when the stack is empty. Casting a sorcery as a spell uses the stack. (See rule 601, “Casting Spells.”)

307.2. When a sorcery spell resolves, the actions stated in its rules text are followed. Then it’s put into its owner’s graveyard.

307.3. Sorcery subtypes are always a single word and are listed after a long dash: “Sorcery — Arcane.” Each word after the dash is a separate subtype. The set of sorcery subtypes is the same as the set of instant subtypes; these subtypes are called spell types. Sorceries may have multiple subtypes. See rule 205.3k for the complete list of spell types.

307.4. Sorceries can’t enter the battlefield. If a sorcery would enter the battlefield, it remains in its previous zone instead.

307.5. If a spell, ability, or effect states that a player can do something only “any time he or she could cast a sorcery,” it means only that the player must have priority, it must be during the main phase of his or her turn, and the stack must be empty. The player doesn’t need to have a sorcery he or she could actually cast. Effects that would prevent that player from casting a spell or casting a sorcery don’t affect the player’s capability to perform that action (unless the action is actually casting a spell or casting a sorcery).

307.5a Similarly, if an effect checks to see if a spell was cast “any time a sorcery couldn’t have been cast,” it’s checking only whether the spell’s controller cast it without having priority, during a phase other than his or her main phase, or while another object was on the stack.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]