Automation + Auto Kick + Auto Grounding + AI vs Rated PvP

[Bertimus-sargeras (Bertimus)]

@Adreaver-undermine

5. Scripting - What is possible in a macro?

Scripting is an advanced feature sometimes used in macros. Be aware that scripting can’t be used to cast a spell, use an item, or take any other “secure” action. Secure actions are those things which are reserved for the Blizzard UI, and are not available to addons.

Essentially, if you use a script in a macro, you are using a micro-addon. It has all the abilities and limitations of a normal addon, but restricted to a 255 character limit. Useful examples are announcing cooldown or crowd control targets in a raid environment, calculating variables and returning the result (e.g. How many glyphs do I have left to learn?), or making non-protected spell casts (e.g. determining which mount to use based on what zone you are in).

There are far more possibilities available with scripting than I could possibly describe here, so if you have specific questions or a script you want to share, feel free to mention it here or post a new thread.

As a result of some scammers passing off malicious scripts as legitimate, Blizzard has implemented a Lua script warning anytime you run a macro with the “/script” or “/run” commands. You get this same warning if you type a script directly in the chat window without a macro.

The warning is essentially telling players to be careful of running custom scripts they get on the internet or from other players, that they should not run any scripts they do not trust.

@Mmr-maiev

/run if not (UnitCastingInfo(“target”) or UnitChannelInfo(“target”)) then ClearTarget() end;
/cast [@target, exists, nodead] Spell Lock
/stopmacro [exists]
/targetlasttarget

#showtooltip Blind
/cast [@focus] Blind

The reason that the clear target function is important here is because it more or less circumvents the bolded rule. The script itself is not actually deciding whether you cast a spell, it’s deciding whether you retain your target. The macro folloing the script just doesn’t have anything to cast the spell on depending on the result of the script.

@Mmr-maiev

# showtooltip 
/run for i=1,10 do local D = UnitBuff("target",i); if D == "Grounding Totem" then ClearTarget() end end; 
/cast [@target, exists, nodead] Hammer of Justice 
/stopmacro [exists] 
/targetlasttarget

Similarly, this one is just setting a temporary/local variable and then polling through unitbuffs a set number of times and then updating the variable with the output and then either dropping target or not depending on a specific condition. The condition is not specifically casting any spells, it’s just preventing the rest of your macro from running because it made you drop target before that line has a chance to execute.

It is just basic coding using a “legal” condition and function to circumvent things that you’re not supposed to be able to do with scripts. The end result is that your character presses its kick button and it either kicks something or not depending on if the target is casting.