|
5 months ago ::
Jan 02, 2013 - 8:49PM
#1
|
|
|
I have Incandescent Soulstoke  on the battlefield, and used its ability to put Hateflayer  from my hand onto the battlefield. Can I then use Reroute  to redirect the sacrifice to my opponents creature, say a 1/1 token for instance, and keep my Hateflayer? If so, can my Hateflayer keep the haste ability to tap/attack, and then redirect the sacrifice before end of turn or would I have to redirect both the haste and sacrifice?
|
|
|
|
5 months ago ::
Jan 02, 2013 - 8:56PM
#2
|
Date Joined:
Dec 13, 2011
|
Incandescent Soulstoke does not target anything (note the lack of the word "target" in the ability's text), so its ability is not a legal target for Reroute. The ability also creates a delayed trigger that will go on the stack at the beginning of the next end step. When that trigger resolves, you must sacrifice the creature you put onto the battlefield. If you can counter  the sacrifice trigger or end the turn  while it's on the stack, it won't trigger again and you can keep your creature (with haste).
|
|
|
|
5 months ago ::
Jan 02, 2013 - 8:56PM
#3
|
Date Joined:
Dec 31, 2012
|
no i had a question about exileation at end of turn you can only avoid it with cards that skip past the rest of the turn sundial of the infinate  right before your end step.
|
|
|
|
5 months ago ::
Jan 02, 2013 - 8:58PM
#4
|
Date Joined:
Sep 17, 2005
|
Incandescent Soulstoke does not target anything (note the lack of the word "target" in the ability's text), so while you can attempt to Reroute the ability and draw a card, it won't have any effect on what the ability does. At the beginning of the next end step, the sacrifice trigger will go on the stack, and when it resolves you must sacrifice the creature you put onto the battlefield. If you can counter the sacrifice trigger or end the turn while it's on the stack, it won't trigger again and you can keep your creature (with haste).
No, you can't use Reroute on anything that does not have exactly one target.
|
|
|
|
5 months ago ::
Jan 02, 2013 - 8:58PM
#5
|
Date Joined:
Dec 13, 2011
|
no i had a question about exileation at end of turn you can only avoid it with cards that skip past the rest of the turn sundial of the infinate right before your end step.
If you end the turn before the end step then the trigger will wait for the next end step to actually occur. If you end the turn after the sacrifice trigger is put on the stack, it won't trigger again.
|
|
|
|
5 months ago ::
Jan 02, 2013 - 9:03PM
#6
|
Date Joined:
Dec 31, 2012
|
it says
Exile all spells and abilities on the stack
and that step hasent taken place so it isnt resolved yet
|
|
|
|
5 months ago ::
Jan 02, 2013 - 9:12PM
#7
|
|
|
So by tapping Sundial of the Infinite at the start of my end step and after the sacrifice triggers, I would never have to sacrifice my Hateflayer , even at the next end step after my turn ends?
|
|
|
|
5 months ago ::
Jan 02, 2013 - 9:14PM
#8
|
Date Joined:
Dec 31, 2012
|
no right before it starts so in combat
if you wait it is exiled at the begining
|
|
|
|
5 months ago ::
Jan 02, 2013 - 9:24PM
#9
|
Date Joined:
Sep 16, 2009
|
Aldekeyser's responses are confusing me, so I'll make it perfectly clear: Incandescent Soulstoke sets up a delayed triggered ability, that only ever triggers once - at the beginning of the next end step. If the ability is countered or stopped in some way after triggering, it will never trigger again. With that in mind, if you activate Sundial of the Infinite before the delayed trigger has even triggered, it will remain in waiting until the next end step to occur - likely your opponents - and then it will trigger, and you will have to sacrifice the card you put out. However, if you activate Sundial of the Infinite in response to the delayed trigger - that is, you actually let it have its one and only trigger first before ending the turn - then you'll never have to sacrifice the elemental to that delayed trigger.
|
|
|
|
5 months ago ::
Jan 02, 2013 - 9:26PM
#10
|
Date Joined:
Dec 31, 2012
|
with the delayed trigger being part of the ability it wont fully resolve untill the end step then is exiled off the stack permanantly
|
|
|
