I take it /click doesnt work anymore?

[Multibocks]

I'm trying to up my shamans pathetic dps (4500) and I just tried throwing Mercurios macros in a /click sequence and while it will cast Flame Shock from the first macro and Lava Burst from the second nothing else gets cast. I assume that means it is broke now? Haven't had much luck with the 2 step method so trying to figure out an alternative to it.

Oh and I also use a simple dps macro currently:

/castsequence reset=combat/8 Flame Shock,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Earth Shock,Lightning Bolt,Lightning Bolt,Lightning Bolt
/cast Lava Burst

which works, but it's pretty crappy dps =(

edit: ya know Im just gonna guess its my shaman's lame gear as the simple dps macro seems to work(no delays). Shocking considering my mage did 8k dps in greens and now 12-13k. =(

[MiRai]

/click has been broken since, like, November?

[Nolife]

Ummm... /click hasn't changed, but /castsequence was changed so that you can no longer add delay using commas = breaking traditional "click macros".

[Multibocks]

I'm using Mercurios macros which have no commas for delays.

[Multibocks]

/click has been broken since, like, November?

I quit boxing in September so I wouldn't know.

[Noids]

QFT

Back to topic, click should work fine with the macros you are using. As mentioned above, the only macros that were broken were our castsequence delays using multiple commas.

[Multibocks]

Ele Shaman

Ele Sequence Macro
/assist focus
/castsequence reset=combat/8 Flame Shock,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Lightning Bolt,Earth Shock,Lightning Bolt,Lightning Bolt,Lightning Bolt
/cast Elemental Mastery

Ele Proc Macro
/castsequence reset=combat/8 Call of the Elements,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Searing Totem,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst,Lava Burst
/use 13
/use 14



That is what I used and it doesnt work with /click

[Maxion]

Fallthrough in a macro will not work when the macro is being triggered through /click, since it works differently when triggered by a button than when by /click.

[Ughmahedhurtz]

Fallthrough in a macro will not work when the macro is being triggered through /click, since it works differently when triggered by a button than when by /click.

Fallthrough "comma-based" macros don't work anymore period, unless there's something I'm missing.

[Multibocks]

Actually that first macro at tops works for me and it's a fall through with lavaburst. Casts it everytime that's possible.

[Ualaa]

If you physically push 1 then 2, and alternate it is two macros.

If you run the first macro as is.
And also include a line: /click Whatever...
Then the fall-through on the second macro, called by the click, won't fall through.

At least that is my understanding of what Maxion is saying.

[Noids]

Considering click basically just builds one big macro, what has been done is to stop castsequences from being your fallthrough now as Ugh mentioned.

ie. The following macro will not work:

/use 13
/use 14
/castsequence flame shock, lightning bolt, lightning bolt. lightning bolt
/castsequence lava burst, lava burst, lava burst

but this one will:

/use 13
/use 14
/castsequence flame shock, lightning bolt, lightning bolt. lightning bolt
/cast lava burst

It doesn't matter if you try and build this macro using click or not, the above structure will still stand:

ie.

/click 1 (/castsequence flame shock, lightning bolt, lightning bolt. lightning bolt)
/click 2 (/castsequence lava burst, lava burst, lava burst or /cast lavaburst)

I think the main reason for this is because they stopped the fall through effect commas used to have. The reason we can use a fall through macro still is because castsequence has an innate latency built into it whereas a pure cast command does not. A castsequence macro has to query the server to see if the previous cast has completed before it sends the next cast command through. During this moment of latency, the macro will fall through to the cast command which does not need to query the server. If you use a castsequence as your fall through, the query that is sent by the first sequence will always return before the query sent by the second sequence and thus the first castsequence will advance first. Once it has advanced, new queries need to be sent through again for both.

A way around this problem that people have been using is to use your multiboxing software to send 2 key commands at the same time. You can bind castsequence one to key 1 and castsequence 2 to key 2. Create a mapped key which has 2 actions to it to send both keys and you will be able to operate a castsequence as a fall through. This is not quite the same functionality as previously because we still can't build in delays using the commas the way we used to.

[Ughmahedhurtz]

Actually that first macro at tops works for me and it's a fall through with lavaburst. Casts it everytime that's possible.

It's not comma-based. By "comma-based" I mean something like this, say, for round-robin interrupt:

Pally 1 = /castsequence reset=20 hammer of justice,,,,
Pally 2 = /castsequence reset=20 ,hammer of justice,,,
Pally 3 = /castsequence reset=20 ,,hammer of justice,,
Pally 4 = /castsequence reset=20 ,,,hammer of justice,
Pally 5 = /castsequence reset=20 ,,,,hammer of justice

That sort of fall-through, comma-based stuff is purely broken today.