There are no comments yet for this card.
I LOVE this card, but have one HUGE gripe about how the rulings on this have worked out:
SO...if you attach to a creature and then bounce that creature, the creature is fine. OK, I get that. The creature isn't there to be sac'd.
BUT...if someone bounces or destroys THIS EQUIPMENT while it's attached to a creature, then you have to sac that creature. How does this make sense? If the wargear isn't on the battlefield (either because it's in the GY, exiled, or in your hand), then why does its effect trigger?
Makes no sense to me. Also inconsistent application of the game principles. They need to fix this ruling.
Posted By:
Paleopaladin
(12/18/2013 3:06:25 PM)
@Paleopaladin: it makes total sense. when the wargear gets bounced, it unattaches from the creature since it can't stay attached if it's not on the battlefield, and its trigger goes on the stack as the wargear leaves the battlefield. Just like creatures ETB abilities still happen even if you sacrifice them before the ability resolves. Since it goes onto the stack before the relevant permanent leaves whatever zone it's in, the trigger will still resolve. In both of your scenarios, the grafted wargear trigger goes onto the stack. If it helps, you can think about the flavor that Zulp suggested: If the creature gets returned to hand, it goes out of existence, so isn't hurt by the implanted armor being ripped out. The armor harmlessly falls to the ground as the creature disappears. However, if you make the wargear disappear, the skeletal structure, nervous system etc. that were bonded to, and relying on the armor to function, collapse and the creature dies.
I'm not entirely sure how this w... (see all)
Posted By:
Aremath
(3/21/2014 4:33:13 PM)