Book of Heroes

2 timer bugs

1. After Riposte triggers sometimes the opponent continues his current action for a while before my sw action hits. I mostly see it in sedalb fo drol dungeon fighting the boss.
2. Legacy of blades raid phase 4. After one of bosses killed say by periodic dmg tick, the second boss timer shows for example 0.4 second. I start action which is shorter than 0.4 sec, for example justicars stun of 0.3sec. And boss action hIts first. I checked that no slowing effects like ice rune were running and finished during this time.
john12345 wrote:1. After Riposte triggers sometimes the opponent continues his current action for a while before my sw action hits. I mostly see it in sedalb fo drol dungeon fighting the boss.
2. Legacy of blades raid phase 4. After one of bosses killed say by periodic dmg tick, the second boss timer shows for example 0.4 second. I start action which is shorter than 0.4 sec, for example justicars stun of 0.3sec. And boss action hIts first. I checked that no slowing effects like ice rune were running and finished during this time.


Regards 2, the timer changes as the remaining boss gets a speed and damage buff - I think it's 20% offhand. So that 0.4 could change to 0.32, for example, leading to a very quick next attack. It's easy to miss when one is killed by a DoT as there is no pause for you to select your next action where that change is seen easily.

Example: Ecnirp has 0.41 on timer and you select Stun at 0.35*. Drol dies from DoT after 0.01, leaving 0.4 and 0.34 respectively. Ecnirp timer drops and action is completed in 0.32, before your remaining 0.34 action.

(* I know you said 0.3 for Stun, but I use 0.35 here for an easy example)

You'll see the timer drop if you watch for it and kill one boss with an action, as the killed boss fades out, the timer on the other drops by that x%.
DreamingDaemon wrote:
john12345 wrote:1. After Riposte triggers sometimes the opponent continues his current action for a while before my sw action hits. I mostly see it in sedalb fo drol dungeon fighting the boss.
2. Legacy of blades raid phase 4. After one of bosses killed say by periodic dmg tick, the second boss timer shows for example 0.4 second. I start action which is shorter than 0.4 sec, for example justicars stun of 0.3sec. And boss action hIts first. I checked that no slowing effects like ice rune were running and finished during this time.


Regards 2, the timer changes as the remaining boss gets a speed and damage buff - I think it's 20% offhand. So that 0.4 could change to 0.32, for example, leading to a very quick next attack. It's easy to miss when one is killed by a DoT as there is no pause for you to select your next action where that change is seen easily.

Example: Ecnirp has 0.41 on timer and you select Stun at 0.35*. Drol dies from DoT after 0.01, leaving 0.4 and 0.34 respectively. Ecnirp timer drops and action is completed in 0.32, before your remaining 0.34 action.

(* I know you said 0.3 for Stun, but I use 0.35 here for an easy example)

You'll see the timer drop if you watch for it and kill one boss with an action, as the killed boss fades out, the timer on the other drops by that x%.
Ur right that's happening also when during Boss attack the second one dying and attack duration shortening. this is somewhere between bug and feature so I don't call it bug:)
I shouldntt give dot example to make things clear. Sometimes (not always) when first boss is killed by weapon attack second ones timer don't jump short in this time but only after I started my action. E.g same example from above but first boss dying not from dot.
By the way sometimes reverse behavior happens and timer won't jump short at all after boss death, but I wouldntt complain about this hehe
john12345 wrote:
Ur right that's happening also when during Boss attack the second one dying and attack duration shortening. this is somewhere between bug and feature so I don't call it bug:)
I shouldntt give dot example to make things clear. Sometimes (not always) when first boss is killed by weapon attack second ones timer don't jump short in this time but only after I started my action. E.g same example from above but first boss dying not from dot.
By the way sometimes reverse behavior happens and timer won't jump short at all after boss death, but I wouldntt complain about this hehe

Ugh, never noticed it jumping after starting my action, that'd be a pain for sure! Will keep an eye out for it though.
Yeah, I wouldn't complain about the timer not jumping either - take the win! ^_^
DreamingDaemon wrote:
john12345 wrote:
Ur right that's happening also when during Boss attack the second one dying and attack duration shortening. this is somewhere between bug and feature so I don't call it bug:)
I shouldntt give dot example to make things clear. Sometimes (not always) when first boss is killed by weapon attack second ones timer don't jump short in this time but only after I started my action. E.g same example from above but first boss dying not from dot.
By the way sometimes reverse behavior happens and timer won't jump short at all after boss death, but I wouldntt complain about this hehe

Ugh, never noticed it jumping after starting my action, that'd be a pain for sure! Will keep an eye out for it though.
Yeah, I wouldn't complain about the timer not jumping either - take the win! ^_^


I have definitely also had that happen to me. At least 50% of my deaths in p4 are due to this bug. It is at the point now where I ignore the timer after the first dies and take precautions assuming that I will get hit first regardless of what the timer says.
1MA_scurvynaive wrote:It is at the point now where I ignore the timer after the first dies and take precautions assuming that I will get hit first regardless of what the timer says.

Well, it only matters if the left one dies first. Also, I don't completely ignore the timer. If I will finish my action way ahead, I will do it. If it is close, I will assume I am getting hit.