New change to /castsequence macro? O.o

Hi, i am trying to make a singel button dps macro for my lock.
just wondering if they changed the reset= in castsequence.
If i spam press my castsequence macro it wont reset, the reset timer will start over each time i press the macro.
Me thats just been to long away from wow or?

Basicly what im trying to do is make this
/Click ActionButton1
/Click ActionButton2
/Click ActionButton3
/Click ActionButton4
/Click ActionButton5

1
/castsequence reset=target corruption, Cake,

2
/castsequence reset=25 Curse og Agony, Cake,

3
/castsequence reset=26 Unstable Affliction, Cake,

4
/castsequence reset=10 Haunt, Cake,

5
/cast Shadowbolt

Impossible or?

Quote:

---

If i spam press my castsequence macro it wont reset, the reset timer will start over each time i press the macro.

---

It has always been this way. The timer doesn't start until after the last keypress. Another keypress will restart the timer.

:\ kk thx Fur :)

So putting reset=time into a macro is useless as you can cast the spell over and over instead of the reset condition locking out the use of the spell as it should until time expires?

Its not useless - its just situational.

Check out click castsequences.

If you want the spell to fire off once, and then never again, at least until the reset conditionals are valid, try:
/castsequence reset=target Hunter's Mark, Null

If you want the reset to be based off of your spam speed, insert a comma (multiplied by your spam click per second speed) for every second you want to wait until the spell fires off again. The delay can be based on the re-use delay of the spell (like Lava Burst) or the duration of the dot effect (like Flame Shock) or even just give time for other casts prior to recasting the main spell.

Quite frequently, if you want reset=combat, in say the pally 96969 macro, you don't have the characters for it. But reset=9, is basically the same thing. As 9 seconds of not spamming the macro at all, will be the same thing as reset=combat (where the reset occurs when combat ends).

What I was trying to do was this macro:

/castsequence reset=11 [target=party1] renew

sadly every time I hit the button it cast renew, it did not matter if the 11 seconds was elapsed or not..it still cast...so I came hunting here..and found this thread, *shrugs*

I dont do the timed clicking thing yet....I just want renew every so often when my DK hits his Death Strike.

will have to try the adding the null to the end and see how that works..thanks.:D

You could try:

/castsequence [target=party1] reset=11 Renew,Null

This will cast renew on the first click (at Party 1).
Subsequent clicks will not do anything, as we are on the Null.
However, it won't reset to Renew until 11 seconds of not pushing the macro at all has occurred.
This means, if you push it every 10 seconds, it will never reset.

If this is on a key you spam, then I'd suggest adding commas for timing.
Even if its not exact always, as long as it is close, that will probably work.
Just tweak the commas, adding or removing them until you have something close.

If this is not a spammed key, you could try putting it on the same keybind as the DK has Death Strike.
Then only hit the key when the DK's spell is ready.

use ,Null at end of macro. It checks if spell is active or not. atleast it works on me when i cast CoE on warlock.

Nothing can check if a spell has been cast/is active on a target. All Null, or Nil, or Bob or Cake does in a cast sequence is lock up the sequence so it cannot advance and reset back to the beginning until the reset conditional has been reached.

A normal cast sequence such as /casesequence Shadow Bolt, Shadow Bolt, Incinerate will progress as it is written, 1st press casts SB, second press casts SB, 3rd press casts Incinerate. At the 4th press the sequence goes back to the beginning because there are no more spells to process.

A Nulled cast sequence such as /castsequence Hunter's Mark, Null will lock up because it can't cast a spell that doesn't exist or that you don't have. So this will cast Hunter's Mark only once and keep erroring out on "Null". It can't go back to the start because as far as the macro is concerned, the cast sequence is not complete.

With reset= you determine the conditions on when the macro should ignore everything else in the sequence and start fresh from the beginning, be it when you acquire a new target, press a certain modifier, enter or leave combat or when you stop calling the macro after so many seconds. A nulled castsequence with no reset specified will remain locked up pretty much forever. I know logouts will reset them, maybe zoning and death will reset them, but you want a reset defined in a nulled sequence.