Talk:Eye for an Eye

Resolution process

Like all on-damage triggered effects, Eye for an Eye triggers when a Damage Event targeting the controlling hero resolves. And Damage Events resolve according to which timing is coded on each damaging effects. Thus, for example, if you have Eye for an Eye active and your opponent casts Arcane Missiles, the first missile that hits you will trigger Eye for an Eye (backfiring 1 damage) before subsequent targets are damaged; if your oppoent casts Consecration instead, Eye for an Eye will be the first trigger to trigger, but after the damage has been dealt to all your characters; on the other hand, if you control Eye for an Eye, Frothing Berserker and Acolyte of Pain, and you opponent casts Swipe on the Acolyte, the damage is done to all targets first (including your hero), but before Eye for an Eye activates you have to wait for the activation of Frothing Berserker on the damage dealt to the Acolyte, the activation of Acolyte of Pain, the activation on any triggered effect that can trigger on the card drawn by the Acolyte, another activation of the Frothing Berseker, and finally gets your Eye for an Eye backfire 1 damage. Thus, I'm going to remove the word "immediately" that has been added with the last edit of this page's Notes.

In addition, regarding the C'Thun example, I feel that example mainly shows how C'Thun's dmaging effect is coded rather than how Eye for an Eye is coded. Giving it the relevance of being in the Notes section may let unexperienced players wrongly guess that Eye for an Eye has some peculiar interaction with C'Thun, while there is not: thus maybe that example (Eye for an Eye can be "countered" by C'Thun) is best suited for the Strategy section.

Elekim (talk) 10:56, 1 March 2017 (UTC)

I will defer to your judgment in this area. Aegonostic (talk) 13:36, 1 March 2017 (UTC)