| 姓名 | 哈拉德一統妖精 
|
|---|---|
| 图案 | Harald Unites the Elves |
| 类型 | 結界 ～傳紀 |
| 描述 | （於此傳紀進戰場時及於你抽牌步驟後，加一個學問指示物。到III後犧牲之。） I — 磨三張牌。你可以將一張妖精或泰瓦牌從你的墳墓場放進戰場。 II — 在每個由你操控的妖精上各放置一個+1/+1指示物。 III — 本回合中，每當一個由你操控的妖精攻擊時，目標由對手操控的生物得-1/-1直到回合結束。 |
| 艺术家 | Ryan Pancoast |
| 版 | 卡尔德海姆促销 #213p |
| Wallpaper |  download |
| 图片 |  download |
等级列表
No Rank
自己评分
哈拉德一統妖精, 結界 ～傳紀, 设计者 Ryan Pancoast 首次发布于 Jan, 2021 在编辑中 Kaldheim 并准确地印在 3 不同的形状. 见游戏 1 格式: Commander. 目前以最低价出售 ¥ 0.86.
这张卡在《魔法风云》中的精灵部落套牌中会很有益处，提供了卡牌优势、生物强化和干扰的混合效果。虽然《哈拉德团结精灵》提供了独特而有趣的效果，但对于精灵套牌来说，可能有更强大的选择，比如《齐集公司》或《引领猎途》，它们提供了即时价值，而不需要等待传奇的进展，这使它们在竞技比赛中可能是更好的选择。
05/02/21
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.
05/02/21
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.
05/02/21
Conversely, the triggered ability created by the chapter III ability will trigger whenever any Elf you control attacks that turn, even if you didn’t control that Elf as the chapter III ability resolved.
05/02/21
For the chapter I ability, the Elf or Tyvar card you put onto the battlefield can be one of the cards you just milled, or it may be one that was already in your graveyard.
05/02/21
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.
05/02/21
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.
登录并加入对话
— 评论0
成为第一个发表评论的人