Yes, I mentioned that this macro is "dumb" and is prone to error until all abilities are on CD. It's simply spamming 363636 or what have you.
Is it possible to code the AHK command such that it'll always press a given ability first? I acknowledge that this might not always translate to that ability being cast first anyway due to latency and the likes.
Right now I've just taken to adding a couple more 1's in the send string, but I'm wondering if a more intelligent solution is possible.
I've realised now that this seems to flicker my vent on/off when I am holding down my push to talk and an AutoHotKey. This produces a sort of "cutting out" effect.
Is this simply because of my bad keyboard or is the a work around?
Viridiz, what you're describing sounds a lot like Keyboard Ghosting. There are a lot of good explanations of it on Google, if you know what its called. The long way around it would be to find out exactly what keys on your keyboard share a signal path, and bind accordingly. The short way is to bind your vent button to something else, and test until it works right. Alternatively, if you have a PS/2 keyboard (not Playstation, I mean the oldschool keyboard/mouse plugs) and your motherboard supports it, give it a try; they usually have less of a problem with key ghosting than USB keyboards do, unless you buy one of the few gaming keyboards that tout "anti ghosting technology", which is usually just a special diode in each switch (read: pricey).
It's definitely not keyboard ghosting, that would just make his vent button/other key work or not work, not 'flicker'. It may be just that he needs to use the Sleep 1 mentioned, to tell the AHK process to yield after every keypress so as to not hog too much CPU.
Thanks for replying, I use my keyboard with the PS/2 adapter anyway.
I think there's a few other things I may need to mention, I currently use a little app that turns off my capslock whenever I let go of the key, and when I hold a "turbo'd" key like swipe and hold capslock I see the light flashing on and off. The app doesn't turn off capslock till I release the key.
Quick question for you folks, I use a lot of my spells via the number pad. How do I add a number pad 1?
For instance this script works for the 3 button, but not for numberpad 1. My character will cast number pad 1, but also open every window in wow and then crash WoW. Any suggestions?
#ifWinActive World of Warcraft
{
$Numpad1::
Loop
{
if not GetKeyState("Numpad1", "P")
break
Send Numpad1
sleep 1
}
return
$3::
Loop
{
if not GetKeyState("3", "P")
break
Send 3
sleep 1
}
return
}
This thread have more than 2 years now, I wanna know: during this time, does anyone who have been using ahk just for spamming a spell when a key is held down have been banned for this or know someone who have been banned for this ? I ask because I'd really like to fix this error of gameplay from blizzard but don't want to be banned for such a ridiculous reason, and since I read "It seems with recent bans, this may not actually be the case.", it may mean that those people have been banned for this...
Has anyone had success with making a script that will also utilize the grave key, a.k.a ` ? What about one for `,1,2,3,4,5
Would be pretty sweet actually heh
The code for numbers has been posted in the OP of this thread. Just have to have 5 cases, one for each number.
For grave key, make a 6th case and escape the grave with another grave except in the first/case line:
$`::
Loop
{
if not GetKeyState("``", "P")
break
send ``
sleep 35
}
return
Having a weird issue with AHK currently, if caps locks is on, and caps locks is bound to anything, caps is spammed along with with the numbers. I had caps bound to death grip and every I press 1-6 caps deathgrip is spammed.
<quote>#ifWinActive World of Warcraft
{
~Enter::Suspend, toggle
~Esc::Suspend, off
~R::Suspend, on
~BS::
~/::
IfEqual, A_IsSuspended, 1, Return
Suspend, on
Return
$1::
Loop
{
if not GetKeyState("1", "P")
break
Send 1
sleep 1
}
return
$2::
Loop
{
if not GetKeyState("2", "P")
break
Send 2
sleep 1
}
return
$3::
Loop
{
if not GetKeyState("3", "P")
break
Send 3
sleep 1
}
return
$4::
Loop
{
if not GetKeyState("4", "P")
break
Send 455
sleep 1
}
return
$5::
Loop
{
if not GetKeyState("5", "P")
break
Send 5
sleep 1
}
return
$6::
Loop
{
if not GetKeyState("6", "P")
break
Send 6
sleep 1
}
return
$7::
Loop
{
if not GetKeyState("7", "P")
break
Send 7
sleep 1
}
return
}
return</quote>
I also use capslock as a keybind, and had this issue. The workaround I came up with was to add a line to AHK that sets capslock to off whenever capslock is pressed. Really, do you ever want capslock on? I'm not on my gaming computer so I don't have the code to do this handy, but it's pretty simple.
How is the new spell queue going to interact with AHK? I see it being a real problem if the queue can start as soon as the previous spell is cast. We'll be locked into casting the spell we just cast because AHK has fired an additional command to the server.
Did Blizzard disable AutoHotkey in the latest patch? I ask because I've used it for months before now with no problems, and suddenly it stopped working after the latest patch. The script (which is a basic key spammer, so I don't have to spam the keys myself) still works on other programs, just not WoW.
I can confirm that using a simple "press '3' at 50ms intervals while I hold the '3' key down" function is still working with WoW itself - using this function, if I hold '3' while typing into the chatbox the key immediately repeats rather than waiting ~0.5s and then repeating (which is windows standard behaviour and what happens when holding any other key).
*However*, it's possible that Blizz have changed the way the client or server responds to spammed keypresses. You could test this by comparing how many casts you could get off in a minute using manual spamming versus using the function; for me though the purpose of this sort of function is to save my fingers more than anything else and regardless of any changes to the way WoW functions, that purpose remains useful.
I just came back to wow after just over a year away from the game and my ultra simple AHK spam script doesnt seem to work" Any help would be greatly appreciated.
Here's the script:
#ifWinActive World of Warcraft
{
$3::
Loop
{
if not GetKeyState("3", "P")
break
Send 3
sleep 1
}
return
}
has this stopped working since latest mini update yesterday?
Originally Posted by Petrocity
Did Blizzard disable AutoHotkey in the latest patch? I ask because I've used it for months before now with no problems, and suddenly it stopped working after the latest patch. The script (which is a basic key spammer, so I don't have to spam the keys myself) still works on other programs, just not WoW.
Autohotkey is not an addon, it sends keys just as if a person would press them manually, Blizzard can not disable this.
Originally Posted by rex4
This thread have more than 2 years now, I wanna know: during this time, does anyone who have been using ahk just for spamming a spell when a key is held down have been banned for this or know someone who have been banned for this ? I ask because I'd really like to fix this error of gameplay from blizzard but don't want to be banned for such a ridiculous reason, and since I read "It seems with recent bans, this may not actually be the case.", it may mean that those people have been banned for this...
It is close to impossible to actually determine if the spam is automated or manual, hence I would guess noone has been banned solely due to the 1-key solution. People have however been banned for using autohotkey for ie. afking in bgs.
Autohotkey is not an addon, it sends keys just as if a person would press them manually, Blizzard can not disable this.
It is close to impossible to actually determine if the spam is automated or manual, hence I would guess noone has been banned solely due to the 1-key solution. People have however been banned for using autohotkey for ie. afking in bgs.
Yes, but its been Blizzard's policy that one keystroke can only cause one action. I know that they did not support using the G15 keyboard's macro feature to accomplish the same effect as this program (spamming a key by holding it down.) So while they may not be able to detect the program's use, my guess is that if they could, it would be ban-worthy.
From my limited testing, i found i was able to spam keypresses at approx rate of 6 per second.
A sleep time of 1 is way in excess of this and blizz are more than capable to detecting someone flooding info at them from 1 spammed key.
Solution is of course to increase the sleep time to something approximating the 6/sec mark.
When i did this all was fine.
05/08/10, 3:26 AM
Similar Threads
