I’ll check this out this weekend and see if I should change it for everyone else, thank you.
Okay, I have noticed mine is doing something a little silly again, it is using both stacks of shield block nearly immediately… I should mention, I am using this sequence with AHK so I don’t have to spam the button, but rather just hold it down. That being said, it uses shield block, and then IMMEDIATELY uses the second stack of shield block, whereas in your OP, it seems like it waits an appropriate amount of time to do another shield block. I feel as though I am not using this sequence correctly, and would like some indepth insight if anyone has time to help me out.
Shield Block is used on CD, which is exactly how it’s supposed to be if you’re using my build and sequence, which will be just about 100% uptime.
v.4.1 - 265ilvl my first 13th key done!
@Orbalisk Ty, your product works great ![]()
Thank you! I’m going to start pushing keys as prot warrior next week hopefully. Can’t wait.
new update
v4.1 269ilvl
Today done 14 skyrich and got 3k rio

congrats man thats fantastic.
Hi, I have a quick question for those using this. Do you also experience such frequent downtime? Sometimes I end up having absolutely no skills available for about 4 seconds because everything is on cooldown. In those moments, I manually press Revenge to “smooth out” the rotation, since it has several different chances to trigger a proc.
Looking at the logs at the end of M+ (tested on +12), I usually end up with around 10–15% parses as DPS and about 85% parses in healing. Is there some way to “sneak” pressing Revenge into a macro at least from time to time?
Very impressed with the 4.1. I just did a 7 and to help with dps i changed to Beserker stance. Healer didnt really notice much difference. but i was pulling over 100k dps on mobs. I had to change back for last boss in MT. But such a good sequence. ty
Did you die? It’s working as intended. Use revenge on proc. You can do more DPS if you rock battle stance and smack revenge a lot, but it’s not worth losing the survivability uptime imo. Prot Warrior isn’t a high APM tank. You sorta stand there a lot. You’re doing things, just not actively doing things. More haste will fix this.
I’m about to hit 2500 on prot warrior without killing myself. ![]()
not more than usual, but i have a huge problem keeping aggro. on packs, someone keeps pulling threat off me and dying, and on bosses i’m already used to having to taunt. it’s hard to explain to every group that they need to wait a few seconds each pull, so they die a lot ![]()
Ah, that should not be happening. Something is wrong. I am holding threat way under geared in 10s and 11s. Not trying at all to hold threat.
Groups I usually run with do around 400–700k DPS on big AoE pulls, and in those situations, if I don’t have Challenging Shout, I’m never able to hold aggro. So I started to using that as a regular cooldown ![]()
I sometimes have situations where I go into a pack, use Shield Slam, Thunder Clap, Shield Block, Ignore Pain, and basically end up waiting 2–3 seconds for anything to come off cooldown.
On smaller packs, it happens that I lose aggro on 1–2 mobs, but I’m able to pick them back up with Taunt.
Do you personally use Version 1 for more control? Or V2?
I used Panel 1 with shield charge.
I know you say you don’t use revenge. But top M+ prot warriors have revenge as their 3rd or 4th most damage dealer, is there any way to add revenge into this macro? I have tried to do it by basically copying the shield slam action block but replacing with revenge to no avail. I use v2 no shield charge. Ive used the macro to nearly 3k m+ rating but would really like to see revenge worked into it somehow.
I originally had revenge in the macro but the usage was marginal in overall DPS and this sequence is for max survivability. It still sims decent, but you’re not going to get sim damage and survivability. Raidbots doesn’t care if you live, just how much damage the tool can show.
Even if you remove ignore pain from the sequence and replace it with revenge, it still won’t be enough damage output.
I’m going to spend some time on this today, but I’m not making any promises.
Try this out and please report back.
Version 4.3 ALPHA
!GSE3!1VfBcuI2GG6uTB9gd2cPuvXQ7oKNTRJONTYYBwypoQTIZHaErWATWfZaclg4ZXrZ7aEPsUmmx75D36Gv0WPulQETp4TpdqYTUp/kf6T///Tp0ze/rvUQznAAnVujByMPjjCiVzUT2lFAr5pVjHxEmBrEhO0ZHfQ+RsRG9HO7bVWUptFpvDs+eSe9Lf7aaELKfgwdyJDTEgtiqSAV9gVZKAhyvYci6gWE/nSjKzZLRp9uq35Sof9z3ubrwKkfOGXqeufsDJRkWcxlwhhiHhWkkpSN2izCZ6AoSeJBLs9gNEYMEeTPwCkJXBj5Z6cOgs5ZusQO/BFM0hT25X1pIyqUChqbhWiJSuvyYW0JtW4QhqJLiBUpxUyfGHOpKBX/EZ1wmxlvzLZQiCBb4b98GvyiXJLTYfFQFFP65k9Snq6kCoTDgiSXvltky5LxOF0PWMwQ/TyO/mYFAz8NjOKBfCiLW6R3u1s1bZF45vhudnlmGaIySI8NMoo9zNZG+7mmLlbdVZtwhHD/hZkYLfQImOY7roewA1Q3qbx2zo/P2jkzbvmYVnZ8fbbc7S3OuWN9Z0T9zJzzcUa3Oecmo7tQwfNxqw2alqT+H93q5b1bBQ/tKttKdkJkG9qecYLghRJHkF7VTcSgBhn8rV5HOMQeuei/dhkLaTmfdzxqB5HzdjzOjymKiccbSr0LMe9C6XVdDXBAaUyvjWWog1h/pF5UlfahVpkM5w170olL1pHGgoKlNnSFf/7Q/2DOzcGJPxzyMa7pE2syHJraBPP4dGbOB/pgoCy+8VBXxpi1lHFrPhi45tSkP0w+qA0NUTvywoSh/ut25I09AjFI+2GwBMP/WT3lJIvQ/hKEk+E9wvnA7K4gVnTRH+ocoqYtIZpzRaGUVabKaDrz+E4Uc1QZKQ8gvrIQP2DeuSMHnAcRgBgDO+DCI6yuusi+oLHfuBTKgsMbdVQ6qCkxc4PouAexPSPfmxB/o0Pi0SO9U1117y+//tMyIYkhXgqYp+LRu26V8AI24soI+YmOPOyx2Z2uoXMYY7anr1dfaclZD/Z+UblQy8DwQ0Qcj4xBz7NZEM1ynUTtZXAcc9w4p2A+tuAlHKMol+tVrY7RbgGhDNaa67qQIMCBB+DNG6A0u4udrpaAbxMl+iEvDbgAYZTMUbtWczFps3haQNwosNzzf1iiWAYa8gPsUTeT/IuSpuvWuaRMrpSJf5WpqaEEJxexh+hN+uzLXN/7N196k18Yaretvvpq74/ftRb00d+fggsHOVLbzWZV7XKQfwE=


