Flickermare 1WW
When ~ enters the battlefield, exile another target creature until ~ leaves the battlefield.
Evoke W
2/2
I believe this as worded permanently exiles a creature for W if you choose to resolve the sacrifice ability of evoke before the ETB ability.
Can anyone think of a clever workaround so this creature works as intended when evoked? i.e. the creature comes back
Thanks in advance
If you choose to sacrifice the creature before it exiles something, the creature it is targeting doesn't go anywhere (with the current wording). However, if you exile the creature, then sacrifice Flickermare, the targeted creature will come back as expected. It is still possible to stack the triggers incorrectly (looking at MTGO) but for the most part, your current wording works as intended without allowing for a permanent exile.
See the wording on Oblivion Ring to see how it would have to be worded to permanently exile something with Evoke.
Thank you, glad to hear that. I should have thought to check the oracle on Banishing Light/Banisher Priest! Perhaps WOTC would not create this due to the ease of mis-stacking the triggers, but I am happy enough.
One way I think to avoid the miss-stacking problem would be to word it like Oblivion Ring but delay the return to the next end step.
When CARDNAME enters the battlefield, you may exile another target creature.
When CARDNAME leaves the battlefield, at the beginning of the next end step, return the exiled card to the battlefield under its owner's control.
Evoke W
Much more wordy though. Miss-stacking should really only be a concern on MtGO, so the Banisher Priest wording is still probably preferable.
One minor concern: It should probably have "you may exile" and/or be restricted to a creature an opponent controls so the game can't potentially get stuck in a loop with three copies of this creature and end in a draw. https://www.youtube.com/watch?v=AGXG5rNe_tI
Private Mod Note
():
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Flickermare 1WW
When ~ enters the battlefield, exile another target creature until ~ leaves the battlefield.
Evoke W
2/2
I believe this as worded permanently exiles a creature for W if you choose to resolve the sacrifice ability of evoke before the ETB ability.
Can anyone think of a clever workaround so this creature works as intended when evoked? i.e. the creature comes back
Thanks in advance
If you choose to sacrifice the creature before it exiles something, the creature it is targeting doesn't go anywhere (with the current wording). However, if you exile the creature, then sacrifice Flickermare, the targeted creature will come back as expected. It is still possible to stack the triggers incorrectly (looking at MTGO) but for the most part, your current wording works as intended without allowing for a permanent exile.
See the wording on Oblivion Ring to see how it would have to be worded to permanently exile something with Evoke.
When CARDNAME enters the battlefield, you may exile another target creature.
When CARDNAME leaves the battlefield, at the beginning of the next end step, return the exiled card to the battlefield under its owner's control.
Evoke W
Much more wordy though. Miss-stacking should really only be a concern on MtGO, so the Banisher Priest wording is still probably preferable.
One minor concern: It should probably have "you may exile" and/or be restricted to a creature an opponent controls so the game can't potentially get stuck in a loop with three copies of this creature and end in a draw. https://www.youtube.com/watch?v=AGXG5rNe_tI