#Prot Warrior - Log Analysis

1 messages · Page 1 of 1 (latest)

azure kayak
#

Hello, I am looking for some feedback on prot warrior. This is my first tier playing pwar, compared to other tanks that I've played for a more considerable amount of time. So still getting used to the rotation.

Specifically this loom'ithar kill https://www.warcraftlogs.com/reports/XQ2BqH9afhNp1KLv?fight=28&type=damage-done&source=448

I noticed in a previous wipe pull (https://www.warcraftlogs.com/reports/XQ2BqH9afhNp1KLv?fight=17&type=damage-done&source=448) I was doing considerable more ionizing strike and thunder blast damage. Doing a quick comparison myself I don't seem to think I was doing anything much differently, so wondering why everything felt so much lower.

Was it the 35% ionizing strikes procs that hurt me on the kill compared to the wipe, or was I doing something massively wrong. Any feedback is appreciated, thank you for your time.

slate elk
#

The surface level source of the issue is that on the wipe, you had more casts of thunder blast overall; 11 more chances at the proc and 10 more casts of blast will increase both ionizing strike and thunder blast representations in your damage breakdowns. This mostly happened due to the difference ion Avatar uptime, since the wipe has 4% more uptime as compared to the clear kill. The interesting part of this is that you actually had one less cast of Avatar on the wipe, so the extra duration likely came from RNG procs.

It looks like there was more Thunder Blast stacks that went unused on the kill, as well, just based on the number of instances of the buff and also of this section in it's uptime:

#

That's a whole chunk of time where you didn't consume any thunder blast charges, which stands out compared to the wipe attempt, where there isn't any solid chunks of time where that was the case

#

I didn't check to see if it was an overlap in mechanics that you had to do or something that caused that large period of time with no spending thunder blast, but it's definitely leading to less casting of Thunder Blast overall on that cleared pull

#

Your outburst management was also worse on the successful pull, as well; that may not seem relevant, but it does cost you extra rage to cycle with Anger Management, so it does end up costing you potential avatar casts, as well. I'd wager it didn't matter in this specific case, I'd have to do more careful math to check, but it is something to enable you to pull more damage at least.

#

There's also random times where you would just sit on GCDs and not press anything for a sec, as well, on the kill pull, like here:

#

Those are all the abilities you cast at that point that are on the GCD

#

And there's just awkward spaces scattered throughout

#

So it's likely you're sitting on potential SS resets, not sending SS/TC/TB when they're off CD, etc

#

Adding on Avatar, around this area:

#

If you had filled those empty GCD slots, you likely would have been able to get both charges of Thunder Blast spent (there was an Ionizing Strike proc) before pressing Avatar, letting you get more Blasts out overall