Quote Originally Posted by Chuyna View Post
Okay, excellent. Thank you. In your option, which is better, doing it that way, or doing it with a comma-separated list?
The reset conditions I use will normally vary depending on the needs I have for the spell or spells in the sequence. For things like DoTs and debuffs, I use a reset=target so that the macro goes back to the beginning whenever I start to attack a new mob and reapply the DoT's/etc.

Most of my "standard sequence" macros use reset=combat because many spells and abilities have a cooldown to them which will lock up castsequences and prevent them from casting anything until the spell's cooldown resets. I don't want to be in a position where I can't kill or pick up agro on a mob because all my early spells are still on cooldown, therefore I don't want my macros to reset until they reach the end of the sequence and/or cooldowns run down. Not having the macro reset until I leave combat is a solid way to ensure that my macros don't lock up at an inopportune time.

I also use modifiers for resets for certain things. Mostly for "nulled" sequences like I use for my DK. In her case, she wants to put her diseases up on a target only once, and because she can spread those diseases to any other mobs, she doesn't need to reapply them to every new target {thus the use of null}. But, sometimes diseases don't get spread or mobs come in late and I need to reapply diseases, so I can use a modifier like alt to force the macro to reset so she can reapply the debuffs again without having to leave combat first.

I'm not sure what you mean by "a comma-separated list." If you mean the original macro that used the 0,0,0,Spell set up, that's not really the same as reset conditions. The 0,0,0, part is just a means for allowing macros to "fall-thru" to the next line in the macro. Every time the macro reaches a 0, it has nothing to do in that line so the game has the opportunity to move to the next line down and trigger the spell there. I don't use this setup, so I can't speak to how useful it is compared to a priority cast setup/step.

If you mean a cast sequence like /castsequence spell, spell, different spell, big spell, another spell... and trying to time out spells that way - castsequences and reset conditionals are two different things. Resets are only for determining when a castsequence should start over. A reset conditional will not allow you to say "after I've activated this macro for X seconds, move to this macro or this line in the macro."

When it comes down to it, there are few, if any, classes left in WoW that use a hard-set "rotation" anymore. It is all priorities where you have spells that you should cast every time you can and some spells you only want to cast if X, Y and/or Z aren't available. This has, IMO, made things a lot easier because you don't need to sit there with a calculator, a slide-rule and a spreadsheet to figure out how many Lightning Bolts you should fit in before you can Lava Burst again. You can just make a few simple macros and call them in steps or via a priority cast system.