Well, crap. What's keeping this from working?

[fogy]

I'm just tossing together what my lvl 22 pally's have and I was certain this worked on my other team. I must be tired. The judgement hits, but the consecration and exorcism aren't firing. Yes, the button numbers are valid.

If the syntax is correct what would keep this from working?

(main)
#show
/castsequence reset=combat/target judgement of wisdom ,,,, ,,,, ,,,, ,,,,
/click BT4Button16
/click BT4Button20

(16)
#show
/castsequence reset=combat/target consecration ,,,, ,,,, ,,,, ,,,,

(20)
#show
/castsequence reset=combat/target exorcism ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,,

I do 4 clicks/sec, though these aren't calibrated yet.

What am I missing?

[Ualaa]

Not sure about having spaces between the end of the spell and also between the commas.

.... Judgement of Wisdom,,,,,,,,, (etc)

Is how I've always done it.



I've also personally gone with a single master macro, which only includes the click and possibly /use 13 and /use 14 for the trinkets.
Then had all of the sequences, such as the Judgement, as called castsequences from the master click.

[TheMuffinMan]

What he said ^

no spaces and the castsequences should be on their own buttons

[fogy]

Regarding putting castsequence in the called macros only, that doesn't resolve the problem, and further, intuitively, to me, it doesn't make a difference since the macro executes step by step, regardless of the local or /click-referenced spells, just like in programming.

I just made this up and it works:

#show
/castsequence wrath ,,,, ,,,, ,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence war stomp ,,,, ,,,, ,,,,,,,,,,,,,,,,,
/castsequence regrowth

I've always done the ,,,, ,,,, ,,,, including a space after the name of the spell. It worked on my previous team, and it's great for counting the seconds, since I do 4/sec. Spaces shouldn't matter; they don't with regular spell names.

The above works, but the following macro that I had on my previous team is now broken. (edit: it was the behavior at the dummy, nm) I just tested it and again, only the first spell is firing.

/startattack
/cancelform
/dismount
/click BT4Button82
/click BT4Button83
/click BT4Button84


That totally used to work. (edit: It still does, see below) So, what setting, where, could break the functionality?

Are yours still working?

[TheMuffinMan]

For giggles take out everything but the /clicks and test again.

Also just because spell names have spaces doesn't mean squat.

On more than one occasion having extra spaces after the end of a spell name (it can sometimes think its part of the spell name thus not finding the spell) has caused issues. Also have anything between 2 commas has also caused numerous issues (unless you are doing it on purpose with something like ",null" to keep the macro from every firing again until the reset is up).

It is not going to be a setting... something is wonky with your macros.

Are you sure you have the button numbers correct?

[fogy]

Button numbers correct: Check.
Took out all spaces: Check.
Tested with nothing but click macros calling castsequences: Check. No go.


(edit: ignore the rest of this post)
Here's a frustration:

I did:

#show
/castsequence wrath,,,,,,,
/click BT4Button39


It worked. I closed the macro window, and reopened it and it broke. The Questionmark appeared instead of Wrath and only button 39 fired.

I then took out the /castsequence wrath,,,,,,, line, closed the macro window, opened it and replaced the wrath line again. It worked.

But only until I closed the macro window, then it breaks again.

Back to debugging.....

[TheMuffinMan]

1. Macro changes do not take effect until you close the window.
2. Wrath is capitalized.
3. Only Click macros should go in the main macro
4. Post the contents of all your (3) buttons.

[fogy]

Well, they're all capitalized for that matter, and sometimes I do and sometimes I don't, but it always works. To be prudent I guess I could force the capitalization to be a habit.

Also, while editing, does clicking out of a dirty macro to a saved macro trigger a macro save, or is closing the macro window absolutely required. I ask because I generally click off then back onto the macro I'm editing to get the change to register. Don't know if the changed is saved at that point, though.

The old macros as they always have been for my 44 druid slave:

(main)
/startattack
/cancelform
/dismount
/click BT4Button82
/click BT4Button83
/click BT4Button84
/stopattack

(82)
/#Show
/castsequence reset=target Insect Swarm ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,, ,,,,

(83)
Hibernate (just the spell itself)

(84)
#showtooltip
/castsequence wrath, wrath, wrath, starfire, starfire, starfire


I'm leaving the dummies and going to pick a fight outside to see it against a live target.

[TheMuffinMan]

Spells must be capitalized. Everything in WoW/LUA is case sensitive. It never worked without being capitalized and anyone who has written a macro will tell you that.

Clicking on to another macro will also save changes in the same way that closing the window will... It just sounded like you were typing changes and then trying to hit the macro expecting the changes to take effect, and in that case they wouldn't.


"/#Show" on 82 will potentially break your macro also.

Are you typing these or copy/pasting?

You should be copy/pasting or helping you diagnose is going to be fruitless.

[fogy]

Egads,

I'm copy/pasting of course, which is why I'm stunned /#show works, but it does. I'll fix the typo just the same.

Also, I'm realizing Hybernate should come last so it doesn't break the rotation on non-critters, so that helps.


Taking things to the field the Druid macro above works as before (Note the lowercase in the third macro works, fyi.). I think the Hybernate breaking on the dummy was the issue testwise.

So the issue moves back to my pally on my other account:


as is:
(main)
/click BT4Button40
/click BT4Button16
/click BT4Button20


(40)
#show
/castsequence Judgement of Wisdom,,,,,,,,,,,,,,,,

(16)
#show
/castsequence Consecration,,,,


(20)
#show
/castsequence Exorcism



The commas are just there for testing to ensure JoW takes a break to allow the others to fire, and only JoW is firing.