mikeyww wrote: ↑11 May 2024, 21:22
Just another idea here.
Code: Select all
#Requires AutoHotkey v2.0
*RButton:: Send('{Blind}{q DownR}'), Send('c')
*RButton Up::Send('{Blind}{q up}')
It's a great idea, and I believe I've attempted it before, though I'm not sure why I didn't pursue it further. Perhaps it's because I'm not entirely comfortable with AutoHotkey; most of the AHK code I use has been sourced directly from the internet. I try to comprehend its functionality and then modify it to suit my needs.
,This indicates that I have no understanding of the fundamentals of AHK.)
I attempted your suggestion, but unfortunately, one game still detects that I'm using AHK to issue keyboard commands. Substituting wheelup/down works, but it doesn't prioritize the commands as highly as the keyboard does. For instance, if I want to send a command as soon as I press the RButton, "c" is transmitted to the game faster than "wheelup/down." My guess is that it might be due to the game using the EAC driver level to intercept mouse or keyboard commands.
Imagine you want to maintain the RButton pressed for in-game aiming while sending 'j' (presumed to be an emote) and then hitting 'q' (presumed to be a skill). If the 'j' command is not executed concurrently with the RButton, it will cause the in-game aiming to disengage, even though the RButton has not been physically released.
在下面的程式碼中,產生的行為RBtutton == 'RBtutton' , "j" == "{wheeldown}", "q" == "{wheelup}"
- This code should function properly within the game and not interfere with the continuous pressing of the RButton command.
Code: Select all
*RButton:: Send "j{Blind}{q DownR}"
*RButton Up::Send "{Blind}{q up}"
I assume that in-game commands such as "RButton down", "j", and "q down" are recognized either simultaneously or with minimal delay.
- The code functions correctly within the game; however, the "RButton down" command gets interrupted in-game, leading the game to mistakenly register the RButton as being continuously pressed, despite it being physically held down.
Code: Select all
*RButton::
{
Send "{wheeldown}"
Send "{wheelup}"
}
I believe that among the in-game commands "RButton down", "{wheeldown}", and "{wheelup}", the "RButton down" command is executed first. Subsequently, the "{wheeldown}" command recognizes it and interrupts the ongoing press of the "RButton".