#showtooltip
/castsequence reset=120 Blade Flurry, Killing Spree
Trying to get it to reset after two mins but it never does.
Also, when trying to include ANY condition ([nostealth], [combat], etc), it breaks the macro.
#showtooltip
/castsequence reset=120 Blade Flurry, Killing Spree
Trying to get it to reset after two mins but it never does.
Also, when trying to include ANY condition ([nostealth], [combat], etc), it breaks the macro.
reset=120
means reset 120 seconds after the macro’s been pressed last.
Not if you put them in the correct location
Right. That’s why I wrote it that way.
Yes, even when I put them in the correct location.
Assuming those are both on the GCD then to get a perfect 2 min cooldown you would want it at reset=118 since rogues GCD is 1 second.
Either way having it like that is not important. You can fix this by simply doing;
#showtooltip Killing Spree
/castsequence reset=10 Blade Flurry, Killing Spree
Reset 10 works because the abilities are on cooldown and even if you press it again during this time it wont go off so not a big deal. Having the showtooltip will let you track the CD to see when it’s ready again.
this doesnt make sense to me. how does the GCD effect the reset time for 1 second let alone two?
As soon as you press the macro a 2nd time it cycles back to the beginning so you’re only interested in the reset time for when you don’t cast KS.
That means you want the reset timed to Blade Flurry’s 30s CD.
Because castsequence macros start the reset count from the last time you pressed the key not from the first time you pressed the key. The more abilities on a cast sequence the more globals it takes to cast it all.
If you have 10 abilities and the first ability has a cooldown of 100 seconds that means with a 1 second GCD it would take you 10 seconds to cast the entire sequence with perfect latency. This means that the first ability now only has 90 seconds left of recharge. So if you, for some reason, want it to land perfectly on that ability being ready you would do reset=90 instead of reset=100. If you did 100 the ability would have been ready for 10 entire seconds but you could not activate it during this time.
im shocked that it starts from the last time you press the key and not the first
ty for the explanation. will test it when i get more time
Im glad I could help but you guys really need to understand that under no circumstances is it useful to have perfect resets like this on cast sequence macros. The only purpose of the reset=?? is to allow you to toss other abilities in between the macro presses without disrupting the flow but keeping it short enough that if you take too long to continue the sequence it would be more beneficial to start it over.
An example since youre are rogue is if you had a burst /castsequence mcacro but needed to manually toss some defensive cooldown during it like kick / evasion having a reset=10 means that you have 10 entire seconds to press whatever other buttons you need to and still are able to pick up exactly where you left off in the cast sequence. Waiting longer than 10 seconds to press the button again would simply reset it, which is good because there are basically no rotations in the game that are optimal to have a 10 second afk window in the middle of it and not just start over. So a SHORT 5-10 second window for reset is optimal.
This is the same for cooldown abilities. You do not need to have a reset land when an ability is off cooldown. You can just #showtooltip the ability with a reset=5 or reset=target and press it again when the ability is ready. Pressing the cast sequence before the ability is ready will simply return ‘ability is not ready yet’ error text and not go off, just like if you were to click the ability by itself on the action bar when it isn’t off cooldown yet.
So please do not try to make ‘perfect’ /castsequence reset=?? for the abilities you are using. Even if the abilities have no cooldown and you just want to start the macro over as soon as the last ability is finished casting. You can simply use no reset on it. Having no reset like /castsequence ability1,ability2,ablity3 will simply put the macro into an infinite cycle. This could be an issue overtime though so it is usually advised on infinite cycle macros to put at least a [combat] or [target] restart command in it because without one you could kill a mob with ability2 and get to the next mob and hit the macro again to cast ability3 but ability3 relies on a short buff from ability1 or ability2 and it is not possible to cast without it leaving you with a stuck macro. Having reset=combat/target solves this problem.