[fixed/close]Purgatory returns to bf copy of exiled creature

[Aswan jaguar]

Describe the Bug:
Purgatory returns to battlefield a copy of an exiled creature not that creature so if this creature dies again and again multiple copies of it will be in the exile zone.
NOTE: when you use Purgatory 's ability in the cards exile menu to choose card from, creatures that have been returned to battlefield by it already aren't in there correctly.

Which card did behave improperly ?
Purgatory

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2015/3/25: Fate Reforged,duel

What exactly should be the correct behavior/interaction ?
Purgatory either return the same exiled creature or (if I am not wrong the workaround to clear the exile zone from it and put the copy/another in).

Are any other cards possibly affected by this bug ?
Nightveil Specter posted: here

[Gargaroz]

Please re-test this too as the code seems fine.

[Aswan jaguar]

In public version this is still bugged as is Nightveil Specter 's similar bug but since Korath says Nightveil Specter works in dev probably Purgatory works in dev version,too.Korath is this the case?

[Korath]

Still present as of a couple days ago, at least. Here's a build.

The bug can be stated a bit more clearly as "Purgatory doesn't remove creatures from exile as it puts them on the battlefield." The talk of copies is misleading; cards always become new objects when they change zones, and that's as it should be.

[Gargaroz]

Could you please look at the code? It's one of these case that the more I look and the less I understand whant's wrong.

[Korath]

Compare it to the case for CHOICE_NIGHTMARE in theros.c:card_ashiok_nightmare_weaver()'s EVENT_RESOLVE_ACTIVATION handler - there's no call to remove_card_from_rfg(). Putting that in should be enough to fix it.

(There's going to be other, much less common problems here - the card doesn't check exiled cards' owners, just assumes that control of Purgatory has never changed, and in particular hasn't changed between announcement and resolution of its trigger. It'll also have the same bug Ashiok, Nightmare Weaver currently does if it leaves the bf between announcement and resolution. That's currently very difficult to arrange since triggers don't go on the stack, but not wholly impossible - something triggering at the same time like Endless Wurm or Smokestack might be able to do it.)

[Gargaroz]

Fixed in 2bd36a6