[fixed]Blazing Torch "creature has the x ability" issues
Describe the Bug:
1- I equipped Blazing Torch to my creature which was enchanted by Arrest.However Arrest didn't prevent the activation of Blazing Torch 's ability: sacrifice Blazing Torch to deal damage.
2- A blue creature equipped with Blazing Torch can target a creature with protection from blue.
3- A blue creature equipped with Blazing Torch can't target a creature with protection from artifacts.
4- If you steal Blazing Torch and equip it to your creature it's owner can still use the damage ability.
Which card did behave improperly?
Blazing Torch
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Manalink 2016/08/27: Eldritch Moon v2, duel
What exactly should be the correct behavior/interaction?
1,2,3 bugs are addressed in 2nd ruling.
4th bug is addressed in 1st ruling.
Rulings
1/10/2009 If a Blazing Torch controlled by one player somehow winds up equipping a creature a different player controls, the damage ability can’t be activated by either player. Only the creature’s controller may activate the ability -- but since that player can’t sacrifice Blazing Torch (a permanent he or she doesn’t control), the ability’s cost can’t be paid.
1/10/2009 The source of the damage is Blazing Torch, not the equipped creature. However, the equipped creature’s ability is what targets the creature or player. If Blazing Torch is equipped to a red creature, for example, the ability couldn’t target a creature with protection from red. It could target a creature with protection from artifacts, but all the damage would be prevented.
Are any other cards possibly affected by this bug?
Other equipment or auras with clause "creature has x ability" besides the known Mortarpod issue which is a bit different? due to sacrifice of creature as cost?
Note:
1- Is this exactly the same as the below Mortarpod bug or can something of the above be fixed:
viewtopic.php?f=86&t=14131&p=149158&hilit=Mortarpod#p149158
2- Is everything here a duplicate of this:
viewtopic.php?f=86&t=12802&p=139569&hilit=Mortarpod#p139569
1- I equipped Blazing Torch to my creature which was enchanted by Arrest.However Arrest didn't prevent the activation of Blazing Torch 's ability: sacrifice Blazing Torch to deal damage.
2- A blue creature equipped with Blazing Torch can target a creature with protection from blue.
3- A blue creature equipped with Blazing Torch can't target a creature with protection from artifacts.
4- If you steal Blazing Torch and equip it to your creature it's owner can still use the damage ability.
Which card did behave improperly?
Blazing Torch
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Manalink 2016/08/27: Eldritch Moon v2, duel
What exactly should be the correct behavior/interaction?
1,2,3 bugs are addressed in 2nd ruling.
4th bug is addressed in 1st ruling.
Rulings
1/10/2009 If a Blazing Torch controlled by one player somehow winds up equipping a creature a different player controls, the damage ability can’t be activated by either player. Only the creature’s controller may activate the ability -- but since that player can’t sacrifice Blazing Torch (a permanent he or she doesn’t control), the ability’s cost can’t be paid.
1/10/2009 The source of the damage is Blazing Torch, not the equipped creature. However, the equipped creature’s ability is what targets the creature or player. If Blazing Torch is equipped to a red creature, for example, the ability couldn’t target a creature with protection from red. It could target a creature with protection from artifacts, but all the damage would be prevented.
Are any other cards possibly affected by this bug?
Other equipment or auras with clause "creature has x ability" besides the known Mortarpod issue which is a bit different? due to sacrifice of creature as cost?
Note:
1- Is this exactly the same as the below Mortarpod bug or can something of the above be fixed:
viewtopic.php?f=86&t=14131&p=149158&hilit=Mortarpod#p149158
2- Is everything here a duplicate of this:
viewtopic.php?f=86&t=12802&p=139569&hilit=Mortarpod#p139569
. I fixed that it couldn't be activated to equip and when that was fixed that it crashed when activated being equipped in commit 7f2fad6e.