Martyrdoom interrupt resistance does not work
Posted: 23 Mar 2015, 15:48
What is the bug?
Martyrdoom talent does not work on Deadly Throw when used with PvP gloves.
What kind of bug is it? (Quest, Class, Spell, PvE)
Talent.
How can you reproduce it?
Take a melee or ranged critical hit so Martyrdoom procs, then start a cast (I used Greater Heal) and let the rogue cast Deadly Throw with PvP gloves equipped.
Please describe, in detail, what is suppose to occur when this bug happens:
If this talent or the deadly throw ability worked as intended, Martydoom would resist the interrupt and the damage as they are linked. I tested this with a warrior who first got to crit me, then I started to cast and he used pummel. In the case my talent prevented his resist, it also prevented the damage caused by pummel. As Pummel and DT works the same way when rogues use their PvP gloves, the result should have been the same in the rogue scenario.
Please describe, in detail, what happens when it bugs up, and how it's malfunctioning:
I am not exactly sure tbh. For I can't say I know the matter myself. But I can see two available scenarios.
1. If the interrupt effect is resisted, so shall the damage be (as the interrupt and the damage are linked together in one ability, although it becomes a matter of perception ability wise).
2. The interrupt effect is resisted, but the damage is still delivered.
Evidence providing proof of bug:
I made several attempts to find proof here which resulted in more than 50+ screenshots.
But on a quick information basis, the warrior's pummel was affected by Martyrdoom but the rogue's Deadly Throw was not. We attempted to get Martyrdoom to resist DT more than 30 times without any luck. Minding the chance is 20% (and it worked correctly vs the warrior in terms of proc rate) I think it is safe to say it does not work at all vs rogues.
I would be happy to help you test this Itslovelol.
Ps: In regards to the DT speed, I checked it up and there is a interrupt time, but it is on 0,1-0,2 depending on distance and server delay, so I guess both are technically right.
Edit: Changed title
Martyrdoom talent does not work on Deadly Throw when used with PvP gloves.
What kind of bug is it? (Quest, Class, Spell, PvE)
Talent.
How can you reproduce it?
Take a melee or ranged critical hit so Martyrdoom procs, then start a cast (I used Greater Heal) and let the rogue cast Deadly Throw with PvP gloves equipped.
Please describe, in detail, what is suppose to occur when this bug happens:
If this talent or the deadly throw ability worked as intended, Martydoom would resist the interrupt and the damage as they are linked. I tested this with a warrior who first got to crit me, then I started to cast and he used pummel. In the case my talent prevented his resist, it also prevented the damage caused by pummel. As Pummel and DT works the same way when rogues use their PvP gloves, the result should have been the same in the rogue scenario.
Please describe, in detail, what happens when it bugs up, and how it's malfunctioning:
I am not exactly sure tbh. For I can't say I know the matter myself. But I can see two available scenarios.
1. If the interrupt effect is resisted, so shall the damage be (as the interrupt and the damage are linked together in one ability, although it becomes a matter of perception ability wise).
2. The interrupt effect is resisted, but the damage is still delivered.
Evidence providing proof of bug:
I made several attempts to find proof here which resulted in more than 50+ screenshots.
But on a quick information basis, the warrior's pummel was affected by Martyrdoom but the rogue's Deadly Throw was not. We attempted to get Martyrdoom to resist DT more than 30 times without any luck. Minding the chance is 20% (and it worked correctly vs the warrior in terms of proc rate) I think it is safe to say it does not work at all vs rogues.
I would be happy to help you test this Itslovelol.
Ps: In regards to the DT speed, I checked it up and there is a interrupt time, but it is on 0,1-0,2 depending on distance and server delay, so I guess both are technically right.
Edit: Changed title