Need Help With Macro Plz

[Insomnia365]

Hey Guys & Gals,

I'm having an issue setting up my "One Button Spam Attack" (Numpad 5 Key)
I want it so that all I have to do (as well as the slaves) is to keep pressing this button and it will cast spells in priority. I've tested by spam speeds and figured I have roughly 2 - 3 clicks per second.

When I tried setting it up it said "You have no target" when I pressed the button. When I removed the [Target=] selector it worked but that's not good.

Can somone help me out please. What I need is someone to do a sample macro for me for a Level 20 Shaman (Elemental) which I can then improve when I get new spells at level 22,24,26,28,30 etc etc.

I've seen Tims vids and he has the exact setup that I am trying to duplicate in terms of keys & attacks etc.

Thank You.

Edit: This is what I tried to use:

#show Flame Shock
/castsequence [target=targettarget] reset=combat Flame Shock,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
#show Lightning Bolt
/cast [target=targettarget] Lightning Bolt

[Poyzon]

How do you select targets with your slaves? Are you setting your main as their focus? If so, then you should use [@focustarget] on your slaves.

[Tim]

Hey Insomnia,

Try doing this instead:

#show Flame Shock
/target focus
/castsequence reset=combat Flame Shock, Lightning Bolt, Lightning bolt (etc etc),,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
/target lasttarget

[Insomnia365]

Hey Tim,

I will give that a go.

Thanks for the info.

[Ualaa]

I'd take a look at click castsequences.

They let you cast multiple spells on separate cooldowns/durations in a priority based sequence.
There are two guides for doing this in the Guide section.

[Tim]

Hey Ualaa, was there ever any debate that you heard about as to why Blizzard allows click castsequences, when they specifically said they removed the castsequence cooldown functionality from the castsequence function?

I remember Blizzard saying they did not want 1 button to be able to perform automation-like selection of abilities, yet they continue to allow it with the click function.

Did Blizzard miss something here, or was there a reason they left that in?

I'm super curious

[Ualaa]

A click castsequence, is essentially a button which clicks multiple other buttons at once.

Blizzard doesn't want anything that will make intelligent decisions.
Such as cast Lava Burst if there's already a Flame Shock on the target.
But otherwise, Flame Shock.

When we make a click sequence, it cannot make any decisions.
It just clicks every castsequence, all at once, per push of the button.
The macros we place on those buttons determine what happens, but they cannot make any decisions.
They just do whatever we have preconfigured them to do.
If the second spell casts after the first, but the first has been resisted, the click sequence has no way of knowing this and happily continues.

Blizzard doesn't really seem to have any issue with using macros or the castsequence functionality.
But wants us to be the ones making the decision, whenever a choice is to be made.

Basically, a castsequence (or a click castsequence, which is just a method for super long castsequences) is a predefined order, which cannot make any decisions so it doesn't duplicate the functionality which they removed.

[Tim]

A big reason why multiboxers moved to /click though I think was because Blizzard removed the ability for castsequence macros to function if a macro item was on cooldown.

For example, you used to be able to have a macro that used a cooldown then did a spell. However, now, if you use that same macro and the cooldown isn't ready, the macro will fail as that spell will not be casted.

So before, the castsequence would continue on a cooldown, now it doesn't. Blizzard specifically said they removed that because people were making macros that made things so much easier.

But /click does that exact thing now, which makes me wonder why Blizzard missed that.

[Ualaa]

This is still entirely true of click castsequences too.

The fall-through for my Marksman Hunter click-macro used to be:
/castrandom Kill Shot, Kill Command, Rapid Fire, Steady Shot, Tranquilizing Shot, Viper Sting

It used to only select an ability if it was available, and automatically pass on it when on cooldown. Now, if the random spell is Rapid Fire, but Rapid Fire is on cooldown then the macro locks up and nothing occurs no matter how often you spam the macro, until Rapid Fire comes off of cooldown and fires as the next spell.

Similarly, if you were to go with a Destruction Warlock click-macro. Let's say your priority was:
a) Chaos Bolt
b) Immolate
c) Conflagrate
d) Incinerate
If your reset=target and Chaos Bolt is on cooldown, then the click macro is useless as that is the first spell called. Being the first spell, nothing else can fire off until Chaos Bolt does.... which means your macro does nothing whenever you change targets while Chaos Bolt is on cooldown.

For click macros, you have two options really.

If you go with reset=target, you'll always have optimal dps, assuming spells are ready to be cast. If a spell is on cooldown, then the macro will lock up and do nothing on some clicks.

If you go with reset=combat, you'll not always have as optimal dps, but its much more likely your spells will have come off of cooldown before they're needed once more.

The last option is to not include any reset conditions, which prevents the macros from locking up, but they can eventually get out of sync between your toons... so a reset condition or time (reset=19) is generally a good idea.

[Iru]

Originally Posted by Tim

For example, you used to be able to have a macro that used a cooldown then did a spell. However, now, if you use that same macro and the cooldown isn't ready, the macro will fail as that spell will not be casted.

I think you're confusing /castsequence with /castrandom. People were using /castrandom to avoid having to deal with CDs