[confirmed]Lim-Dûl's Paladin vs. planeswalkers
Posted: 03 Mar 2017, 05:42Describe the Bug:
If Lim-Dûl's Paladin attacks unblocked, all combat damage it would deal to anything that turn is prevented.
Most easily seen when it attacks planeswalkers, but it'll also deal damage to creatures that somehow block it later. (I think the only way to do that with cards in Manalink is with Mirror Match and Nature Shields Its Own. (It's likely that the scheme will incorrectly prevent other "when this attacks and isn't blocked" triggers from happening at least some of the time, but I haven't tested it and it's unrelated to this anyway.))
Which card behaved improperly?
Lim-Dûl's Paladin
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Dev fa72c43.
What exactly should be the correct behavior/interaction?
"it assigns no combat damage to defending player this turn" - i.e.,
1. It shouldn't assign the damage at all, rather than assigning and then preventing. The difference hardly ever matters. (It might in Manalink if there's a Shadowbane or Divine Deflection or something similar that checks to see whether it prevented damage "this way".) Ruling from similarly-templated Farrel's Mantle: 10/1/2008: If the enchanted creature's controller chooses to have it deal no combat damage, that combat damage is not prevented. It's simply not dealt. A creature whose damage can't be prevented (such as Excruciator) would deal no combat damage this way.
2. Only damage to the defending player should go unassigned. Not damage to planeswalkers, and not damage to creatures that block it later.
So if e.g. you have a Gaea's Anthem and a Lim-Dûl's Paladin, attack your opponent's Jace Beleren with it, and nothing else happens, your opponent should lose 4 life during the declare blockers step and Jace should lose a loyalty counter during the combat damage step.
Are any other cards possibly affected by this bug?
For 1: All of the other creatures templated similarly to "Whenever [this creature] attacks and isn't blocked, [do something] and it [doesn't deal combat damage]". The only one of them that actually prevents its damage is Zealot il-Vec (which isn't in Manalink).
For 2: Nope. At least, not among cards with "Whenever [something] attacks and isn't blocked" triggers. All the others (except Zealot il-Vec) are templated "~ assigns no combat damage this turn."
If Lim-Dûl's Paladin attacks unblocked, all combat damage it would deal to anything that turn is prevented.
Most easily seen when it attacks planeswalkers, but it'll also deal damage to creatures that somehow block it later. (I think the only way to do that with cards in Manalink is with Mirror Match and Nature Shields Its Own. (It's likely that the scheme will incorrectly prevent other "when this attacks and isn't blocked" triggers from happening at least some of the time, but I haven't tested it and it's unrelated to this anyway.))
Which card behaved improperly?
Lim-Dûl's Paladin
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Dev fa72c43.
What exactly should be the correct behavior/interaction?
"it assigns no combat damage to defending player this turn" - i.e.,
1. It shouldn't assign the damage at all, rather than assigning and then preventing. The difference hardly ever matters. (It might in Manalink if there's a Shadowbane or Divine Deflection or something similar that checks to see whether it prevented damage "this way".) Ruling from similarly-templated Farrel's Mantle: 10/1/2008: If the enchanted creature's controller chooses to have it deal no combat damage, that combat damage is not prevented. It's simply not dealt. A creature whose damage can't be prevented (such as Excruciator) would deal no combat damage this way.
2. Only damage to the defending player should go unassigned. Not damage to planeswalkers, and not damage to creatures that block it later.
So if e.g. you have a Gaea's Anthem and a Lim-Dûl's Paladin, attack your opponent's Jace Beleren with it, and nothing else happens, your opponent should lose 4 life during the declare blockers step and Jace should lose a loyalty counter during the combat damage step.
Are any other cards possibly affected by this bug?
For 1: All of the other creatures templated similarly to "Whenever [this creature] attacks and isn't blocked, [do something] and it [doesn't deal combat damage]". The only one of them that actually prevents its damage is Zealot il-Vec (which isn't in Manalink).
For 2: Nope. At least, not among cards with "Whenever [something] attacks and isn't blocked" triggers. All the others (except Zealot il-Vec) are templated "~ assigns no combat damage this turn."