
Originally Posted by Akston
I have been hearing a lot of (mis)information about how deep wounds lately. As far as I understand it used to simply reset the duration if you crit again with your deep wounds already on the target without doing anything to the damage of the ticks right? Right now there seems to be a lot of confusion about how it is currently working. I have heard that it rolls now and I have heard that it simply acts how ignite does currently.
Ex. 1 Rolling behavior indicates receiving above and beyond the additional 48% bleed damage from crits like:
(I am assuming DW ticks 3 times over 6 seconds)
Crit: 1000
DW: 160
DW: 160
Crit: 1000
DW: 320
DW: 320
Crit: 1000
DW: 480
DW: 480
Noncrit: 417
DW: 480
DW fades.
Total DW Expected: 1440
Actual DW Damage (assuming DW actually "rolls"): 2400
Ex. 2 What you would expect if DW is working like the current version of ignite:
Crit: 1000
DW: 160
DW: 160
Crit: 1000
DW: 213
DW: 213
Crit: 1000
DW: 231
DW: 231
Noncrit: 417
DW: 231
Expected Damage: 1440
Actual Damage: 1439
So basically I am curious as to whether DW is using the arguably bugged "rolling" behavior or if it is simply stacking as ignites currently do for mages (indicated in second example).
|
DW rolls perfectly fine using 2nd way - the reason why you see the 10k ticks on some WWS is totally different and not really applicable to mages.
a) DW tick every second not 2
b) Even then a warrior using all haste buffs and fast OH often crits MORE often then every second.
c) Every crit refreshes duration of deep wound
d) Crits more often then 1 sec apart cause deep wounds to not tick AT ALL, but "accumulate" damage in "DW buffer"
e) When you stop critting for moer then a sec the damage is "released"
Assuming you crit exactly 1.0 sec (or slightly more so DW ticks just before the next crit) apart with 1000 dmg MH range the ticks will be
0.0 CRIT (480 DW "buffer") ->DW tick of 80 (DW "buffer" down to 400)
1.0 CRIT (+480 DW "buffer"=880) ->DW tick of 147 (DW "buffer" down to 733)
2.0 CRIT (+480 DW "buffer"=1213) ->DW tick of 202 (DW "buffer" down to 1011)
....
....
....
(lets assume after 60 sec it comes to DW cap - in real math it never reaches it but its good enough approximation)
60.0 CRIT (+480 DW "buffer"=2880) ->DW tick of 480 (DW "buffer" down to 2400)
then it 'caps out' at 480/sec ticks
Thats exactly how ignite rolls, and its damage you can observe in some testing environment
However the huge ticks corm from different mechanism. Lets assume now the crits are still 1.0 sec apart but now its just 0.0001 sec BEFORE DW ticks
0.0 CRIT (480 DW "buffer") ->DW do NOT tick, because duration is refreshed
1.0 CRIT (960 DW "buffer") ->DW do NOT tick, because duration is refreshed
2.0 CRIT (1440 DW "buffer") ->DW do NOT tick, because duration is refreshed
...
...
60. CRIT(60x480=28800 DW "buffer") ->DW do NOT tick, because duration is refreshed
so far DW damage is ZERO. But if we stop attacking or stop critting that often, all the buffer is released THEN in 6 sec burst
61. NO CRIT - DW TICK OF 4800 (24000 dmg remaining in buffer)
62. NO CRIT - DW TICK OF 4800 (19200 dmg remaining in buffer)
63. NO CRIT - DW TICK OF 4800 (14400 dmg remaining in buffer)
64. NO CRIT - DW TICK OF 4800 (9600 dmg remaining in buffer)
65. NO CRIT - DW TICK OF 4800 (4800 dmg remaining in buffer)
66. NO CRIT - DW TICK OF 4800 (0 dmg remaining in buffer)
The damage from DW is about same if you add it up in 1st case remember they tick for 66 sec total in 2nd for 6. But the average tick damage will be 11 times higher in the 2nd - they will be just less spaced apart.
Notice how the DW recount/WWS with the huge ticks , have WAY less ticks then seconds in fight from 2.5-4 times less actually.