You can store your macros in Warcraft, or you can store them within IS Boxer.
The CLS setup has the macros within IS Boxer.
Having them inside IS Boxer makes it easier to edit them, as they're all in one place... and you just assign them to whatever team you want them to apply to.
The priority system, mashing all of the keys for each desired macro works great for a Death Knight.
They have abilities which use Frost Runes, Blood Runes, Unholy Runes (with Death Runes counting as a Wild Card Rune) plus Runic Power abilities.
When one resource is depleted, another can fire off.
Most classes have one resource only, whether it is Energy, Focus or Mana.
And just about every ability uses that same resource.
So if Lightning Bolt is the primary ability, it is going to be pressed first (if only slightly ahead of each of the other keybinds/macros being mashed) and it will fire off more often then not.
If you have an ability with a cooldown, and that is higher priority then it will fire (or attempt to) more often.
But the cooldown, will limit its ability to actually fire off.
So something else with lower priority can actually fire off.
Similar to a Death Knight, with Frost Strike going off (when Obliterate cannot fire off, because the runes are depleted).
If you use a castsequence in the place of a straight macro...
It is going to obey the normal rules for a wow macro... whether it is a macro stored within IS Boxer or the Warcraft client.
If you have a castsequence with reset conditions, it will obey those.
You can have one with a null, or 'do not advance', it's going to get stuck at that point.
So you could have an initial, or setup your sequence macro, as the initial/highest priority option and it will reset on combat or target, or whatever.
If you're using a Priority, and you don't have several distinct resources...
You're pretty much going to use castsequences.
You can use a spell with a recast delay, to force a spell to stick... so something else fires off.
Steps are easier to use.
Whether they're distinct spells, or castsequences.
You can mimic our old fall-through macros too.
Code:
#show
/castsequence Spell A, Spell B
/cast Fall-Through Spell
You could go with two steps.
And send the outputs to trigger Step 1, Step 1 and Step 2.
Even if the default macro is not going to allow the fall-through to fire off, by having Step 2 going off periodically, we get our desired behavior.
If you want four abilities to fire off, you could put each on its own macro.
And cycle through the macros, Step 1, Step 2, Step 3, and Step 4.
Or multiples of the steps.
Within IS Boxer you can set a Step to not advance for a given amount of time.
So no matter how you spam the key, the mapped key does not advance to the next step.
If you want, you can also check only execute the current step once.
But you (and IS Boxer) have no way of knowing if a spell actually did fire off or you were on a GCD (or whatever else).
Connect With Us