The AutoHotKey Thread - Page 5

Prinsesa · 10/09/09, 9:27 PM

I'm currently using the following script for my Paladin:

$1::
   Loop  
   {
    if not GetKeyState("1", "P")
      break
     Send, 1f3g45
     sleep 1
    }
return

In essence, as long as the 1 key is held down, the string "1f3g45" is sent over and over. My various Ret abilities are bound to 1, f, 3, g, 4 and 5, which effectively allows this macro to fire off my abilities as soon as they come off cooldown, albeit rather randomly if they're all still available.

My question is: Is it possible to code some kind of delay or selection such that one set of buttons will always be pressed ahead of others? This would be useful when dealing with abilities that have no cooldown, such as a Shaman's elemental Shields.

The current method I'm using would cause a Shaman to cast his Lightning Shield over and over and miss the Flame Shock cooldown for some random amount of GCDs, and I'm wondering if you can program some kind of "fall-through" or priority to the keybinds so that it only goes to the non-cooldown ability after everything else has been expended.

Machinator · 10/11/09, 2:20 PM

Originally Posted by Skyhoof

You cannot use AHK or the G15 keyboard to spam a single key -- even if you are sitting at the keyboard and just want to prevent your finger from falling off.

Reading the blue posts on this subject I am a bit confused if this would be legal or not. Holding down a button so that the script continually sends that key to WoW without any delays or other conditionals, and the key is assigned not to a macro but a single ability that is not on the GCD.

I would like to use Heroic Strike, which is a on-next-swing attack, when I am holding down the button rather than hitting the button more than once a second in addition to my normal rotation. I would also like a toggle so I dont have to hold down the button but that does seem clearly against ToS.

Blue posts seems to indicate it is delays that are the issue, so I am not sure if the quoted line is a generalization or if policies have been updated since early 2008.

ricco19 · 10/14/09, 8:23 AM

I am currently having issues trying to get an autohotkey script to work, and figured this was a good place to possibly get some help.

Basically the main issue I am having is trying to remap shift so that I can bind shift+numpad keys. For example, if I hit shift+numpad1, the actual keystroke is End. However, End is already bound to something else. I figured a good way to fix this issue would be to remap shift to another key such as alt. I first tried a basic script, like this.

EDIT: Problem fixed...

• Titanstrider · 10/14/09, 1:30 PM

Originally Posted by Machinator

Reading the blue posts on this subject I am a bit confused if this would be legal or not. Holding down a button so that the script continually sends that key to WoW without any delays or other conditionals, and the key is assigned not to a macro but a single ability that is not on the GCD.

I would like to use Heroic Strike, which is a on-next-swing attack, when I am holding down the button rather than hitting the button more than once a second in addition to my normal rotation. I would also like a toggle so I dont have to hold down the button but that does seem clearly against ToS.

Blue posts seems to indicate it is delays that are the issue, so I am not sure if the quoted line is a generalization or if policies have been updated since early 2008.

If you want to queue up heroic strike for every swing, just add the following to a macro for each of your normal attacks:

/cast !Heroic Strike

This will toggle it on, and multiple key presses won't toggle it back off the way a normal /cast Heroic Strike does. Make the equivalent macros for all your normal rotation abilities; my main's a druid and I have Maul added to all my tank roation attacks this way. So as you use your normal rotation, you'll also be keeping HS queued up, without needing any extra key presses:

#showtooltip Devastate
/cast Devastate
/cast !Heroic Strike

Machinator · 10/15/09, 8:43 AM

There are a couple issues with doing that. First is that then you can't stop doing HS if needed, such as low rage. Second is that HS often needs to be hit more often than once per GCD.

• Titanstrider · 10/16/09, 6:44 PM

You could create a button holding /cast !Heroic Strike and assign that button to the mouse scroll wheel. Then use the scroll as needed/wanted, and get it to fire many times per second.

Wtfitzandy · 10/18/09, 1:24 PM

Maybe my keyboard keys will finally last a little bit longer with this x.x

My "W" "S" "A" "D" keys are literally gone from me keyboard =/

Will give it a shot.

• Koban · 10/19/09, 8:56 AM

So, after about 5 months of inactivity I've decided to reactivate my account.

Here's my problem.
I've always used an AHK script to replicate keypresses. This used to work almost perfect and I've never had any problems with it until now.

Here's the script I used:

#ifWinActive World of Warcraft
{
$&::
   Loop  
   {
    if not GetKeyState("&", "P")
      break
     Send & 
     sleep 1
    }
return
$é::
   Loop  
   {
    if not GetKeyState("é", "P")
      break
     Send é 
     sleep 1
    }
return

$"::
   Loop  
   {
    if not GetKeyState(""", "P")
      break
     Send " 
     sleep 1
    }
return

$(::
   Loop  
   {
    if not GetKeyState("(", "P")
      break
     Send ( 
     sleep 1
    }
return
$v::
   Loop  
   {
    if not GetKeyState("v", "P")
      break
     Send v 
     sleep 1
    }
return

~Enter::Suspend, toggle
~Esc::Suspend, off
~r::
IfEqual, A_IsSuspended, 1, Return
Suspend, on
return
}

The only thing that has changed between now and 5 months ago is my OS. I've upgraded to Windows 7 Ultimate, but as far as I can look up on Google there have been no known problems between ahk scripts and Win 7.

So if anyone has any idea's on how to fix this, please do not hesitate to post.

Edit: Post can be deleted, the excellent people at AHK found my problem. (Set admin priviliges to autohotkey.exe and make sure the right executable is used.)