Just change the poison name to your need and there you go. Speaking of weapons and poisons, here are useful macros that apply poison on weapons without opening your bags nor the character’s page. Note that weapon swapping triggers a global cooldown, meaning you have to wait before using Shiv right after a weapon swap. Using this macro means that you have one bind for each type of Shiv/poison and it automatically swaps your weapon before casting Shiv. equipslot 17 WEAPON SWAPPING + SHIV MACROS

Using this macro would mean that you have only one bind for Shiv, and multiple binds dedicated to weapon swapping (1 per weapon). (e.g Wound OH for healers, Mind-Numbing OH on casters, etc.)įor this reason, you’ll need to use the /equip macros as it follows. That is why you may equip different off-hand (OH) weapons in order to apply them to your enemy. Therefore, it doesn't matter if the line /cast Horn of Winter causes you to enter combat, the line immediately after it will still think you're out of combat, because the client isn't going to realize you've entered combat for about a fifth of a second.On the Burning Crusade, you Shiv a lot to stack your poisons. And even if your latency is absolutely zero (impossible, but whatever), because the thread executing the macro is busy executing it, the client (or rather, the layer of it where the Lua API and state sits) still won't be aware of the change until after it's done executing the macro. So if said cast does cause you to enter combat, the client isn't aware of it for a split second - however big your latency is. In other words, how it pertains to this macro: The server has to recognize an attempted cast as legal before the client is aware it's been successful, and that anything has changed (like you entering combat as a result of that cast). But how's this: the client isn't aware of any meaningful state change until after the macro is done executing, so all of the macro executes under the same apparent conditions. I couldn't think of a better way to word it. The second underlined part can be any emote token (right-most column) found >here< (once again, only change the underlined part). (The quotes around it must be kept in place, so only change the underlined part). The first underlined part is a standard bracket conditional system (can have multiple brackets, etc), exactly like you'd pass to a slash command. run if SecureCmdOptionParse' ' then DoEmote' ROAR' end

For instance if you want to run multiple opposing conditionals (do one emote if in combat, another if out of combat). For instance if you want to cast the spell Mutilate, and, if you're out of combat also roar, you'd do this:

If you want to do more in the macro, just place that stuff above the first line, so this part is at the very end of your macro. The macro will only reach the line /roar if the conditional fails (you're out of combat) otherwise /stopmacro will prevent it. So you invert your conditionals into a stopmacro and place the command in question below it:

There's a command called /stopmacro which stops the macro based on conditionals. So there's two ways to approach a macro like this.įirst is, you can use fallthrough. Only commands geared towards combat usually do.

Combat blinkk macro