[waitlisted]Angelic Renewal-bad triggers-Commander

[HarlequinCasts]

Describe the Bug:
1) Angelic Renewal triggers off opponents creatures. It triggers and you can get a prompt, but trying to return the opponents creature will not actually bring it back. This trigger seems similar to the second trigger mentioned in #2 below.

2) Angelic Renewal triggers twice off your own creatures. Once when you creature dies. Then you activate the trigger and return your creature. Then it will trigger again with the prompt and everything but fizzle at that point.

3) Using Angelic Renewal on your EDH Commander can return them to the battlefield as a regular creature and not with a commander legacy card. (Their damage will not count as commander damage). Perhaps this is a problem with the ordering of the remove from game commander trigger and the renewal trigger? Or with the Angelic Renewal simply creating a copy?

Save files for regular creatures and commanders attached below.

Which card did behave improperly ?
Angelic Renewal

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
m15 mini 4

What exactly should be the correct behavior/interaction ?
return one of your recently dead creatures to the battlefield including your Commander.

Are any other cards possibly affected by this bug ?
NA

[HarlequinCasts]

Possibly worth noting that if you do something a little crazy like fetch Angelic Renewal using an Academy Rector in response to a board wipe, and then use Angelic Renewal to bring back your commander you can get two copies of your commander in play and invoke the legend rule. (One is your commander, the other is a regular legendary creature version of your commander). This causes your commander to die several times...

This was the original corner case that caused me to investigate Angelic Renewal.

[Nexhro]

Regarding bug 3: have you tested how the legacy card behaves when you choose to not return the commander to the command zone?

Choosing to return it is a replacement effect and shouldn't trigger abilities that trigger off dying creatures, anyways. (Thread regarding dying commanders triggering such abilities here)

[HarlequinCasts]

Yeah so when you choose to return the commander to the command zone with Angelic Renewal in play a couple things happen which you can see in the screenshot below.

The commander goes to the graveyard and you have an EDH Commander mandatory trigger and an Angelic Renewal trigger. Resolving the EDH trigger first, the commander goes to the command zone, and then the Angelic Renewal trigger prompts you to reanimate your commander but it doesnt actually do anything since there is no longer a target. (Not perfect but it works)

Resolving the Angelic Renewal trigger first you get back your commander but it no longer has the EDH Commander card associated with it. From that point on its just a regular legendary creature and you cannot cast your commander again. (This is a big problem)

If however you passed on returning your commander to the command zone Angelic Renewal and all EDH commander cards can be resolved correctly. You get the commander back in play, and it has the commander legacy card associated with it. (This is the correct way this interaction should work in a real game, it has to go to the graveyard).

So yes like in the other bug report you linked, the fact that commanders bounce into the grave yard is a big part of the problem here.

[Aswan jaguar]

- About the 2nd bug the 2nd trigger is not so innocent as if you have a creature into the graveyard with the same name with the one you renewed the first time it will bring back the 2nd creature to the battlefield,too.

- The problem regarding bug 3 has nothing to do with Angelic Renewal but as Nexhro says it had to do with the bug he reported about Commanders that go to graveyard before and then EDH card triggers.

Maybe a similar approach to regeneration engine code is needed as regeneration doesn't let the creature go to graveyard,it triggers first but needs to be expanded to trigger to exiled commanders?Of course if that can be feasible or worth the trouble is for devs to answer.If that is rules wise to begin with.

[Gargaroz]

Fixed & improved code in f0bccca
However, the interaction with Commanders is still problematic...