[fixed/closed]Curse of Bloodletting + lifelink
Describe the Bug:
OK, another incarnation of a prior bug. In previous versions Curse of Misfortunes would have weird interactions with Exquisite Blood and Curse of Bloodletting. In the present form, when your opponent is cursed with Curse of Bloodletting and he is damaged by a creature with lifelink he suffers double damage, but you only gain single damage (ex. if you attack with a Vampire Nighthawk he suffers 4 damage and you gain 2 life). However, if you cast Exquisite Blood then everything works as it should, even if Exquisite Blood is latter destroyed. Noble Purpose eliminates the problem as well, as it seems does any enchantment that gives lifelink.
Which card did behave improperly ?
Curse of Bloodletting (maybe)
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
PDMNv2 *** still a bug in PTT
What exactly should be the correct behavior/interaction ?
Curse of Bloodletting should double damage, resulting in double gain from lifelink.
Are any other cards possibly affected by this bug ?
unknown
OK, another incarnation of a prior bug. In previous versions Curse of Misfortunes would have weird interactions with Exquisite Blood and Curse of Bloodletting. In the present form, when your opponent is cursed with Curse of Bloodletting and he is damaged by a creature with lifelink he suffers double damage, but you only gain single damage (ex. if you attack with a Vampire Nighthawk he suffers 4 damage and you gain 2 life). However, if you cast Exquisite Blood then everything works as it should, even if Exquisite Blood is latter destroyed. Noble Purpose eliminates the problem as well, as it seems does any enchantment that gives lifelink.
Which card did behave improperly ?
Curse of Bloodletting (maybe)
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
PDMNv2 *** still a bug in PTT
What exactly should be the correct behavior/interaction ?
Curse of Bloodletting should double damage, resulting in double gain from lifelink.
Are any other cards possibly affected by this bug ?
unknown

