Card "Pain For All" bugged
When “Pain for All” enters the battlefield and triggers, it should deal damage to any target based on the creature's power. And according to "last known information" (rule 608.2h), removing the creature from play should have no effect on the damage dealt.
However, currently removing the creature from play in any way - shuffling into library, destroying, bouncing, exiling - will reduce the damage dealt to 0. This is especially impactful because Pain for All can be played as part of a combo alongside Storm Herald and Colossification, where normally the combo is particularly resilient to creature removal. Since Storm Herald's trigger doesn't target, as long as any creature remains in play when the trigger resolves Pain for All + Colossification can be attached to it, triggering the 20+ damage. The bug removes a key strength of the combo over something like Greasefang.
If it's relevant for the bug, I noticed that the display for Pain for All's ability on the stack will show no number if the creature is removed. Normally the trigger displays the incoming damage, even if that damage is 0 from being attached to a creature with no power.
NotKjell#18019
shared this idea
-
NotKjell#18019
commented
Very strangely, the gatherer ruling is contradicting the release notes (https://magic.wizards.com/en/news/feature/edge-of-eternities-release-notes) and rulings shown on scryfall, (https://scryfall.com/card/eoe/151/pain-for-all) which both state the same:
"If the enchanted creature leaves the battlefield before Pain for All's second ability resolves, use its power as it last existed on the battlefield to determine how much damage is dealt."
I have no idea how it happened, but I believe the release notes and scryfall are correct. It is the creature dealing damage, not the enchantment. This is also a discrepancy with how burning anger and pain for function on the client, they are both auras that use wording that is identical save for the word "other":
"enchanted creature deals damage equal to its power to any other target"
Yet burning anger deals the damage through removal while Pain for All doesn't.
-
Rezzahan#77802
commented
From Pain for All's gatherer rulings:
"If the enchanted creature leaves the battlefield before Pain for All’s second ability resolves, no damge will be dealt."
(Second ability meaning the ETB damage trigger, the first ability is the enchant ability.)
And the reason is, that the LKI for enchanted creature is N/A, since at its last moment on the field, Pain for All was not attached to anything. So there is no enchanted creatuere to reference for the damage, even in LKI.