Mecurio's Cataclysm Multiboxing Macros

[Mercurio]

At least one of the screenshots in the OP is not setup correctly, from what I've found.
Also, make sure you include the FTL assist step when creating the 2 step macro (unless you have an /assist command in your macro already)

Bollwerk is correct - the second screenshot is not correct. It should contain two steps that alternate "2" and ";", not one step sending both at once.

I updated the first post accordingly.

[Shodokan]

While I am just starting to come back into things

The optimal thing to do in order to take advantage of art of war for ret paladins is as follows

/castsequence crusaderstrike,blah,blah,blah,blah
/cast exorcism
/stopcasting

this will only use the exorcism when it is procced... also good for soloing by just adding it like this to any macro

/cast crusader strike
/cast exorcism
/stopcasting

[Ualaa]

The problem with the /stopcasting, is that it resets the swing timer.
Or so earlier tests in one of the pally DPS threads has shown.

[Tin]

Thanks Mercurio - my Destro lock do close to 11K on the raid dummy with this marcos.

- only doing refersh of Soul Fire everytime it fall off.

[kate]

I implemented a simplified version of the ISBoxer step keys this weekend, and it's quite lovely. Here's how I have it set up:

Hotbar 1:
1: Main attack sequence macro for SINGLE TARGET
2: Proc macro for SINGLE TARGET
3: Main attack sequence macro for AOE
4: Proc macro for AOE (usually the same as single target)

I set my 1 key to have 2 steps - first sends 1 to all, 2nd sends 2 to all; my 3 key does the same - sends 3 and then 4 to all. I'm happy to say it all seems to be working well; no real DPS increase, but it is more convenient than what I had been doing, which is a huge plus.

[Va1entines]

http://img97.imageshack.us/img97/3739/secondtq.jpg[/URL] NOTE: This is *not* correct - it should show two steps in the macro: the first step sending "2" to all windows and the second step sending ";" to all windows - sorry I didn't initally notice this!

It works the same way, it will still send both 2 and ; to all windows, but does it in a single keystroke rather than 2. Iv'e been using it since you made the macros and have never missed a proc.

[tanknspanker]

think I'll be trying these things out tomorrow on my druids, however it seems VERY complicated to me to setup cause i don't really understand anything of it xD but i'll just copy it ^^

greetingz

[Lyonheart]

It works the same way, it will still send both 2 and ; to all windows, but does it in a single keystroke rather than 2. Iv'e been using it since you made the macros and have never missed a proc.

I think you NEED the steps to keep it legal, ie one press=one action per account. You are getting two actions per one press. ( correct me if I'm wrong )

[Ualaa]

If you were to glue a quarter across two keys (and bind the first macro to one key, the second macro to an adjacent key), pushing the quarter will push both keys together.

One will push slightly before the other, on each push.

But warcraft has a thing called the Global Cool Down; because of the GCD, even if you were to push 23 buttons all as the result of a single input, you would only get one action in the game as the result of the one key press.

Every spell that triggers the GCD cannot be cast at the same time as another ability that also triggers the GCD. So even though both macros are pushed at once, unless one calls something off of the GCD then two things cannot activate.

The click based macros, which on a single keypress on our part, click two different macros do the exact same thing, except instead of doing it at the software multiplexer level, this is occurring at the warcraft level. Exactly the same thing though.

The actions that Blizzard cares about are governed by the GCD. They don't give a shit if you jump while doing something else. Similarly, it is ok to move both forward and strafe at the same time, there's nothing in the game that prevents you from moving while doing something else.

Blizzard does not want Bot type activity, which if anyone takes the time to read the post where the 1 press = 1 action was stated, the blue elaborated.. They don't want you to push one key, have one thing occur and then 3 seconds later without another push, something different, which can continue onwards for a lengthy process.

You're better off with two steps and alternating between them. This way you're guaranteed each castsequence advances as quickly as possible. If you mash both together, you could theoretically get one sequence several presses in a row, and it might be a sequence which is stuck. The whole point of two sequences, is that even though one of them cannot fire for whatever reason, the other can fire off fine.

[tanknspanker]

If you were to glue a quarter across two keys (and bind the first macro to one key, the second macro to an adjacent key), pushing the quarter will push both keys together.

One will push slightly before the other, on each push.

But warcraft has a thing called the Global Cool Down; because of the GCD, even if you were to push 23 buttons all as the result of a single input, you would only get one action in the game as the result of the one key press.

Every spell that triggers the GCD cannot be cast at the same time as another ability that also triggers the GCD. So even though both macros are pushed at once, unless one calls something off of the GCD then two things cannot activate.

The click based macros, which on a single keypress on our part, click two different macros do the exact same thing, except instead of doing it at the software multiplexer level, this is occurring at the warcraft level. Exactly the same thing though.

The actions that Blizzard cares about are governed by the GCD. They don't give a shit if you jump while doing something else. Similarly, it is ok to move both forward and strafe at the same time, there's nothing in the game that prevents you from moving while doing something else.

Blizzard does not want Bot type activity, which if anyone takes the time to read the post where the 1 press = 1 action was stated, the blue elaborated.. They don't want you to push one key, have one thing occur and then 3 seconds later without another push, something different, which can continue onwards for a lengthy process.

You're better off with two steps and alternating between them. This way you're guaranteed each castsequence advances as quickly as possible. If you mash both together, you could theoretically get one sequence several presses in a row, and it might be a sequence which is stuck. The whole point of two sequences, is that even though one of them cannot fire for whatever reason, the other can fire off fine.

so what you are trying to say is.. it's legal? ^^
or not? Ö
sorry if i'm being kind of nub now but long text confuse me, aint a english man here ^^

greetingz