Need Help With Macro Plz

[EaTCarbS]

use /assist toonname
problem solved =)

[Tim]

Castsequence used to skip entries where there was a cooldown, basically making it so you could have 1 button to do multiple types of attacks without having you, as a human, calculate whether or not something was on cooldown. They removed that, and now castsequence breaks if it has an area on cooldown.

Blizzard specifically removed that, and said they did so because they did not want an automated way of determining what attacks you are doing.

I wish I could find the link but I just woke up, too tired. But it makes me wonder why they left /click back in.

[Ualaa]

If something is on cooldown, then a castsequence gets stuck.
If its not on cooldown, then the castsequence can use whatever the spell/ability is.

Click only gets you a couple of things which you cannot do with castsequences.
a) You can exceed the 255 character limit.
b) You can rearrange the order of the spells, by moving the macros on the screen or even omit a given spell by pulling the macro out from the buttons which click calls.

Click actually calls several other castsequences, so you're stuck with all of the limitations of a castsequence.
You're not bypassing any limitations blizzard has put into the game.

If your sequence of abilities were short enough, and you were to run a small enough list, then click would function perfectly fine as a single macro, with multiple castsequences.
For example:

#show
/castsequence reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/castsequence reset=combat Lava Burst,,,,,,,,,,,,,,,,
/castsequence reset=combat Chain Lightning,,,,,,,
/cast Lightning Bolt

Assuming two clicks per second, and no Trinkets or Elemental Mastery built into the macro, this click sequence runs just fine (and is under 255 characters). Technically not a click sequence, as everything is built into the single macro.

If you were to change reset=combat to reset=target, the castsequences could get stuck on either Flame Shock or Lava Burst, the same as any other castsequence. No ability is skipped if on cooldown, whether its all in the same macro or click calls several.

[Tim]

True, but /click can click a macro that uses a cooldown, and whether or not that cooldown is up, the /click will continue onward, which is the specific thing Blizzard wanted to avoid.

I'm not saying /click is bad, heck no I'm just wondering why Blizzard choose to be non-standard in that.

[TheMuffinMan]

Originally Posted by Tim

True, but /click can click a macro that uses a cooldown, and whether or not that cooldown is up, the /click will continue onward, which is the specific thing Blizzard wanted to avoid.

I'm not saying /click is bad, heck no I'm just wondering why Blizzard choose to be non-standard in that.

No it wont.

For instance on my priest I have a /Click macro setup with 3 lines to /Click on each of my /castsequences for Vamp Touch, Mind Blast, and then Mind Flay spam.

I kill things quick enough with my 3 DPS team that by the time I cast Vamp Touch again on the next mob, Mind Blast is not off of its cooldown yet. When this happens my /Click macro locks up until Mind Blast is off of cooldown. It does NOT continue on to my Mind Flay spam until it is OFF cooldown.

[Ualaa]

With click, you are inserting commas (no action on this click) based on your personal spam speed and the desired delay until the spell fires off.

If your first castsequence is Flame Shock, and it will tick for 18 seconds until it expires, and you personally spam at 3 clicks per second.
You build your macro like this:

/castsequence reset=combat Flame Shock,,,, (18x3=54 commas).

The second macro for the sequence might be Lava Burst, which is usable every 8 seconds.

/castsequence reset=combat Lava Burst,,, (8x3=24 commas).

Let's say you don't like AoE threat, because you're playing a warrior which sucks in that regard, and want your team to single target DPS... so you omit Chain Lightning. The last spell is the fall through:

/cast Lightning Bolt




If you accidently use reset=target, and have just used Flame Shock on the initial target and then switch to a new target...
Shocks have a 6 second cooldown (unless you take pvp oriented talents, and even then have a 2-3 second cooldown).
Your very first macro is on cooldown.
Spamming the click cannot move past this macro until it is ready, which means the 2nd, 3rd, 4th etc.. (as the case may be) macros and the fall-through all do nothing until this macro can cast.

Even if the Flame Shock goes through fine, let's say you had the PvP talents.. Lava Burst could be on cooldown for another 6 seconds... in which case, the macro sticks on LvB.

In this case, because FS is earlier in the click, if you spam the button enough, you'll work through the 54 commas of no action. And eventually the FS will fire off, even thought the LvB is still on cooldown for the 8 seconds.

The Lightning Bolt will never fire off, if the FS or LvB castsequences are on a spell casting step, even if the spell is on cooldown. However, when the castsequences are on commas, the macros prior to LB are on "no action on this press", so the fall through can fire off.

If you click too fast or too slow, for the number of commas you have inserted into your castsequences, then click is not optimal. If over time, you average out to 3 clicks per second, over the long haul, then you can build your click macros to cast spells in a priority sequence and almost as soon as they come off of cooldown or their dot component has finished.