The "exec" command.
Posted: Fri 28 Jan , 2011 1:03 am
The command "exec" in console followed by the name of a text file in the System directory executes all valid commands in that file.
For example, consider two example text files, ASBinds.txt and CBBinds.txt.
ASBinds.txt:
and CBBinds.txt:
Typing exec ASBinds.txt will apply Assault keybindings and typing exec CBBinds.txt will apply CarBall bindings. I know the bindings are shitty but they're just an example of how you can switch your binds between mods without spending ages setting them.
Exec will execute any valid commands, and will execute them as fast as possible. I used execs to apply tons of cmdonplayer commands within a very short time in the FarNy incident.
There is an important caveat with this, however - piped binds don't work, or at least, they don't work in Windows 7. This means binds like set input x scopeview | onrelease scopeviewrelease can't be applied with this method.
For example, consider two example text files, ASBinds.txt and CBBinds.txt.
ASBinds.txt:
Code: Select all
set input space jump
set input shift walking
Code: Select all
set input space cbquickflip
set input shift cbwheely
Exec will execute any valid commands, and will execute them as fast as possible. I used execs to apply tons of cmdonplayer commands within a very short time in the FarNy incident.
There is an important caveat with this, however - piped binds don't work, or at least, they don't work in Windows 7. This means binds like set input x scopeview | onrelease scopeviewrelease can't be applied with this method.