How do Deadeye Navigator and Guilded Drake interact when you use the Navigator to "blink" the Drake?

Asked by coleman984 13 years ago

How do Deadeye NavigatorMTG Card: Deadeye Navigator and guilded-drake interact when you use the Navigator to "blink" the Drake? The question really is this. If I use the Navigator to "blink" the Drake does the ability go on the stack twice and because of the oracle text cause the Drake to be sac'd to the second Drake ETB effect? Meaning if I "blink" the Drake do I get a creature they control and they have to sacrifice the Drake? I believe the answer is: No because of "ability memory" meaning the first effect lost track of the Drake and does nothing so only the second one on the stack will successfully resolve. Is this correct?

coleman984 says... #1

May 19, 2012 5:55 a.m.

mafteechr says... #2

Gilded DrakeMTG Card: Gilded Drake's Oracle text reads:

When Gilded Drake enters the battlefield, exchange control of Gilded Drake and up to one target creature an opponent controls. If you don't make an exchange, sacrifice Gilded Drake. This ability can't be countered except by spells and abilities.

Your scenario is no different than just casting Gilded DrakeMTG Card: Gilded Drake. It has a single ability that triggers when it enters the battlefield (be it from the stack or from exile). You choose up to one target creature your opponent controls, and when the ability resolves, you either exchange control of Gilded DrakeMTG Card: Gilded Drake with the target creature, or you sacrifice Gilded DrakeMTG Card: Gilded Drake.

May 19, 2012 6:03 a.m.

coleman984 says... #3

Right but the ability is on the stack twice. When the first ability resolves the exchange happens but the second ability from when the Drake entered the battlefield the first time then resolves and no exchange is made, therefore the drake dies no?

May 19, 2012 6:06 a.m.

GoblinsInc says... #4

If you don't control the drake, you cannot sacrifice it.

May 19, 2012 6:08 a.m.

benzzer853 says... #5

When drake gets blinked no matter how many more triggers are on the stack they all disapear when he returns because he is considered to be a completely new creature not even soulbound with the navigtor

May 19, 2012 8:37 a.m.

Epochalyptik says... Accepted answer #6

You control a Deadeye NavigatorMTG Card: Deadeye Navigator and you resolve a Gilded DrakeMTG Card: Gilded Drake. The soulbond ability of Deadeye NavigatorMTG Card: Deadeye Navigator and the exchange ability of Gilded DrakeMTG Card: Gilded Drake both go onto the stack in the order you choose.

Say you opt to stack the soulbond ability over the exchange ability, meaning Gilded DrakeMTG Card: Gilded Drake will be paired with Deadeye NavigatorMTG Card: Deadeye Navigator before the exchange ability resolves.

Now, with the exchange ability on the stack, you blink Gilded DrakeMTG Card: Gilded Drake using its inherited activated ability. Gilded DrakeMTG Card: Gilded Drake reenters the battlefield and its ETB exchange ability triggers along with the soulbond ability of Deadeye NavigatorMTG Card: Deadeye Navigator (since the creatures lost their soulbond when the blink happened).

At this point, the first ETB exchange ability (on the bottom of the stack) will do nothing when it resolves. The Gilded DrakeMTG Card: Gilded Drake that was the source of that particular ability left the battlefield. When it reentered as part of the blink, it became an entirely new permanent.

This sequence of events really hasn't done anything besides cost you two extra mana. The original ETB exchange ability of Gilded DrakeMTG Card: Gilded Drake does nothing but the second instance of that ability will effectively replace it.

May 19, 2012 5:53 p.m.

Epochalyptik says... #7

@benzzer853: The abilities linked to the "old" Gilded DrakeMTG Card: Gilded Drake don't disappear. They just don't do anything because the object that they are trying to exchange doesn't exist in the zone it's expected to be in anymore. If those abilities had additional effects (such as "Draw a card.") those effects would still happen.

May 19, 2012 5:55 p.m.

This discussion has been closed