19 October PTR Devastate Testing
** Edit 22 October because I forgot to divide by 1.10 at the end **
So I went to the PTR to test the new Devastate as patched in on 19 October.
This is the wording of the Devastate tool tip on the PTR...
Applying Devastate gives this in the combat log...
Sunder the target's armor causing the
Sunder Armor effect. In addition,
causes 50% of weapon damage plus
35 for each application of Sunder
Armor on the target. The Sunder
Armor effect can stack up to 5 times.
Assumption 1: Based on the ability description and combat log output, I assume that triggering Devastate causes Sunder Armour to be invoked as if you pressed a key to do so, and that they have not made code changes to try and combine the two effects in some way. (Being a lazy programmer, that's exactly how I'd do it =)
Your Devastate hits Servant of Razelikh for 44
Servant of Razelikh is afflicted by Sunder Armor
Assumption 2: The innate threat modifier of Devastate has remained a static, additive number. That is, they have not gone and changed it to a multiplier on us.
(It also looks very much like the Sunder effect takes place after the Devastate effect, so the damage mitigation on your third Devastate will be against two Sunders)
- Me, 70 warrior with Defiance and Devastate. All threat generated in Defensive Stance.
- I recruited my roommate to come with his mage, giving me a partner with no innate threat modifiers
- Target: Our old friend Servant of Razelikh in the Blasted Lands as target dummy.
- We both used shiny new http://thottbot.com/i851 to keep error margins small. However, when testing multiple Sunders + Devastate, he used his http://thottbot.com/i28802 to whittle down the majority of the threat I created with the Sunders, then switched to the Cutlass well in advance of the expected aggro transfer.
- I took my shield off to ensure that Shield Specialisation procs would not inject extra threat for the rage gain should I block.
I wrote a little addon to read the combat log and pick out when I hit, when I Devastate, and when I Sunder my target and stores each hit as a threat number unmodified by anything (straight damage numbers as they appear in the combat log; 301 for a Sunder) in a list. It also reads the hits made by my party members and stores them in a separate list. Once the addon detects that my target's target is no longer me, it stops recording data. It then performs the calculation taking modifiers into account and displays the difference in threat as a quick sanity check. All calculations below are done in a spreadsheet based on the recorded damage numbers for verification. The data points themselves are in this thread.
Standing out of aggro range, I performed Bloodrage. Once Bloodrage finished, I walked to the mob and took social aggro. At this point, some combination of Devastate and Sunder Armour was performed. I then ensured that attack was off, and turned my back on the mob. Mage proceeded to autoattack the mob until it turned to him, at which case we ran off and leashed it. As noted above the addon stops data collection the instant my target's target changes, so no extra hits should be collected.
Some tests have autoattack hits in the data points. Since we are not testing for a threat multiplier, the extra threat from autoattacks will fall out in the wash (i.e. some number of the Mage's attacks go to overcoming the autoattack threat) and does not affect the calculated result for Devastate threat.
We expect a significant difference between the calculated amount of threat which does not assume any value for the innate threat of Devastate, and the amount of damage needed by the Mage to draw aggro. We sum all of the Mage's hits except the last one. At this point, we know that the next hit is the one that drew aggro, and so the amount of threat needed to draw aggro was between 1 and the size of the last hit. Using this, we determine a minimum threat and maximum threat for drawing aggro for each data collection. The difference between these threat numbers and the calculated amount of threat should give us the range of the innate threat for Devastate.
Warrior => 346 => 569 with defensive stance, defiance, 110% threat
Mage => 755 to second last hit. Last hit was 10.
Minimum low = 756, delta = 114 ((756 - 569)/1.495/1.10 = 114)
Minimum high = 765, delta = 119 ((765 - 569)/1.495/1.10 = 119)
(This set includes one autoattack for 85 damage)
Warrior => 468 => 770 with defensive stance, defiance, 110% threat
Mage => 961 to second last hit. Last hit was 10
Minimum low = 962, delta = 117
Minimum high = 971, delta = 122
Warrior => 345 => 567 with defensive stance, defiance, 110% threat
Mage => 752 to second last hit. Last hit was 14
Minimum low = 753, delta = 113
Minimum high = 766, delta = 121
Warrior => 344 => 566 with defensive stance, defiance, 110% threat
Mage => 754 to second last hit. Last hit was 17
Minimum low = 755, delta = 115
Minimum high = 771, delta = 125
Range = (115-119)
One Sunder then one Devastate
(This set includes one autoattack for 90 damage)
Warrior => 792 => 1302 with defensive stance, defiance, 110% threat
Mage => 1522 to second last hit. Last hit was 14
Minimum low = 1523, delta = 134
Minimum high = 1536, delta = 142
Range = (135-142)
Two Sunders then one Devastate
(This set includes one autoattack for 90 damage)
Threat done = 1126 => 1852 with defensive stance, defiance, 110% threat
Damage done = 2100 to second last hit
Minimum low = 2101, delta = 152
Minimum high = 2112, delta = 158
Range = (152-158)
Three Sunders then one Devastate
Here the Servant failed us and got to 1% health before the Mage drew aggro. He goes kinda funny for a while at 1% so we just leashed it and left it at that. I'll probably find something with more health to test these cases later.
The important result is that we do appear to get the threat of Sunder and Devastate both. To my thinking, it appears to come from the fact that triggering Devastate also invokes Sunder Armour as if you had done so with a separate keystroke, as assumed above. I'm sure the debate regarding overpowered will rage on, and it may well be scaled back before 2.3 goes live. We shall see.
Another interpretation is that Devastate simply applies the Sunder debuff, and its innate threat has been changed to the 402.
A very interesting thing is the observed amount innate threat of Devastate. Given the triggered Sunder assumption, it appears to have been increased from 101 to (115-119) for zero Sunders, and at first glance (using only one data point for each test) increases by approximately 20 per Sunder already stacked (more results are needed to get a correct value). Perhaps the values are 115/135/155/etc. This could be an error in my calculation or an error in data collection. It could also be an actual change, intentional or not. As before, this could be explained by changing the innate threat of Devastate to 415/435/455/etc. and having Devastate simply apply the effect of Sunder Armour on the target. Ideally, someone else's independent testing will confirm or refute this result one way or the other. A wider array of data points will certainly be needed to be certain and to get an accurate number.
I stand by my initial assumption on the mechanics, given the feedback from the game in the talent description and combat log.
The actual number of Devastate's innate threat will be, of course, needed for updating threat meter addons. However, I think these results should satisfy that the threat generated by a Devastate has been increased, and actually conforms to the statement "the threat of Sunder and Devastate".
Threat in Battle/Berserker Stances?
Nice work, Satrina!
A question for you, or someone else on the PTR:
Have you attempted to measure the threat of Devastate while in Battle or Berserker Stance?
The combined sunder effect is very welcome for all situations. The additional threat is great for when we want it or don't care (tanking or solo'ing).
My concern is for when we don't want the threat (group/raid situations where you aren't the MT, and wish to contribute DPS).