• 0

    posted a message on Official Threat-1.0 error reporting and discussion thread
    Bug with Devastate threat?
    Threat-1.0 r49422
    Warrior r44618

    I actually came across this while doing research on devastate to model how much threat I can do in a spreadsheet. In the Warrior.lua file, it looks like you're adding 35 innate threat per application of sunder armor.
    function Warrior:Devastate(rank)
    	local threat = self:GetLinearThreatGuess("devastate", rank)
    	--[[
    	for buffName, _, applications in Aura:DebuffIter("target") do
    		if buffName == BS["Sunder Armor"] then
    			threat = threat * applications
    			break
    		end
    	end


    Wowwiki (http://www.wowwiki.com/Devastate) has it correct in that it's a flat 101 threat added to a Devastate attack and that it is damage, not threat, that scales with sunders. There is still some conflicting information out there about the way devastate works, so I did some testing that ended up confirming Wowwiki's explanation. It also turned out that Devastate scales with AP divided by 2 which has been shown by other, more rigorous, research. This could explain some of the inconsistencies in the various ways people have tried to calculate Devastate's total threat.

    The total threat scaling of Devastate can be described with the following equation:
    (1-Mitigation)*(.5*2.4*(WeaponDPS*AP/14)+35*#Sunders)+101
    So basically, it's Mitigation*Damage+101.

    That said, I think your threat library is wonderful and thank you for putting the time in to do this. It has certainly improved my WoW raiding experience a great deal.
    Posted in: Libraries
  • To post a comment, please or register a new account.