아즈골 침략 (March of the Machine) - Gatherer

SIMPLE ADVANCED Random Card Settings Language Help

아즈골 침략

Community Rating:

Community Rating: 5 / 5 (0 votes)

Click here to view ratings and comments.

Oracle Printed

Card Name:

아즈골 침략

Mana Cost:

Mana Value:

Types:

전투 — 공성전

Card Text:

(공성전이 들어오면서, 이를 보호할 상대를 선택한다. 당신 및 다른 플레이어들은 공성전을 공격할 수 있다. 공성전이 패배할 때, 그 공성전을 추방한 후, 변신된 상태로 그 카드를 발동한다.)

아즈골 침략이 전장에 들어오면서, 플레이어를 목표로 정한다. 그 플레이어는 생물 또는 플레인즈워커 한 개를 희생하고 생명 1점을 잃는다.

Expansion:

March of the Machine

Rarity:

Uncommon

Card Number:

232a

Artist:

Joshua Raphael

Language:

Korean

Rulings

4/14/2023	Ashen Reaper's ability triggers at the beginning of each of your end steps, even if nothing has entered any graveyard that turn. The ability checks as it resolves whether to put a +1/+1 counter on Ashen Reaper or not. This means the ability will count any permanent that's put into a graveyard in response to the ability.
4/14/2023	The ability will count any permanent that was put into a graveyard, including token permanents.
4/14/2023	If a nontoken permanent is put into a graveyard, it doesn't matter what happens to the permanent card afterward. Ashen Reaper's ability will count it even if the card has left the graveyard by the time the ability resolves.
4/14/2023	Sieges each have an intrinsic triggered ability. That ability is "When the last defense counter is removed from this permanent, exile it, then you may cast it transformed without paying its mana cost."
4/14/2023	As a Siege enters the battlefield, its controller chooses an opponent to be its protector.
4/14/2023	A Siege's controller can't be its protector. If a Siege's protector ever gains control of it, they choose a new player to be its protector. This is a state-based action.
4/14/2023	If a non-battle permanent that is already on the battlefield become a copy of a Siege, its controller chooses one of their opponents to be that battle's protector. However, it will most likely be put into its owner's graveyard because it has no defense counters (see below).
4/14/2023	A battle's "defense" is displayed in the bottom right corner of the card. A battle enters the battlefield with that number of defense counters. If another permanent enters the battlefield as a copy of a battle, it also enters with that number of defense counters.
4/14/2023	Only creatures controlled by a battle's protector can block creatures that are attacking that battle. This means a Siege's controller can never assign creatures to block for it.
4/14/2023	A battle can be dealt damage and be target of spells and/or abilities that target "any target."
4/14/2023	Damage dealt to a battle causes that many defense counters to be removed from it.
4/14/2023	A battle can be attacked by all players other than its protector. Notably, this means a Siege's controller can attack it.
4/14/2023	If a battle has no defense counters, and it isn't the source of a triggered ability that has triggered but not yet left the stack, that battle is put into its owner's graveyard. This is a state-based action. This doesn't cause a Siege's intrinsic triggered ability to trigger.
4/14/2023	If a Siege never had defense counters on it (perhaps because a permanent became a copy of one), it can't have its last defense counter removed. It will be put into its owner's graveyard. You won't exile it or cast the other face.
4/14/2023	If a token or a card that isn't represented by a transforming double-faced card becomes a copy of a Siege, it can't be cast as its triggered ability resolves. It will remain in exile. If it's a token, it will cease to exist the next time state-based actions are performed.
4/14/2023	If a permanent that is represented by a transforming double-faced card becomes a copy of a Siege, it will be exiled as that Siege's triggered ability resolves, then it will be cast transformed. Note that this applies only to transforming double-faced cards, not to modal double-faced cards that can normally be played using either face.
4/14/2023	In a multiplayer game, if the protector of a battle leaves the game and that battle is not currently being attacked, its controller chooses a new protector for it as a state-based action. If it is being attacked, its controller chooses a new protector for it once no creatures are attacking it. This means that it continues to be attacked and can be dealt combat damage as normal.
4/14/2023	If a battle that's being attacked somehow stops being a battle, it is removed from combat. Similarly, if its controller changes in the middle of combat, it is removed from combat.
4/14/2023	Battles can't attack or block, even if one also becomes a creature. If an attacking or blocking creature somehow becomes a battle in addition to being a creature, it is removed from combat.