iMtG Server: Gathering

Magic (The Gathering) => Rules => Topic started by: Lilhek on December 21, 2013, 01:50:13 AM

Title: Tidebinder Mage
Post by: Lilhek on December 21, 2013, 01:50:13 AM
Whenever tidebinder Mage enters the battlefield and I tap something, then say I cloudshift it and select a new target, will the first creature I tapped remain tapped? Or will it untap?
Title: Re: Tidebinder Mage
Post by: Spencer Addington on December 21, 2013, 01:55:48 AM
{tidebinder mage}
Title: Re: Tidebinder Mage
Post by: Spencer Addington on December 21, 2013, 01:56:14 AM
It stays tapped.
Title: Re: Tidebinder Mage
Post by: Gorzo on December 21, 2013, 06:36:54 AM
The first creature will untap at it's control let's next upkeep. Once {Tidebinder Mage} leaves the battlefield (flickers out), no matter how long, it severs all ties with its previous existence on the battlefield. It re-enters as a totally new object, with no connection whatsoever of the previous Tidebinder Mage that flickered out (including what it was holding tapped down).
Title: Re: Tidebinder Mage
Post by: Kaleo42 on December 21, 2013, 01:34:50 PM
Permanents are untapped during the untap step not the upkeep.
Title: Re: Tidebinder Mage
Post by: Millionlittlee on December 21, 2013, 04:47:54 PM
What if you flicker it when it enters the battlefield in response to the trigger
Title: Re: Tidebinder Mage
Post by: Gorzo on December 21, 2013, 05:06:57 PM
Quote from: Kaleo42 on December 21, 2013, 01:34:50 PM
Permanents are untapped during the untap step not the upkeep.

Derp! Yes, untap not upkeep, lol brainless mistake on my part, thanks for the correction!

Quote from: Millionlittlee on December 21, 2013, 04:47:54 PM
What if you flicker it when it enters the battlefield in response to the trigger

In response to what trigger? Tidebinders ETB?
It won't work like {fiend hunter} if that's what you're asking. Fiend hunter works because he has an exile when enter trigger and a return when leaves trigger that can get screwed up on the stack with an instant speed flicker. Tidebinder has no "leaves the battlefield" trigger, and simply keeps the target of its ETB tapped as long as it's in play. If it flickers before that ETB resolves, it will still tap that creature, but there is no Tidebinder in existence anymore that is linked to it to prevent it from untapping at the next untap step.