[Patched] ClearTarget() isn't a secure command

[Elvenbane-veknilash (Elvenbane)]

ClearTarget() isn’t a secure command, nor does it require a hardware event to trigger. This allows for a variety of automation.

Examples: Apparently ClearTarget() isn't a secure command

[Holycow-uldaman]

It can be abused in PvP so you will never get juked. Your kick will only be used if something is being casted.

There are also various other ways it can be used to automatically prevent you from casting spells when you’re not supposed to cast them:

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

Hello everyone. We all know blizzard try to fight scripters, third-party program usage and cheaters in general. So I want to talk about ClearTarget() function. First of all I’m not a developer and some of the code below can be terrible (but working). Secondly, we all know that CastSpellByName() function is protected to avoid unintended usage. But what about this? /run if not (UnitCastingInfo(“target”) or UnitChannelInfo(“target”)) then ClearTarget() end; /cast [@target, exists, nodead] Spe…

[Holycow-uldaman]

@Kaivax

We’re investigating this, and we will take appropriate steps to address it as soon as possible.

[Méòw-moon-guard]

They added more in-game restrictions this week:

@Linxy

MACROS

• Macros can no longer conditionally execute commands based on your party state.
• Macros can no longer change equipment using /script, /run, or the Lua API. Equipment can still be changed using regular macro commands such as /equip.
• Technical notes:
  • UI Macros have been restricted in a few ways. The general issue was there were several exploits to conditionally execute macro commands. These exploits tended to use un-restricted Lua API functions that happened to mutate states that various macro options/conditionals queried, or selectively register the globally available MacroEditBox for the event that would run commands
  • To address the state mutation, two methods were employed:
    • Converting APIs like PickupInventoryItem to be restricted when trying to change gear during combat.
    • Caching the state queried by the macro conditional when combat starts so that the state remains invariant while combat is in progress. Macro options that check party membership and composition uses the cached state approach.
  • To address selective event registration the MacroEditBox was removed from the global namespace and the event was replaced with a callback.