5/12/2023 0 Comments Combat blinkk macroAnd 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. I would like to hear any feedback anyone has.Most commands don't take conditionals. When in Soulshape, I now Flicker, and otherwise I Blink. Please let me know if you have any thoughts or advice.Įdit: While working on it, I made the following which actually works properly, but from my understanding of conditional true/false statements, should be wrong: The conditional does evaluate properly while in it, so I just need to find out why Blink is not casting while out of Soulshape. ![]() This works as intended, Intervene if target can be helped, otherwise (try to) charge them. For reference, I have a macro with similar logic for my warrior using Charge and Intervene: cast Flicker BlinkĬurrently, I cannot get this to work and I am not sure why. I modified it so both had conditionals, but that didn't work: This works to cast Flicker while in Soulshape, but it doesn't do anything about Blink when not in Soulshape. I am trying to create a simple Blink macro for my Ardenweald mage: If I am in Soulshape, I want the keypress to use Flicker, otherwise I want it to use Blink. However, that doesn't seem to be working for me here. ![]() I like to keep them simple, so basic true/false logic. I don't tend to use macros too often, mostly just simple ones.
0 Comments
Leave a Reply. |