Utilizing /click to run concurrent castsequences

[Trixster]

/run local f = GetMouseFocus(); if f then DEFAULT_CHAT_FRAME:AddMessage(f:GetName()) end

does work in 3.2

[blast3r]

/run local f = GetMouseFocus(); if f then DEFAULT_CHAT_FRAME:AddMessage(f:GetName()) end

does work in 3.2

What I ended up doing is just using my blizz bar for the /click macros and got it to work. DPS has increase significantly! Thanks for everyone's help!

[Mahogany]

Greetings all,

one of my chars is a Death Knight which I essentially played using a /castrandom macro to use, Scourge Strike, Blood Strike, Rune Strike, Death Coil and put up Bone Shield.

Now that Blizz has killed /castrandom this of course doesn't work. So I find myself here reading about /click.

Now I could have misunderstood but my understanding is that if I set up one macro as follows, ALL buttons would be pressed at the same time.

Mine reads:

/click ActionButton3 <-------- Button 3 = Blood Strike
/click ActionButton4 <-------- Button 4 = Scourge Strike
/click ActionButton5 <-------- Button 5 = Obliterate
/click ActionButton6 <-------- Button 6 = Death Coil

Now I run this macro every .05 seconds but the only action that triggers is Button 3. Swap around the skills and that skill triggers.

So am I totally missing the point?

My only thought is may I have and I need the /castsequence "skill" ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, AS the buttons 3 4 5 6 and the /click as the main macro sitting say in Button 1.

Would very much appreciate any help with this.

Thank you.

[Ualaa]

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

It is the same thing as making a macro with every spell in one line.
Normally this will work up until you have a 2nd spell which also incurs a global cooldown.

So:

/Use Icon of the Silver Crescent
/Cast Elemental Mastery
/Cast Lightning Bolt
/Cast Flame Shock
/Cast Lava Burst

This functions up until Lightning Bolt.
Anything past that point fails, because LB incurs a GCD, which FS and LvB also incur.

By having the Clicks call castsequences we get around this.

A castsequence will do one thing and then the next.
With two castsequences running at once, the first to be called runs first.
The second one tries to run, and like Flame Shock or Lava Burst fails to do anything.

However, unlike just Clicking abilities or running my above macro, they are a sequence.
Part of the sequence are comma's which function as "Nulls", which means nothing happens.

So we have click one activating the Lightning Bolt.
And nothing else happening.

Click two activates "Null" on the first sequence, which means no GCD is incurred.
This allows the second castsequence to do something. So Flame Shock will fire off.
The Lava Burst fails because Flame Shock used the GCD it needs.

The 3rd click gets a null on both the LB and FS castsequences, which allows LvB to fire off in the 3rd sequence.





Generally when you're building these sequences, you'd like to follow these steps.

Go to a target dummy, and figure out your DPS sequence.
You'll generally have several abilities you wish to use.
In your case it was Blood Strike, Scourge Strike, Obliterate and Death Coil.

I don't know exactly how a Death Knight works, having not played one since the Beta.
I do know abilities use Runic Power, which you need to have enough of to do them.
I also know an ability generally costs a rune type, and you have two of each.
So you could not do a Frost power, another Frost power and a third Frost power, until a Frost Rune refreshed.
That's about the limit of my knowledge of DK powers.
I don't know which of these powers you want incur which rune types or how much runic power they require.

To build a strong DK rotation, you'd probably want:
a) a Blood Ability.
b) a Frost Ability.
c) an Unholy Ability.
d) a 2nd Blood Ability.
e) a 2nd Frost Ability.
f) a 2nd Unholy Ability.
g) a Runic Power dump or an attack which doesn't use any rune type.

You then need to know how fast you mash your click sequence key.
Get a stopwatch or watch the clock for 15 seconds.
While watching, spam something like P or R; anything where several in a row are easy to read ( PPPP has several down strokes which are easier to count then say XXXX ).
Spam away, and then after 15 seconds count how many you typed.
Divide that by 15, and you have your clicks per second, or thereabouts.

Now you want to take your first ability.
Figure out the recast delay or how long until you'd like to cast it again.
Something like Chimera Shot for a hunter would be nice to cast often.
Something like Flame Shock for a shaman would be better to cast just as it expires.
Figure out how long after you cast it the first time, until you'd like to cast it a second time.
I personally click at 2 clicks per second.
If I'd like to do a Flame Shock every 18 seconds (12 seconds duration, but +6 seconds duration glyphed...)
In the first second I click the spell and a null, so 18 - 1 = 17 seconds of delay, plus my null.
So my first sequence is Flame Shock plus one comma plus [ 17 (my desired delay) x2 (my click speed) ] = 34 comma's.
So I go with /Castsequence reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

That's a total of 35 comma's for my click speed.
One comma for the second click in the second that the spell fires off.
34 additional clicks for the 17 seconds of delay, given my 2 clicks per second.

Now that you have your first ability done, you'll want to choose a 2nd.
Once that's done, choose a 3rd.
Repeat for as many spells/abilities as you wish to include in your sequence.
Ideally put an ability you can spam at the end for your fall through.
The "Fall Through" will trigger when all the other sequences are on a "null".
This way, you'll always be doing something if your toon can (is not waiting for a GCD).

[Ualaa]

Pretty easy to test if it clicks everything at once, or one thing after another.

Make a macro, which reads:

/Castsequence Curse of Agony
/Castsequence Corruption
/Castsequence Immolate
/Castsequence Haunt
/Castsequence Unstable Affliction
/Castsequence Shadow Bolt

Don't include any comma's in the sequences.
If all buttons are clicked at once, then the later spells should not fire.
I could see server latency possibly letting a Corruption go off, but probably not anything later in the macro.



Personally, it makes sense that it tries to do everything at once.
On click #1, the first sequence fires off.
However the 2nd and subsequent macro's fail, because the first has incurred a GCD.
We know a castsequence will not skip a spell, so these later sequences are still on the first cast.

On click #2, the first sequence is a null, which allows the second sequence to act.
Etc.

I could easily be wrong, but that makes logical sense, and seems to be true to my observations.

[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.

[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.