Utilizing /click to run concurrent castsequences

[Stealthy]

Hi all,

Here's my one button spam for Prot pallies:

Macro 1:

/cast [nocombat] divine plea
/startattack
/click MultiBarLeftButton1
/click MultiBarLeftButton2
/click MultiBarLeftButton3
/click MultiBarLeftButton5
/click MultiBarLeftButton6
/click MultiBarLeftButton7

Basically I start spamming this just before entering combat make sure divine plea is up and running as soon as I hit combat. Once I'm actually in combat, that line of the macro is skipped.

Here are the rest of the macros that get called from the /click functions:

Macro 2:
#showtooltip
/assist focus
/castsequence reset=8/combat judgement of light,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Insert whatever judgement is appropriate.

Macro 3:
#showtooltip
/startattack
/castsequence reset=6/combat Hammer of the Righteous,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Macro 4:
#showtooltip
/startattack
/castsequence reset=8/combat holy shield,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,

Macro 5:
#showtooltip
/startattack
/castsequence reset=6combat Shield of Righteousness,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Macro 6:
#showtooltip
/startattack
/castsequence reset=8/combat Consecration,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,

Macro 7:
#showtooltip Cleanse
/cast Cleanse

Note - there aren't supposed to be spaces inbetween the commas, it just 'appears' that way in my posts.

I set cleanse as the last macro instead of Hammer of Wrath, since I find myself using cleanse much more during boss fights. I have a another button macro'd for all pallies to cleanse each other as well if necessary.

Hope this helps.

Cheers,
S

[coupas]

Thanks again Stealthy!

I tried your setup and works flawlessly..

[blast3r]

btw, I added one to hit trinkets as well.

[Stealthy]

Do we still need /click?

I remember the reason for it originally was multiple castsequences in one macro would bug out, and not remember their positions correctly. Has this been fixed since then?

I just built a macro for my shammies based on the one Fursphere posted that involves something like this (all in one macro using macaroon):

/castsequence [harm] reset=combat/3 flame shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,
/castsequence [harm] reset=combat/3 lava burst,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence [harm] reset=combat/3 chain lightning,,,,,,,,
/cast [harm] lightning bolt; [help] lesser healing wave

This seems to work fine, without needing /clicks to call separate macros.

The benefit of using /click is that it makes the 255 char limit of WoW macros less of an issue. Macaroon gets around the 255 char limit as well...but not eveyone wants to use an addon to do this. Also by not using an addon you have less chance of running into a problem after a patch, unless Blizz themselves change the functionality (actually I don't think Macaroon has been updated for 3.2 yet?).

/click isn't meant to be the only solution...it just gives you another option.


Cheers,
S.

[Mahogany]

The "Click" functionality is essentially saying, press all of these things at once.

"Wall of informative well written text"

Ualaa, thanks for such a great response. I can now follow the concept. Just falling short on the actual coding. Never the less I shall persist and again thank you for a great response.

[Ualaa]

If you go with a single macro which reads:

#show
/cast Flame Shock
/cast Lava Burst
/cast Chain Lightning
/cast Lighting Bolt

The Blizzard macro system executes top down, but tries to do everything at the same time.

If it were sequential, then four presses of this macro would get four spells, one after the other.
Because they're all pressed at once, but the execution is top down, only the first one casts.
The second, third and fourth will fail, because the GCD is already used.







If you go with a castsequence which reads:

#show
/castsequence Heroism, Heroism, Flame Shock, Lava Burst

The sequence will do the first Heroism.
A castsequence will not move on to the next item, until it is successful.
So we'll have to wait for the Exhaustion before the 2nd Heroism/Bloodlust fires.
And after that point, the Flame Shocks and Lava Bursts can cast.






Click doesn't change the mechanics of /cast or /castsequence.

/Click Button1
/Click Button2 (etc)

Would not help us if the macro's were set up like this:

1:
/cast Flame Shock

2:
/cast Lava Burst

The first spell fires off, and the 2nd is stuck despite it being /Click.





Similarly, castsequences without nulls won't work either.

1:
/castsequence Flame Shock

2:
/castsequence Lava Burst

The first sequence fires off each time, and the 2nd is stuck, despite it being /Click.







For multiple sequences to work, the first needs to include a null or comma.
So it isn't doing anything when it is clicked.

By doing nothing when clicked, it allows the second sequence which is clicked at the same time to do something.
When neither the first or second sequence are doing anything when clicked, this allows the third sequence to execute.

The /Click mechanic presses each button at the same time.
Blizzard UI attempts to execute these simultaneous presses on/in a first come (top down) order.

The second, third and fourth sequences do not progress from Lava Burst, Chain Lightning or Lightning Bolt, because these spells have not successfully fired off. As with other sequences, until the spell executes, the sequence will not advance.





That's my understanding of how Click Castsequences work, along with the Blizzard macro system.

[OogaJiggaWooga]

I've just set up a click/castsequence macro for my SPriest as follows:

Spamming Macro
/click MultiBarBottomLeftButton4
/click MultiBarBottomLeftButton5

Button4 Macro
/castsequence [nochanneling] reset=combat/162 vampiric embrace,devouring plague,vampiric touch,mind blast,mind flay,shadow word: pain,shadowfiend,shadow word: death,null

Button5 Macro
/castsequence [nochanneling] reset=combat vampiric touch,mind blast,mind flay,mind flay,mind blast,mind flay,mind flay,devouring plague

What this allows me to do is make sure that Shadowfiend is being popped initially, and then again on every cooldown. The first macro is always attempted before the second one, and the reset allows the process to start over at exactly the right time (assuming I have the mana to reach the next Shadowfiend call ><)

I find this use of null and reset to be an elegant solution to the comma issue, as that can be largely dependent on the speed at which you are hammering that macro key.

What is interesting about this is if spells are equivalent on the two macros (ie. VT,MB,MF line up after the first few casts of the first macro) then the system interprets both macros as having executed and progresses both of them. So by the end of the Button4 macro, the Button5 macro is 3 casts in, but then cycles through that dps macro until the reset timer is finished on the first macro.

[muffe]

how do you determine the amount of commas in your castsequence macros? if you're spamming a button at different rates all the time wont they reset at inconsistent intervals?

[KvdM]

how do you determine the amount of commas in your castsequence macros? if you're spamming a button at different rates all the time wont they reset at inconsistent intervals?

The dps will fluctuate with your spamming rate. A good way to compensate for the fluctuation is to configure it to do its highest dps at your highest spam rate. This way you'll get a bit lower dps when you're just slowly spamming the buttons and high dps when you're frantically spamming your dps button during a boss fight.

[moosejaw]

I wanted to add the format for clicking bindpad macros in case anyone needed to know.

/click BindPadMacro macroname

Single space before macro name. The macro name is exactly as you have named it in the bindpad interface.