Hello,
This game has script commands for all actions including movement.
In patch 1.10 Blizzard put many scripting functions into a protected status to prevent botting.
The list of protected functions includes: moveforward timers, strafe timers, left click function, right click function, jump, and others.
Good use of macro allowed players to bot the game similar to a runescape auto-clicker except it was in-game and this was stopped by Blizzard putting the macro functions into protected status.
I am working on bluetooth controller support.
Doing pretty much any left/right click action with a controller requires an extra button press to complete the action; the extra button press is to set the camera back onto the mouse.
For example: placing an AOE takes 3 buttons. Spell button, left click button, camera-on-mouse button.
Furthermore, when mapping the controller to the keyboard we need to put the mouse buttons on the controller and the jump keybind too.
The problem scripts on the protected list are the functions for left click, right click, and jump.
Removing the following 5 scripts from protected station will eliminate the need for the extra button.
It will allow controller users to take the left/right mouse/spacebar buttons off the controller map and ONTO the in-game spell bar.
This will allow controller players to map 6 additional spellbar slots with the use of modifiers.(Shift, alt, ctrl.)
It will also allow players to put both mouse buttons on the same controller button with the use of modifiers.
Functions to the re-allowed:
Jump()
CameraOrSelectOrMoveStart()
CameraOrSelectOrMoveStop([stickyFlag])
TurnOrActionStart()
TurnOrActionStop()
Script to use mouse to move camera:(Not protected functions.)
/run if IsMouselooking() then MouselookStop() else MouselookStart() end
Example of macro for left click:(After protection ends.)
/run CameraOrSelectOrMoveStart() then CameraOrSelectOrMoveStop([stickyFlag]) then if IsMouselooking() then MouselookStop() else MouselookStart() end end end
The other functions on the protected list should stay protected.
Jump is able to be done already but it's off the spellbar and it's exceeding comfy to have the spellbars arranged like the controller buttons.
Botters are already sophisticated, they've got around the ban.
I cannot think of a method for exploiting these and would love to hear ideas on how this could be used to grief and cause a dealbreaker.
If you do this I'm going to get the controller going with the new setup and I'll write a guide and share the macros.
Turtle wow will be able to add "Controller support"to it's list of features and IT WILL BE BETTER THAN BLIZZARD CONTROLLER SUPPORT WHICH USES THE EXTRA BUTTON PRESS MUHAHAHA
Re-allow 5 scripts banned by Blizzard to prevent botting.
Re: Re-allow 5 scripts banned by Blizzard to prevent botting.
PvPer's will be able to doubletap aoe bind for instant mouseover placement on keyboard and mouse.
Re: Re-allow 5 scripts banned by Blizzard to prevent botting.
These functions are clientside, removing the protection can be done relatively easily AFAIK.
The problem is, that Warden will detect that something is up with most of these edits.
The problem is, that Warden will detect that something is up with most of these edits.