Advanced Warrior macro help needed
 

#showtooltip
/cast [mod:shift, stance:1] Rend; Thunder Clap
/cast [mod:shift, stance:2] Piercing Howl; Thunder Clap
/cast [mod:shift, stance:3] Piercing Howl; Pummel

Only recognizes Stance 1 (The top line) .... What am I doing wrong ?

Also is there a mod I can use to increase the amount of macro's I can make because the default Macro Ui seems rather limited for space.

I'm not a fan of multiple actions, but the following might work according to a quick check of WoWWiki:

As for more macros, check out BindPad. And on another note, you could simplify this macro simply by binding it to shift+* and dropping all the mod:shift conditions.

This would be because on the first line you have Rend, wich requires shift and battle stance as condition, however Thunder clap doesn't. I think you just want castsequence?
if not:

The reason that won't work is that Thunder Clap will cast whenever the condition on line 1 returns false. What you want is:
i.e...

"cast pummel in form (stance) 3 without shift, thunder clap in form 1 or 2 without shift, rend in form 1 with shift, piercing howl in form 2 or 3 with shift"

I believe that's what you're looking for. And, since I'm compulsive about character counts:

FYI, #show has less functionality than #showtooltip, so it's not always appropriate to use it just for the smaller character count.

In any case, mine had fewer already. If the character count really matters, it's not necessary to explicitly state which modifiers or forms (same meaning as stance but shorter) you want to check for if you've already exhausted the alternatives. Although I guess I could have done with with mod instead of nomod:

As an experienced macro user, I know this can be done even shorter:
I am always terribly annoyed when I see /cast or /script, they are just long versions of /run and /use. It is a good practice to use Capitalized Characters in spell/item names. In this case, and in the most cases, mod:shift is not needed. Mod is enough. Now you might think, what if he has CTRL+<somebuttonhere> bound to something else? Quote WoWWiki: "If you bind A to a macro with, say, [modifier:shift] and you have something else bound to SHIFT-A, the SHIFT-A binding will take precedence and your macro will not run." That's about it.

Your macro will always cast Rend unless those three conditions aren't met. Here's a fixed version:

No it doesn't, my macro was ok. Placing all parameters up front is just a matter of style and is exactly the same as [paramenter]spell;[parameter]spell;.

No it's not. Macros are evaluated left to right. Your macro says "if holding a modifier and in form 1 -or- holding a modifier -or- in form3, then cast Rend. Else cast Piercing Howl."

Mine says "if holding a modifier and in form 1 cast Rend, else if holding a modifier cast Piercing Howl, else if in form 3 cast Pummel, else cast Thunder Clap."


This is a good site for how macros work:
http://www.macroexplain.com/

Ahh nice, I should have thought of that. I personally would leave the shift in just because I think it would lead to surprises; but most people would probably not care, and it definitely shortens it.

I also must have missed that you could use /use for spells; although it makes perfect sense.

Yes it does, log into the game and try the following macro:
Just some random example I thought of in 2 seconds though. And the last time I check(and used) the "all parameters in the beginning"-macro was 2.5 weeks ago.

And to prove that macro explain-o-matic is not always right:
/use Attack? In the tooltip when hovering over the ?: The /use command takes items. Attack was recognized as a spell. Did you mean to use a command like /cast instead?

To expand on Seerah's point, the [][][] notation is meant primarily to allow multiple [target=] conditions to apply to the same spell (although it certainly can be used for other purposes). It is not functionally the same as [x]y;[x2]y2 though, nor would it be any shorter if it were.

If that works, it does because you can't summon a mount in combat, or while casting hearthstone.

W/E, Try this macro then:

I have been using macros like this since the system was introduced in 2.0. For the sake of making sure there wasn't some mini-patch recently that I didn't know of that changed it, I logged in and tested several. They absolutely do not work the way you are saying they do. That macro will attack if there is a mod down or button 2 was used, otherwise it will cast SomeRandomSpell.

Edit: To further clarify, here is a macro of mine that uses both notations at once (yes I know it could be shortened; in real macros I don't care unless it's hitting the char. limit.):

I'm taking all my words back, because if I look clearer at the macro in which I use[][][]y;y1;y2 the macro is this:
And if I replace that with
It works the same. It doesn't happen often, but I was wrong :p

As someone who's been wrong once or twice myself, I applaud your admission. :p