Battle for Bretagard
Enchantment — Saga
(As this Saga enters and after your draw step, add a lore counter. Sacrifice after III.)
I — Create a 1/1 white Human Warrior creature token.
II — Create a 1/1 green Elf Warrior creature token.
III — Choose any number of artifact tokens and/or creature tokens you control with different names. For each of them, create a token that's a copy of it.
I — Create a 1/1 white Human Warrior creature token.
II — Create a 1/1 green Elf Warrior creature token.
III — Choose any number of artifact tokens and/or creature tokens you control with different names. For each of them, create a token that's a copy of it.
フォーマット
スタンダード : 不可パイオニア : 可能モダン : 可能レガシー : 可能ヴィンテージ : 可能パウパー : 不可統率者戦 : 可能デジタル専用フォーマット
アルケミー : 不可エクスプローラー : 可能ヒストリック : 可能タイムレス : 可能リミテッド評価値
リミテッド評価値が存在しません。
カード裁定
2021/02/05
原文The chapter III ability doesn't target any of the tokens. You choose which ones you're copying as the ability resolves.
2021/02/05
原文Unless the effect that creates a token specifies a different name, the name of a token is the same as its creature types plus the word "Token". In particular, a Human Warrior creature token has a different name than an Elf Warrior creature token, and you may create a copy of each using the chapter III ability.
2021/02/05
原文Each token you create copies the original characteristics of the token it's copying as stated by the effect that created that token. The newly created token doesn't copy whether the original token is tapped or untapped, whether it has any counters on it, whether it has any Auras and/or Equipment attached to it, or any non-copy effects that changed its power, toughness, types, color, and so on.
2021/02/05
原文If the original token is copying something else, the token you create will use the copiable values of the original token. In most cases, it will be a copy of whatever the original token is copying. If it's copying a permanent or card with in its mana cost, X is 0.
2021/02/05
原文Any enters-the-battlefield abilities of tokens you create will trigger when they enter the battlefield. Any "As [this permanent] enters the battlefield" or "[This permanent] enters the battlefield with" abilities of the tokens will also work.
2021/02/05
原文As a Saga enters the battlefield, its controller puts a lore counter on it. As your precombat main phase begins (immediately after your draw step), you put another lore counter on each Saga you control. Putting a lore counter on a Saga in either of these ways doesn't use the stack.
2021/02/05
原文Each symbol on the left of a Saga's text box represents a chapter ability. A chapter ability is a triggered ability that triggers when a lore counter that is put on the Saga causes the number of lore counters on the Saga to become equal to or greater than the ability's chapter number. Chapter abilities are put onto the stack and may be responded to.
2021/02/05
原文A chapter ability doesn't trigger if a lore counter is put on a Saga that already had a number of lore counters greater than or equal to that chapter's number. For example, the third lore counter put on a Saga causes the chapter III ability to trigger, but chapters I and II won't trigger again.
2021/02/05
原文Once a chapter ability has triggered, the ability on the stack won't be affected if the Saga gains or loses counters, or if it leaves the battlefield.
2021/02/05
原文If multiple chapter abilities trigger at the same time, their controller puts them on the stack in any order. If any of them require targets, those targets are chosen as you put the abilities on the stack, before any of those abilities resolve.
2021/02/05
原文Removing lore counters won't cause a previous chapter ability to trigger. If lore counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives more lore counters.
2021/02/05
原文Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities, the Saga's controller sacrifices it as soon as its chapter ability has left the stack, most likely by resolving or being countered. This state-based action doesn't use the stack.
data from gatherer