4.1 Prot Pally Tanking Rotation

[Kekkerer]

Yeah I have 0 hit rating and expertise because I'm not up to 102.4% avoidance & block cap yet. Tanked a successful ZA mount run yesterday with my two macros, people were pulling 20-25k dps each overall for the first 4 bosses, single target dps was not an issue, had some issues with people aoeing but that is probably a reflection on my gear rather than the macros.

[Mercurio]

Thanks for this, Lans83. I tried your rotation for a bit, tweaked things in a number of different ways, then ended up going back to your rotation as I liked it the best.

I've updated it in my Macros Compendium accordingly. Thanks for your contributions to the community. We love those contributions here (unlike the hateforums at Blizz).


One other thing - Eternal Glory is probably not worth taking now for Prot Pallies. Instead of that, which is included in the build you linked, I would opt for Reckoning.

[lans83]

Thanks Merc, I'll make that change. Wasn't too sure about keeping EG, but I figured it wouldn't hurt much. I'll make the change when I log back in.

[daanji]

you should put holy wrath in both rotations. if you're going up against one target all the damage goes to the one target.

Your button2 should be judgement, holy wrath

Heavyd? Are you the same Heavyd that used to play on firetree and was once a member of the guild called Shadow?

[Heavyd]

Nope. That's not me. I box(ed) on Doomhammer for a while.

[Kvas]

My rotations now are:

Single target:
button 1: /castsequence reset=combat Crusader Strike,Crusader Strike,Crusader Strike,Shield of the Righteous
button 2: /castsequence reset=8 judgement, holy wrath
button 3: hammer of wrath
button 4: /use 10 /cast divine protection /cast Avenger's Shield

It makes it two buttons, but I leave off SotR and manually fire it off. I like to micro the tank a bit, so it's not that difficult and has a nice benefit for extra effort.

Using a similar setup to what you have, I added a button for consecration and a separate one for holy wrath. But then found that crusader strike seem to deprioritize and not fire off enough. So, my current iteration essentially has fall through macros for each ability.

for example the Avenger Shield button looks like this, for other abilities substitute their name for Avenger's Shield:

#showtooltip Avenger’s Shield
/castsequence Crusader Strike, Crusader Strike, Crusader Strike
/cast Avenger’s Shield
/use 14
/cast Divine Protection

The biggest problem is judgement and Hammer of Wrath felt like they weren't firing off properly, I just put /cast Judgement and /cast Hammer of Wrath on that button. So the main mashing macro looks like this:

/startattack
/click Crusader's Strike
/click Judgement
/click Hammer of Wrath
/click Avenger's Shield Button
/click Consecration Button
/click Holy Wrath Button
/script UIErrorsFrame:Clear()

AoE looks similar, but with HotR in lieu of CS and changed the order of buttons to prioritize different abilities.

Had quite a bit of success with this so far. I'm not convinced abilities are being prioritized perfectly though, but it was a pretty healthy gain in dps/threat from the simple two button macro.

Anyhow, hope this wasn't too confusing, I'm still learning exactly how stuff "falls through" and how to really prioritize what I want to.

[cookcpu]

I can't fill in the last 2 spell as it have reach the 255 chars limit and also after spamming a while at the dummy, I can only get auto attack unless I stop pressing the key for 3 sec then the macro will reset and start all over again.

I am not sure what I did for the macro to stop working, can it be due to the last 2 spell not in the macro that cause the macro not to work after spamming it.

[Sturmy]

I can't fill in the last 2 spell as it have reach the 255 chars limit and also after spamming a while at the dummy, I can only get auto attack unless I stop pressing the key for 3 sec then the macro will reset and start all over again.

I am not sure what I did for the macro to stop working, can it be due to the last 2 spell not in the macro that cause the macro not to work after spamming it.

Not sure which macro you're using (first page filtered at work), but sounds like you're using a reset=3 in your macro. It'll reset the macro after 3 seconds "BUT" only 3 seconds of not touching it. Putting a reset="time" in a spam macro is useless, as it'll never reset. (remember it's 3 seconds from "last click of macro".

If you could confirm which you're using could explain a bit better

Thanks

[Khatovar]

Not sure which macro you're using (first page filtered at work), but sounds like you're using a reset=3 in your macro. It'll reset the macro after 3 seconds "BUT" only 3 seconds of not touching it. Putting a reset="time" in a spam macro is useless, as it'll never reset. (remember it's 3 seconds from "last click of macro".

If you could confirm which you're using could explain a bit better

Thanks

I disagree. In the case of the poster you quote, not having a reset=x seconds means the macro won't reset at all until it gets to the end. The way castsequences and reset commands work is after this condition is met OR after the macro sequence has been completed, that macro starts at the beginning. So, reset should have NOTHING to do with it.

The macro {whatever one it is since Cookcpu didn't actually post it} is getting stuck somewhere, preventing the macro from processing something so it can complete the sequence and start over. This points to a typo in the macro, a spell listed in the sequence that they don't actually have, improper punctuation or spacing {a period instead of a comma perhaps}, a spell listed that is not having prerequisites met {Judgement when there is no Seal active, A spell that requires Holy Power when there is no HP built up} or something with a long cooldown that is getting recalled too early.

[cookcpu]

Not sure which macro you're using (first page filtered at work), but sounds like you're using a reset=3 in your macro. It'll reset the macro after 3 seconds "BUT" only 3 seconds of not touching it. Putting a reset="time" in a spam macro is useless, as it'll never reset. (remember it's 3 seconds from "last click of macro".

If you could confirm which you're using could explain a bit better

Thanks

I am copying the macro posted on the 1st post except for the macro 2, I have reach the limit of 255 chars before completing the entire macro. I am using WOW macro and I am not using ISboxer macro.

Initially, I double check on the macro to find any typo mistake and I have found some overlapping of words in the macro. I have corrected that but the problem still exist even I change the reset=1. With reset=1, the test on the dummies last slightly longer before it become auto attack.

Yes, I have to stop pressing the key for 1 sec before the macro start again.