BLUF Rend should cause an extra tick of damage when reapplied with “Lambs to the Slaughter” or “Blood and Thunder” and should not snapshot. FYI this causes a substantial nerf to Arms Warrior DPS as well as Prot Warrior threat.
(Transcribed from github[dot]com/ClassicWoWCommunity/cata-classic-bugs/issues/1532, for additional visibility)
- Current Behavior
1.1. Description
Mortal Strike and Thunder clap were doing an extra rend tick previously to the recent patch. This was changed and introduced rend snapshotting.
1.2. How to Reproduce
classic.warcraftlogs[dot]com/reports/7GhKxnLt6R3gXNkD#fight=6&type=damage-done&source=1&pins=2%24Off%24%23244F4B%24expression%24ability.name%20in%20(%22Mortal%20Strike%22,%20%22Thunder%20Clap%22,%20%22Rend%22)&view=events
- normal rend without procs (2340)
- popped angerforge + potion, kept refreshing with mortal strike, still same damage
- rend recast at 51 seconds, new baseline damage (3535)
- kept refreshing with mortal strike until the end, damage didn’t change
thunder clap:
classic.warcraftlogs[dot]com/reports/J4kaGQFYBy28rPK3#fight=7&view=events&type=damage-done&source=1&pins=2%24Off%24%23244F4B%24expression%24ability.name%20in%20(%22Thunder%20Clap%22,%20%22Rend%22)
- normal rend on target 1 with snapshot (3557)
- thunder clap refreshes on target 1, but doesn’t update value, just like mortal strike refresh bug fix
- thunder clap applies rend to target 2, with new value according to current stats
- they keep ticking for different values until the end of the log
1.3 Source Material
classic.warcraftlogs[dot]com/reports/J4kaGQFYBy28rPK3 there’s more examples in that log
2. Expected Behavior
2.1. Description
Rend should dynamically update with every refresh
2.2 Source Material
youtube[dot]com/watch?v=2yYrZqDSLig rend is dynamically updating, can see that at 44 seconds rend ticks for 5229 with potion, enrage and landslide? up, and then at 56 seconds it does 4844 damage with only enrage and landslide up. Mortal strike being the only ability refreshing rend in this scenario
I have reason to assume that the extra tick from mortal strike that was removed in the latest patch was correct. 4.3 simulationCraft has mortal strike causing an extra tick. Using the original video posted here (youtu[dot]be/OYM_rhC-ldA?t=424), from the timestamp 7:04 until 7:13 (excluding the 3 rend ticks shown at the 7:04 time frame that come from previous events) there were a total of 5 rend ticks and 2 mortal strikes cast. If there were no extra ticks from mortal strike there would be 3 total rend ticks at 7:07, 7:10 and 7:13. As that is not the case, adding the 2 extra ticks from the mortal strikes match the total ticks value.
youtube[dot]com/watch?v=2yYrZqDSLig&t=54s the timestamp shows another example that further solidifies this scenario as there are 2 non-aggregated rend ticks in sub 1 second, exactly after a mortal strike was cast. I also tried to count the first minute of the fight (excluding the mortal strike before the initial rend application and the rend tick on cast - from 0:28 to 1:28 - and got 31 rend ticks and 12 mortal strikes, which shouldn’t be possible to get more than 20 unless mortal strike refresh would cause a tick.
Using an addon that can be configured to aggregate dot ticks with different options shouldn’t be used to confirm any of this anyway and some sort of confirmation on the intended behavior from your side would be nice. Cheers
web.archive[dot]org/web/20120508014554/elitistjerks[dot]com/f81/t106913-arms_dps_4_0_cataclysm/p16/#post1933673 found a post talking about this situation that was recently changed. Could not find any patch notes or comments in that thread contradicting this statement.
web.archive[dot]org/web/20120209232143/elitistjerks[dot]com/f81/t106913-arms_dps_4_0_cataclysm/p19/#post2005839
different person confirming the behavior described by the previous user
Another post dated after patch 4.3.2, which was the last patch with class changes I could find
web.archive[dot]org/web/20120207224856/elitistjerks[dot]com/f81/t106913-arms_dps_4_0_cataclysm/p24/#post2091835
Original github post by github[dot]com/zoristaken, not by me.
edit: had to break all links (not allowed to post links - replaced “.com”, etc. with “[dot]com”, etc. and deleted all “http/s”) Replace “[dot]” with “.” to fix links.