Rapid Fire?

[acidphreaked]

Anyway to rapid fire without getting banned on PC? Don't care about actual cheats, just want a finger saver.

[0x41^4]

Ins::Suspend
LButton::
Loop
{
	GetKeyState, lcstate, LControl
	GetKeyState, lsstate, LShift
	
	If lcstate = D
	{
		Send, {Control}
	}
		If lsstate = D
	{
		Send, {Shift}
	}
SetMouseDelay 30
Click
If (GetKeyState("LButton","P")=0)
Break
}

Insert suspends it.

[acidphreaked]

Originally Posted by -0x41^4-

Ins::Suspend
LButton::
Loop
{
	GetKeyState, lcstate, LControl
	GetKeyState, lsstate, LShift
	
	If lcstate = D
	{
		Send, {Control}
	}
		If lsstate = D
	{
		Send, {Shift}
	}
SetMouseDelay 30
Click
If (GetKeyState("LButton","P")=0)
Break
}

Insert suspends it.

So running AHKs won't lead to bans? I wasn't sure. Haven't played COD on pc before.

[0x41^4]

Originally Posted by acidphreaked

So running AHKs won't lead to bans? I wasn't sure. Haven't played COD on pc before.

Technically it can, as it’s third-party software...
But I have NEVER seen someone get banned for using AHK.

[cue990]

which programm running i have the logitech software^^

[acidphreaked]

Originally Posted by cue990

which programm running i have the logitech software^^

AutoHotKey; youtube how to run an autohotkey script

Originally Posted by -0x41^4-

Technically it can, as it’s third-party software...
But I have NEVER seen someone get banned for using AHK.

Thanks man. The script keeps getting stuck in click mode. It seems if I hold the mouse for around 2.5-3.0 seconds it will get stuck in fire mode and not stop until I click a 2nd time. I tried slowing the click rate but it still gets stuck often, nearly every 3 fights.

Any ideas? Thanks again mate! Very weird bug but 2.5-3.0 seconds of hold seems to have it. I tested 1, 1.5, 2.0, etc and after 3.0 it seems to stop happening.

Was able to produce this bug in game, in IE and in notepad.

[0x41^4]

Originally Posted by acidphreaked

Thanks man. The script keeps getting stuck in click mode. It seems if I hold the mouse for around 2.5-3.0 seconds it will get stuck in fire mode and not stop until I click a 2nd time. I tried slowing the click rate but it still gets stuck often, nearly every 3 fights.

Any ideas? Thanks again mate! Very weird bug but 2.5-3.0 seconds of hold seems to have it. I tested 1, 1.5, 2.0, etc and after 3.0 it seems to stop happening.

Was able to produce this bug in game, in IE and in notepad.

I tried on two different computers and couldn't replicate the problem you're having.

Do you have anything else running (macro wise) or are you toggling frequently?

[acidphreaked]

Originally Posted by -0x41^4-

Technically it can, as it’s third-party software...
But I have NEVER seen someone get banned for using AHK.

Originally Posted by -0x41^4-

I tried on two different computers and couldn't replicate the problem you're having.

Do you have anything else running (macro wise) or are you toggling frequently?

HotKey, *LButton, Off ;Initially, the Fast Fire part is deactivated
Return ;End of Auto-execute Section https://autohotkey.com/docs/Scripts.htm#auto
/::suspend
*F8::Hotkey, *LButton, % (Toggle := !Toggle) ? "On" : "Off"
*LButton:: ;Fast Fire part
	SetMouseDelay 48
	While GetKeyState("LButton","P")
		Click
Return

This seemed to fix it.

[0x41^4]

Originally Posted by acidphreaked

HotKey, *LButton, Off ;Initially, the Fast Fire part is deactivated
Return ;End of Auto-execute Section https://autohotkey.com/docs/Scripts.htm#auto
/::suspend
*F8::Hotkey, *LButton, % (Toggle := !Toggle) ? "On" : "Off"
*LButton:: ;Fast Fire part
	SetMouseDelay 48
	While GetKeyState("LButton","P")
		Click
Return

This seemed to fix it.

It's the exact same thing, just a longer delay.

[acidphreaked]

Originally Posted by -0x41^4-

It's the exact same thing, just a longer delay.

Essentially same thing, just worded differently and for some reason even when setting yours to 100 ms delay, I could still get the bug where it would spam on and stay on. Yet with this I can set a delay as low as possible and no auto bug.

Has to be something with the way its worded. So strange. I tried on my laptop and got same results.

[0x41^4]

Originally Posted by acidphreaked

Essentially same thing, just worded differently and for some reason even when setting yours to 100 ms delay, I could still get the bug where it would spam on and stay on. Yet with this I can set a delay as low as possible and no auto bug.

Has to be something with the way its worded. So strange. I tried on my laptop and got same results.

Weird. I had several people try and nobody else had issues. I wonder if it has something to do with your in-game settings or gun that you used.

Been using is since you posted to test and it hasn't bugged once.

[acidphreaked]

Originally Posted by -0x41^4-

Weird. I had several people try and nobody else had issues. I wonder if it has something to do with your in-game settings or gun that you used.

Been using is since you posted to test and it hasn't bugged once.

Even with game closed using chrome as the test. I could click in a certain way that would cause it to go on and stay on. Thought maybe it was the mouse so I switched from a MM710 to a G502 and had same issue. It must be something with rapid activation times or something similar. If I rapid clicked left mouse I could get it to bug almost every 3rd click.

Strange indeed.

Figure I'd post what fixed it for me incase someone ever has the same issue.

[0x41^4]

Originally Posted by acidphreaked

If I rapid clicked left mouse

That's why it's bugging. You can't spam click rapid macros as that is the purpose of the macro. It's resetting the delay too frequently and therefore getting stuck.

Rapid fire macros are designed to be held down, not spammed, that's why it's a rapid fire macro

[acidphreaked]

Originally Posted by -0x41^4-

That's why it's bugging. You can't spam click rapid macros as that is the purpose of the macro. It's resetting the delay too frequently and therefore getting stuck.

Rapid fire macros are designed to be held down, not spammed, that's why it's a rapid fire macro

That much I get, but I was running into issues with 2 seconds of fire, break 2 seconds of fire, then it got stuck. Not so much spamming it.

[0x41^4]

Originally Posted by acidphreaked

That much I get, but I was running into issues with 2 seconds of fire, break 2 seconds of fire, then it got stuck. Not so much spamming it.

Strange. Nobody else in our Discord had issues with it.

Glad you found something that works, though you might want to add a control and shift block so you don't stop firing if you drop-shot or run.