Utilizing /click to run concurrent castsequences

i doubt they'll take it away. all /click gave you was more macro space for one button click.

It seems to me that rather than depending on clicking something 5 times a second you should just be doing something like what Yo-Yo has in his tanking Macro. Set your reset to whatever that spell requires.

Druid
/castsequence reset=8 Moonfire,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=13 Insect Swarm,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/cast Wrath

Shaman
/castsequence reset=13 Flame shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=8 Lava Burst ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/casts Lightning Bolt

reset parameter only works if you don't press the button for X seconds.

Thanks, that's what I was missing.

This seems like a great way to optimize dk rotations. Macro length is not long enough to do a full rotation.
Plague Strike -> Icy Touch -> Blood Strike 2x -> Scourge Strike -> Unholy Blight -> Scourge Strike 3x -> Death Coil

So you can make a macro to put plague strike and icy touch. Then make a bloodstrike macro then scourge strike macro. Insert unholy blight in the scourge strike macro then just death coil manual when you have extra rp.

Have to test on the dummy to figure the comma amounts to do. But this gives me a start for testing. I need to edit this for the other half of the rotation.. Now if I can only find the post on what the full rotation is suppose to look like.


Bah.. forget this post. I need to get the attacks required for rotations before I can even start testing this.

== Macro 1 ==
/click MultiBarLeftButton7
/click MultiBarLeftButton8
/click MultiBarLeftButton9

== Macro 2 ==
/assist focus
/castsequence reset=target Plague Strike, Icy touch,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

== Macro 3 ==
/assist focus
/castsequence reset=target ,,Blood Strike, Blood Strike,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,,,,,

== Macro 4 ==

/assist focus
/castsequence reset=target ,,,,Scourge Strike, Unholy Blight, Scourge Strike, Scourge Strike, Scourge Strike,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

Note to everyone wondering about rate of button pressing and button spam.

As said earlier in the thread, the macros with the castsequences with long lines of commas at the end all assume that you repeatedly hit the button at a constant, set rate.
Personally, my button spamming does not have a set speed, and usually is at a rate that is too fast to fit enough commas in a macro, so I would have to change my buttonmashing style if I were to be able to utilize such a macro.

Actually you don't, depending on your class. For example if you use 3 buttons and one of them is castsequence reset=combat Flameshock,,,,, then your macro will eventually grind to a stop when it reaches that Flameshock. It will wait until the C/D on FS is up before proceeding. Sometimes this can be very bad of course, but for the most part I'd rather wait 4 secs until FS is back up and let it continue its spam than try to work around this.

Ok I've read the bigfish posts a bunch of times and I am still lost on something. Are you saying that this:
# mac1
/click but1
/click but2

# mac2 on but1
/cs foo,,,,,,,,,,,

#mac3 on but2
/cs a,b,c,d

is better than this:
#mac0
/cs foo,,,,,,,,,,,,,,,,,
/cs a,b,c,d


I am currently using the latter and it seems to work. Is the click one supposed to be faster because of latency? I don't get it.

Thanks,
-K

It really depends on what spells you are casting, which ones are instant, and what you are trying to accomplish. Some things you can include all in one macro, others become so complex you run out of characters before being half way done with what you are trying to do. If you can get what you want done in one macro, by far that is simpler. On the other hand, juggling a half-dozen Dots on something like an affliction lock is an extreme headache.

you can certainly use multiple lines in one macro as effectivlely as /click in many situations, but /click has the following advantages:

- Allows you to break up a very long macro into mulitple macros to bypass the macro length limitations
- Allows you to modularize macros and swap in different sequences by changin what macro resides on a specific button
- Allows you to break up a macro into sections that have their own unique scope for clever use of /stopmacro

For example:

Button 1:
/click Button2
/click Button3

Button2:
/stopmacro [target=target,harm,nodead]
/target Astral Flare
/stopmacro [target=target,harm,nodead]
/assist focus
/stopmacro [target=target,harm,nodead]
/targetenemy [combat]

Button3:
/castsequence XXX, YYY, ZZZ

Alternate Button3:
/castrandom XXX, YYY, ZZZ