Autowalk / Autorun tool (using AutoHotkey)

[Ducain]

I always hated games that made you run long distances without an autowalk / autorun button. My S.O. loved this game Fable 3 so much when she tried it, I got it for her. She kept complaining about that lack of an autowalk / autorun button.

I did some digging around and used the forums / walkthroughs at the AutoHotkey website to create a code / macro like program that turns the tilda ( ` ) key by the 1 button into an autorun key. When you push tilda ( ` ) the computer thinks that the W key is being held down. When you push tilda ( ` ) again, the computer thinks you let go.

Disclaimer: I wouldn't imagine this would be considered a cheat in a single player game like Fable, and I will take this down if I am informed that this is an inappropriate thing to submit.

Here is the code that you should use with the program AutoHotkey:

#Persistent
Wdown = 0
`::
if (Wdown = 0) {
Wdown = 1
send, {w up}
}
else {
Wdown = 0
send, {w down}
}
return


You can turn any button into an autorun button just by substituting the button you want to use in place of the tilda above too.

I also used the program AutoHotkey to make a mini .exe file that will load the script without having to install AutoHotkey at all.

https://www.dropbox.com/s/3glzic09eq5b20n/Auto%20Walk%20Tilda.exe

but if you feel uncomfortable downloading an .exe from a weblink (and I would be too, but I figured I might as well share it), just install AutoHotkey. It has a program that installs with it (Convert .ahk to .exe) that will take the code I copy/pasted above and turn it into a portable .exe like the one I linked from Dropbox.

[Avastgard]

This has worked well for me, but my character on a game called The Long Dark will only start auto walking after I tap the key twice. Any idea why this might be happening?

[Ducain]

I've seen some programs treat this script oddly and one program didn't even work with it (part of the STALKER series, so I didn't bother), so I don't know if it's something wrong with the script or not. The only thing I would maybe try is to bind it to a different key (not `) and see if that changes its behavior (just to troubleshoot it, and if it's a more comfortable key, it might be a win-win).

[Avastgard]

The behavior I mentioned happens with the "\" key. I'll try it with the original " ' " and see if that changes anything

[Avastgard]

A friend of mine got the problem solved for me with this:

#MaxThreadsPerHotkey 2 ; usa duas threads, uma para entrar no loop e ficar "segurando" a tecla e outra pra sair do loop
looping = 0

; SC056 é o "scan code" da tecla '\'
SC056::
looping := !looping
if (looping){
state := GetKeyState("w") ; GetKeyState retorna false (0) pra tecla levantada e true (1) pra tecla abaixada
if state = 0 ; só continua a lógica se a tecla 'w' estiver levantada
send {w down}
while (looping) {
sleep 100
state := GetKeyState("w")
if state = 0 ; se alguém pressionou o 'w' de verdade e a tecla foi levantada, sai do loop sem emitir o keyup do 'w'
looping := !looping
continue
}
send {w up}
}

; # ! ^ +
; super alt ctrl shift

Press \ once to autowalk, again to stop, again to start walking again. Pressing W breaks the loop.