Please run the script again then start Diablo III MsgBox, Diablo III not started within the allotted time. WinWaitActive, Diablo III,, 60 this command waits for Diablo III to be the active window to get window information Y_offset = 10 distance from character to issue move command on the y-axis (used to calculate the x_offset to maintain aspect ratios) Mkey = F12 key bound to Move command in game BEGIN config section - you can change the variables below to your specific needs SetTitleMatchMode, 3 Window title must exactly match Winactive("Diablo III")
SetDefaultMouseSpeed, 0 For character movement without moving the cursor SetWorkingDir %A_ScriptDir% Sets the script's working directory SendMode Input Avoids the possible limitations of SendMode Play, increases reliability. #MaxHotkeysPerInterval, 200 Safeguard to prevent accidental infinite-looping of events #Persistent Allows the script to stay active and makes it single-instance #NoEnv Prevents bugs caused by environmental variables matching those in the script If you change the resolution of the game at any point after running the script, you must reload the script for it to function properly Keep in mind if you edit this script to use another keyset the same rule applies to those keysĤ) Bind the F12 key on your keyboard to the Move action. If anyĪction is bound to one of the keys used for movement by this script the action would be performed in addition to the Screen, meaning north is moving towards the top of the screen, west is moving towards the left of the screen, and so on.Ģ) Start Diablo III within 60 seconds of step 1ģ) If this is your first time running this script remove bindings for the "W" "A" "S" and "D" keys in Diablo III.
The keys can be combined to produce a total of 8 directions (4 ordinal and 4 diagonal). This script enables traditional WASD movements for Diablo III. Love it! It is not a download, it shows the AHK script.Īuthors: Ever1ast, Jared Sigley aka Yelgis, Soda
0 kommentar(er)
