崔納的絕境
結界 ～傳紀
（於此傳紀進戰場時及於你抽牌步驟後，加一個學問指示物。到III後犧牲之。）
I, II — 崔納的絕境向每位對手各造成2點傷害且你獲得2點生命。
III — 派出一個X/X黑色夢魘／驚懼獸衍生生物，X為你總生命的一半，小數點後進位。它對你造成X點傷害。
I, II — 崔納的絕境向每位對手各造成2點傷害且你獲得2點生命。
III — 派出一個X/X黑色夢魘／驚懼獸衍生生物，X為你總生命的一半，小數點後進位。它對你造成X點傷害。
standard
future
historic
gladiator
pioneer
modern
legacy
pauper
vintage
penny
commander
brawl
alchemy
paupercommander
duel
oldschool
premodern
Rulings
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.
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 III chapter ability to trigger, but I and II won’t trigger again.
If another effect causes the Nightmare Horror token’s power or toughness to be a number other than X immediately after it enters the battlefield, the amount of damage it deals to you is still X, not its modified power or toughness.
If counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters. Removing lore counters won’t cause a previous chapter ability to trigger.
Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities—in the Dominaria set, this is always three—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.
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.
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.
If an effect such as that of Anointed Procession causes the final chapter ability of Chainer’s Torment to create two Nightmare Horror tokens, each will deal X damage to you.
In a Two-Headed Giant game, the first chapter abilities of Chainer’s Torment each cause the opposing team to lose 4 life and you to gain 2 life.
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.
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 III chapter ability to trigger, but I and II won’t trigger again.
If another effect causes the Nightmare Horror token’s power or toughness to be a number other than X immediately after it enters the battlefield, the amount of damage it deals to you is still X, not its modified power or toughness.
If counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters. Removing lore counters won’t cause a previous chapter ability to trigger.
Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities—in the Dominaria set, this is always three—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.
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.
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.
If an effect such as that of Anointed Procession causes the final chapter ability of Chainer’s Torment to create two Nightmare Horror tokens, each will deal X damage to you.
In a Two-Headed Giant game, the first chapter abilities of Chainer’s Torment each cause the opposing team to lose 4 life and you to gain 2 life.
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.
Rulings
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.
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 III chapter ability to trigger, but I and II won’t trigger again.
If another effect causes the Nightmare Horror token’s power or toughness to be a number other than X immediately after it enters the battlefield, the amount of damage it deals to you is still X, not its modified power or toughness.
If counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters. Removing lore counters won’t cause a previous chapter ability to trigger.
Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities—in the Dominaria set, this is always three—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.
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.
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.
If an effect such as that of Anointed Procession causes the final chapter ability of Chainer’s Torment to create two Nightmare Horror tokens, each will deal X damage to you.
In a Two-Headed Giant game, the first chapter abilities of Chainer’s Torment each cause the opposing team to lose 4 life and you to gain 2 life.
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.
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 III chapter ability to trigger, but I and II won’t trigger again.
If another effect causes the Nightmare Horror token’s power or toughness to be a number other than X immediately after it enters the battlefield, the amount of damage it deals to you is still X, not its modified power or toughness.
If counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters. Removing lore counters won’t cause a previous chapter ability to trigger.
Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities—in the Dominaria set, this is always three—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.
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.
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.
If an effect such as that of Anointed Procession causes the final chapter ability of Chainer’s Torment to create two Nightmare Horror tokens, each will deal X damage to you.
In a Two-Headed Giant game, the first chapter abilities of Chainer’s Torment each cause the opposing team to lose 4 life and you to gain 2 life.
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.
Votre collection ? vos decks ?
Envie de gérer votre collection et/ou créer des decks ?
0.15€