mage
mage copied to clipboard
Umezawa's Jitte Bug
- If a creature equipped with Umezawa's Jitte dies in combat, often time the Jitte will not receive counters.
[[Umezawa's Jitte]]
Umezawa's Jitte - (Gatherer) (Scryfall) (EDHREC)
{2} Legendary Artifact — Equipment Whenever equipped creature deals combat damage, put two charge counters on Umezawa's Jitte. Remove a charge counter from Umezawa's Jitte: Choose one — • Equipped creature gets +2/+2 until end of turn. • Target creature gets -1/-1 until end of turn. • You gain 2 life. Equip {2}
By the time "DamagedPermanentBatchEvent" or "DamagedPlayerBatchEvent" fires, the equipment or aura has already detached from the permanent, thus the check fails if the permanent leaves the battlefield, etc. Other events, like "DamagedPermanentEvent" still allow for an accurate check of the equipment or aura still being attached to the permanent.
By the time "DamagedPermanentBatchEvent" or "DamagedPlayerBatchEvent" fires, the equipment or aura has already detached from the permanent, thus the check fails if the permanent leaves the battlefield, etc. Other events, like "DamagedPermanentEvent" still allow for an accurate check of the equipment or aura still being attached to the permanent.
Is that difference supposed to occur?
Also why is DealsCombatDamageEquippedTriggeredAbility
using DamagedPermanentBatchEvent
instead of DamagedPermanentEvent
?
If you do a search on the Discord channel, you will find references to it. In order not to break anything, I left it alone. Of course, the batch allows for one trigger fire versus many.
Each time the equipped creature deals combat damage, Umezawa's Jitte's first ability will trigger only once, no matter how many permanents and/or players it deals that damage to at the same time (C.R. 603.2, 603.2c, 700.1). However, if that creature deals combat damage at separate moments (e.g., during two different combat damage steps because it has double strike [C.R. 702.4b]), the ability will trigger once for each such moment.
In general, triggered abilities can treat a single "happening" as one event or as several events depending on what "event they're looking for" (C.R. 700.1). Compare Umezawa's Jitte with [[Giant's Skewer]].
Giant's Skewer - (Gatherer) (Scryfall) (EDHREC)
{1}{B} Artifact — Equipment Equipped creature gets +2/+1. Whenever equipped creature deals combat damage to a creature, create a Food token. (It's an artifact with "{2}, {T}, Sacrifice this artifact: You gain 3 life.") Equip {3} ({3}: Attach to target creature you control. Equip only as a sorcery.)
Also why is
DealsCombatDamageEquippedTriggeredAbility
usingDamagedPermanentBatchEvent
instead ofDamagedPermanentEvent
?
Suppose a creature with a "when this deals damage" ability (either its own ability or added by an aura or equipment) is double blocked, and deals damage to both of its blockers. Or the creature has trample and it deals damage both to its blocker and to the player it is attacking. According to the rules of Magic, each of these is a single instance of "dealing damage" and the creature's ability only triggers once, not once for each creature or player it dealt damage to. The "batch" events are how xmage handles this.
Also why is
DealsCombatDamageEquippedTriggeredAbility
usingDamagedPermanentBatchEvent
instead ofDamagedPermanentEvent
?Suppose a creature with a "when this deals damage" ability (either its own ability or added by an aura or equipment) is double blocked, and deals damage to both of its blockers. Or the creature has trample and it deals damage both to its blocker and to the player it is attacking. According to the rules of Magic, each of these is a single instance of "dealing damage" and the creature's ability only triggers once, not once for each creature or player it dealt damage to. The "batch" events are how xmage handles this.
Right. I understood that part from other cards with the distinction between "whenever a" and "whenever one or more".
I guess I was asking why does the Jitte specifically use the batch rather than non-batch. But the reply above covers it.
If you do a search on the Discord channel, you will find references to it. In order not to break anything, I left it alone. Of course, the batch allows for one trigger fire versus many.
Thanks for the reply about the batch.
I couldn't find anything on discord. What is the rationale for having the batch events trigger afterwards?
It is just coded that way and needs to be fixed to align with the non-batch events. We can assume that some other cards have the same issue.
We can assume that some other cards have the same issue.
Eater of Virtue is still buggy, sometimes it doesn't exile the creature when it dies, perhaps the two are related?
Zangief is also horribly bugged ( #8775 it only triggers if the creature didn't die.)
Duplicate of #8555
Any updates on progress?
If there were, they'd be on this issue.