Cleavis
1 month ago
[New Bug?] Battle Shout

Re-testing on the final stress test, build 31407, shows Battle Shout party threat with multiple party members has been fixed to now generate additional threat per party member. Thank you for finding and fixing that one! Warriors have a hard enough time aoe tanking in Classic that I for one would not have wanted to venture into Azeroth with Battle Shout threat the way it was back in June.

There is one outstanding issue, however, that may or may not be a bug:

Battle Shout threat is not capped at 5 buff targets.


Per Kenco’s guide from 2006:

*Battle Shout generates 55 threat for each player that is buffed; up to 5 people in your party and their pets, as long as they are on the relevant mob’s threat list.

https://web.archive.org/web/20061218200637/http://evilempireguild.org:80/guides/kenco2.php


Testing on the final stress test, 31407, showed 5 party members and a warlock imp were able to generate 6x buff threat.

https://github.com/magey/classic-warrior/issues/19#issuecomment-520281912

Test 1
1 shout (6 party) + 39 damage was found to do between 144 and 151 threat in defensive stance (111 to 116 base threat; 72 to 77 attributable to battle shout). 72 to 77 battle shout threat is rank 2 battle shout (=12 threat per target buffed) times six players.

Test 2
1 shout (6 party) + 29 damage was found to do between 131 and 136 threat in defensive stance (101 and 105 base; 72 to 75 attributable to battle shout). 72 to 75 battle shout threat is rank 2 battle shout (=12 threat per target buffed) times six players.


Now, clearly Kenco may have been mistaken, so don’t want to presume this one is necessarily a bug. But wanted to bring it to attention.

Big thanks again to Aggrend and the team for all your hard work!

Aggrend
1 month ago
[New Bug?] Battle Shout

Hi Cleavis,

Thank you for your detailed analysis on this! We also took a look at this on the reference client, and this behavior is consistent with 1.12 and as such is not considered to be a bug. I’ll go ahead and get this added to the Not A Bug list as well.

Currently Ranked: Fluff