My Warrior macro doesn't work.

[Angrypuffin]

It's probably a noob question you've all seen before, but: how does the macro UI handle multiple /cast or /click commands in sequence? It isn't working the way I expect.

A shortened version of the macro I want is this:

/cast Revenge
/cast Shield Slam
/cast Devastate

I want it to be just like clicking those three buttons. (In fact, I tried /click Revengebutton // /click Shieldslambutton // /click Devastatebutton too, but it didn't work either). But instead, it seems to always be trying to cast Devastate without trying the others. Is there any way to do this, or do I have to constantly faceroll 1-2-3 every half second to get this behavior?

[angeldeelite]

You need to do a /castsequence I.E

#showtooltip
/castsequence reset=combat/target devastate, shield slam, revenge

So one key will do all 3 in that order over and over

I would not advise having a "proc" like revenge on the same key as devastate and shield slam though as you'll get stuck doing nothing until revenge procs : /
Also shield slam has a 3 second cool down I think so you need more abilities between the first slam and the next.

[Mooni]

Yeah I've been having various problems with click macros these days, like on a DK there's one that'll only click my blood rune buttons and wait for those to refresh before doing them again. Dunno why; the first time I hit it , all of the buttons I want it to click light up borders, but once that rune's down it just wastes time.

As for warrior (I'm prot too) the /click MultibuttonLeftBarActionBarMultiAction whatever is working. Here's what I've got goin on:

#showtooltip
/use 13
/use 14
/click MultiBarLeftButton1
/click MultiBarLeftButton2
/click MultiBarLeftButton3
/click MultiBarLeftButton4
/click MultiBarLeftButton10

These MultiBarLeftButton things refer to "action bar number 4" actually, which is the one that's on the left side of the right side of the screen. It's blizzard math. Why did I use that one? Because that's the only place I had rooooooooom (pic related)


Button 1 has another macro on it. So my macro clicks a macro. This is the epitome of laziness, but a standard op around our crowd.

[IMG]file:///C:/Users/G/AppData/Local/Temp/moz-screenshot-4.png[/IMG][IMG]file:///C:/Users/G/AppData/Local/Temp/moz-screenshot-5.png[/IMG]#showtooltip
/castsequence reset=8 shield slam, devastate, devastate, devastate
/startattack

[IMG]file:///C:/Users/G/AppData/Local/Temp/moz-screenshot-3.png[/IMG]

MultiBarLeftButton2 is Shield Block (25% chance to block, 10 sec duration, 30 second cooldown lolblizzmath)
MultiBarLeftButton3 is Revenge. It procs all the time, and I find when I run 5-mans it accounts for the majority of my DPS compared to anything else I do.
MultiBarLeftButton4 is Victory Rush. I still don't understand this one, because sometimes it procs when I'm just doing normal damage. Sometimes it procs when the enemy is in "execute" range (20% or less health left) But it's nice to healers in this cataclysmized world if you can help out with heals, so I like it to go off whenever it's available.

I was reluctant to post this because others may be jealous of my macro and MSPaint skillz.

[Mooni]

BUT WHILE I'M ON A ROLL, let's show you what button 5 does. (If you didn't know, everything up to now was spamming button 3, which is my single target tank spam)

/cast !rend
/click MultiBarLeftButton5
/click MultiBarLeftButton6
/click MultiBarLeftButton7
/click MultiBarLeftButton10

Theoretically this means I should be casting rend when it's not up, and not casting it when the target is rended. It used to work that way with Flame Shock on shamans.
Then you see button 5 (if you refer to the exhibit in the reply above of my UI) is also Rend, then button 6 is Thunder Clap and button 7 is Cleave. I do this because my warrior has the talent from the other tree that makes thunder clap spread rend like thunder CLAPP.

So it would probably work better as a castsequence macro. But I'm just putting it out there.



Now I know what you're thinking and I don't like it one bit. You're wanting to know what MultiBarLeftButton10 is.

The truth is: No one knows for sure. When I hover over it, it's a Ruby Essence from the Oculus. I guess something worth macroing had been there at one point, but no more. I left it in anyway because, being a cowardly and superstitious lot, maybe the fact I have a broken button in there is why my click macro even works where others fail.

Best of luck!