Post Patch COD4 Fire Rate

[toysrme]

566rpm
53ms down+53ms up
anything below that will result in the game skipping inputs
(for an equal trigger up/down time (i.e. no "tricks" being used)

This can be exceeded somewhat using lots and lots of tricks, but not enough to be worth it at this point IMO less someone comes out with something in the future (why when MW2 is about to come out and its been stated that it will work differently)

Just thought Id let yall know that since alot of people think it's in the 400rpm range.

[n1gh7]

Just a question... how did u find this out?

[toysrme]

because 53ms is the smallest trigger time allowed that doesn't skip the fire rate on a G3. 52/52, 52/53, 53/52 will all begin to skip.

#NoEnv
SendMode Input
SetMouseDelay, -1
SetKeyDelay, -1

~Space:: ;Use the space key to quickly toggle the script on & off
        Hotkey, ~LButton, toggle
If toggle != 1
         {
          toggle := 1    ; Will beep if it is set to on
          SoundPlay *84 ;Good because it plays over primary speakers. Others tend to play on motherboard speakers. It's 2008 many computers no longer have motherboard speakers!
          }
else
         {
          toggle := 0        ; Will beep if it is set to off
          SoundPlay *64 ;Good because it plays over primary speakers. Others tend to play on motherboard speakers. It's 2008 many computers no longer have motherboard speakers!
          }

_auto := true

~LButton::autofire()
~^LButton::autofire()
Code:


\::suspend ;\ key completely suspends the script
autofire()
{
global _auto
if _auto
{
{
Loop
{
if GetKeyState("LButton", "P")
{
Test1 := A_Index ;Test1 = A variable that carries outside of the loop, A_Index = how many times this specific loop has run.
SendInput {LButton Down}
Sleep, 53 ;Time to wait in MS
{
 If ( mod(A_Index, 3) <> 0 )
mouseXY(0,2)
}
SendInput {LButton Up}
Sleep, 53 ;Time to wait in MS
}
else
break
}
} ;; loop
} ;; if
} ;; autofire()

mouseXY(x,y)
{
DllCall("mouse_event",uint,1,int,x,int,y,uint,0,int,0)
}
return
;;;;;;
;;; End script


[toysrme]

In that code what you want to pay attention too is the sleep times of 53ms (i.e. how long to signal something is held down, and how long to signal there is no input)


60,000ms in a min
60,000ms / (53ms+53ms) = 566rpm

[n1gh7]

And where did you find that?

[toysrme]

ive got alot of experince scripting through menu's, finding fire/button rates. finding the exact & practical limits. getting around some of them. i write them for some games i like. specially console games that are overloaded with queer menu's.

been scripting on 360 for about a year now. not a pro, but i can do about anything you want. blah people life auto-fire scripts/mods. they're fun to play with when the games get patched just to try to spend hours trying to figure out what they changed.

at this point in W@W (well i quit playing W@W along time ago, assuming they've not aptched it AGAIN) the tough rules for the right trigger dont entirely apply to the left trigger (ROTFLMAO!) so you swap triggers, and without using ANY tricks. set the button released time to 26ms. boom 650-700rpm pretty easy to do with no tricks.

OFP:DR sucks on PC, but you can bind your way through most of the obtrusive menus. console its better (still buggiest game on console in years) but the menus SERIOUSLY detract from SP/COOP action (SP AI so buggy its terrible, MP is just a HORRIBLE experince)
once you get good at the menu's you may take 5-10-15-30 seconds trying to give the AI 3-4 basic commands.
meh, you can give 3 a second if your timing is halfway worth anything.

did some menu functions for console halo wars (crappy game) and supreme commander (awesome on PC, sucks on console, will NEVER be close to what total annihilation was when it was released)



so if i say it's xxx ms there you go. where people with controller mods get "iffy" is when you question how accurate their hardware/software timing circuits are.

[Aphoristic]

^
I would actually be interested in some Halo Wars info. (ya I know it's crappy)