Original Post — Direct link

I'm wondering if anyone can confirm a possible bug. It was my first sealed, so maybe I missed something else going on.

I played Dreadful Apathy on Erebos. I clicked the card to exile Erebos. I'm sure this went on the stack, because Arena autotapped the mana. In response, my opponent sacrificed creatures to lose devotion and make Erebos no longer a creature.

The enchantment fell off, and I thought this was a super clever play. Dreadful Apathy says it exiles a creature, there was no creature, so the trigger on the stack fizzled. But then I looked up the official ruling, and it says it should still exile the god if I'm understanding it correctly.

Is this a known bug? I'm willing to admit that I might have missed something else the opponent was doing (maybe sacrificing something triggered something else?). I was thinking about a lot of stuff at the time and reading my own cards to double check things.

External link →
over 4 years ago - /u/WotC_BenFinkel - Direct link

Yeah, this seems to be a bug, the ability is checking that the enchanted object is a creature, which doesn't match Dreadful Apathy's ruling. I'll look into fixing it, thanks for the report! #wotc_staff

over 4 years ago - /u/WotC_BenFinkel - Direct link

Originally posted by homoskedasticity

Can I ask what the reasoning behind this ruling is? I just ended up looking up the ruling after returning to nature a dreadful apathy after its ability is on the stack. It seems strange that "Exile enchanted creature" resolves when there is no enchanted creature when the ability resolves.

The notion is that "creature" in "enchanted creature" is just clarifying text, not actually constraining. It really means "the object that this is (or was via last-known information) attached to". There are similar rulings around phrases like "that creature" or "the chosen creature" - they really just mean "the same object we referred to before, it doesn't still have to be a creature." #wotc_staff