DW Axe Bleed Refreshing Incorrectly

Avran_Sylt

successive applications of the bleed will overwrite the passed time of any forthcoming ticks

Vidya

STANDARD - sound warning (didn't realize game capture also captured Pandora audio)

https://www.youtube.com/watch?v=T8L4YyznQew&feature=youtu.be

---

SUCCESSIVE - sound warning (didn't realize game capture also captured Pandora audio)

https://www.youtube.com/watch?v=gUWyqLLX2XE&feature=youtu.be

Qbiken

Only thing I know is that the bleed from each axe can override eachother. Let say axe A will give bleed A and axe B will give bleed B.

If bleedtick A and B occurs at the same time you´ll only get the bleed damage from one of them, not both. The mainreason you should never run 2 axes.

Avran_Sylt

@Qbiken

I don't think that's how the axe bleed works. I think its just one bleed type that gets applied, having two axes just increases the likelihood of that bleed occurring.

The issue here is application of that bleed again in between the DoT ticks, refreshing the time till the next tick. If the initial application dealt damage it wouldn't be much of an issue, but since it doesn't, it acts more as a suppressing application if done between ticks.

Lexxypwns

Avran_Sylt wrote: »

@Qbiken

I don't think that's how the axe bleed works. I think its just one bleed type that gets applied, having two axes just increases the likelihood of that bleed occurring.

The issue here is application of that bleed again in between the DoT ticks, refreshing the time till the next tick. If the initial application dealt damage it wouldn't be much of an issue, but since it doesn't, it acts more as a suppressing application if done between ticks.

This is an old "feature" that has resurfaced as a bug.

@Joy_Division its another one of those old bugs like status effects not proc'ing on shields. How do they keep doing this?

@ZOS_GinaBruno