[fixed/closed]manifested aura + exile-return-to-bf effect
Posted: 16 Nov 2015, 08:32Describe the Bug:
If you use an exile-then-return-that-card-to-the-battlefield effect, whether immediate (as with Cloudshift) or delayed (as with Liberate), on a face-down manifested instant or sorcery (such as by Soul Summons), that card gets cast and put in your graveyard when it returns to the battlefield.
Which card did behave improperly ?
Cloudshift, Liberate, etc. Manifest itself isn't at fault.
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
FRF.
What exactly should be the correct behavior/interaction ?
400.4. Cards with certain card types can't enter certain zones.
400.4a If an instant or sorcery card would enter the battlefield, it remains in its previous zone.
So the exiled instant or sorcery should stay in exile. It definitely shouldn't cast itself.
Are any other cards possibly affected by this bug ?
There seem to be a lot of irritatingly-similar variants of exile-then-return-to-bf: blink_effect() (Cloudshift), remove_until_eot() (Liberate), obliviate() (Journey to Nowhere), and exile_permanents_and_auras_attached() (Oubliette) are the standard functions, but there's no doubt plenty of ad-hoc reimplementations.
On the targeting side, I doubt Auras will work right either; at best, you won't be able to attach them to creatures with shroud. And they should stay exiled too if there isn't anything they could legally attach to. (Rule 303.4g: If an Aura is entering the battlefield and there is no legal object or player for it to enchant, the Aura remains in its current zone, unless that zone is the stack. In that case, the Aura is put into its owner's graveyard instead of entering the battlefield.) -still bug
If you use an exile-then-return-that-card-to-the-battlefield effect, whether immediate (as with Cloudshift) or delayed (as with Liberate), on a face-down manifested instant or sorcery (such as by Soul Summons), that card gets cast and put in your graveyard when it returns to the battlefield.
Which card did behave improperly ?
Cloudshift, Liberate, etc. Manifest itself isn't at fault.
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
FRF.
What exactly should be the correct behavior/interaction ?
400.4. Cards with certain card types can't enter certain zones.
400.4a If an instant or sorcery card would enter the battlefield, it remains in its previous zone.
So the exiled instant or sorcery should stay in exile. It definitely shouldn't cast itself.
Are any other cards possibly affected by this bug ?
There seem to be a lot of irritatingly-similar variants of exile-then-return-to-bf: blink_effect() (Cloudshift), remove_until_eot() (Liberate), obliviate() (Journey to Nowhere), and exile_permanents_and_auras_attached() (Oubliette) are the standard functions, but there's no doubt plenty of ad-hoc reimplementations.
On the targeting side, I doubt Auras will work right either; at best, you won't be able to attach them to creatures with shroud. And they should stay exiled too if there isn't anything they could legally attach to. (Rule 303.4g: If an Aura is entering the battlefield and there is no legal object or player for it to enchant, the Aura remains in its current zone, unless that zone is the stack. In that case, the Aura is put into its owner's graveyard instead of entering the battlefield.) -still bug