Press tilde (~), input the following, and press enter:


If you only came for toggle sprint, then consider this the end of the guide.

Documents > My Games > KillingFloor2 > KFGame > Config > KFInput

Scroll all the way to the bottom, then scroll up until you find

Replace it with

*Notice how the only difference is that you remove "toggle bRun"
These should all be one line btw.

If you find [Configuration], then you have gone too far (or just ctrl+F it).

Let us take a closer look at the binding we just did, shall we?


setbind is the command that allows you to rebind a key.
As you are typing in the command prompt, you should notice the game giving you hints as to what command you want to use.

If you type setbind, you should notice underneath it saying:
SetBind BindName[FName] Command[FString]

The [FName] requires the name of the keystroke, while [FString] requires a command.
In the case of the BindName[FName], we did leftshift.
For Command[FString], we did toggle bRun.

Now you could theoretically put anything you want.
For example, you can do
and you will create a line in KFInput that is

Problem is that there is no such key on your keyboard called ROFLCOPTER, and no such command called Hi, hoe.
That is to give you an idea with what is happening under the hood.

Try experimenting with commands. Don't start with setbind. Type s, and notice all the possible commands that you can do. Do it with another letter, and another. There are a lot of commands to choose from, all of which can be used in Command[FString] for setbind. If you want to cycle through these commands, open the command prompt with F3, then use the arrow keys to cycle through the commands.

The downside to using the command prompt is that you are limited in what you can do. You cannot use commands in conjunction to shift, ctrl, or alt; and it is more of a hassle to modify your existing commands.

This is the devs' sprint command

Button bRun... Toggle bRun... I am sure you can figure out what Button and Toggle do ;)

add is from the number pad.

That vertical slash is the drop weapon keybind from KF1, that is if you are holding shift while doing it. It allows you to chain multiple commands into one keybind. Make sure you include quotes if you chain commands, or it will not work.

I just gave you the path to the file where all of your setbinds and other commands get stored. You might want to create a shortcut somewhere... and a backup so the next update can reset your file without pi$$ing you off..

Between [Configuration] and [Iniversion] is where you will be messing with your commands: at the bottom of the file.

Remember this?
The game looked through KFInput when you did that to see if there was a binding for leftshift, and there was. So instead of creating a new line for leftshift, it was remapped.

Now the reason for the italics and underlining in the code snippets is to show you what changes if you use something other than leftshift or a command other than toggle bRun from using the command prompt ingame.

Now for the Control=False,Shift=False,Alt=False,bIgnoreCtrl=False,bIgnoreShift=False,bIgnoreAlt=False (D@mn, that is a mouthful...). If you set Control, Shift, or Alt to true, then you have to hold down that key in conjunction to your keybind. If you set bIgnoreCtrl, bIgnoreShift, or bIgnoreAlt to true, then the command will not happen when you hold any of the those keys in conjuction to the keybind.

Here is an example:
I know it looks messy, but notice how the first command has bIgnoreAlt set to true, and the second has Alt set to true. The first command will toss 50 dosh when you press B. The second one will toss 500 dosh when you hold alt and press B. If bIgnoreAlt on the first command was set to false, then you would have executed both commands by holding alt.

Now instead of using keys from your keyboard for BindName[FName], we can do ROFLCOPTER. No I am not kidding.

*I added the say so the command will work.
Now that you have created the command ROFLCOPTER, you can use it for Command[FString].
Press J, and you will say "Hi, hoe."

How about a more familiar example from the devs?

I would recommend having all of your custom commands to start with the same name.
Example: Custom_Poof, Custom_MegaMan, Custom_Sprint

No problem! Just go to the ingame keybinds menu, and map the desired key to some random command that you don't give a $hit about. Then you go to KFInput and search through your keybinds until you find the the command you set the key to. If the key was never previously mapped before, you should find it just above [Iniversion].

I once tried to figure out what (-) was called. It wasn't minus, and subtract was already reserved for the number pad. I went to the ingame keybinds and mapped it to Last Used Weapon. I went to KFInput and found this just above [Iniversion]:
Now I know it is called underscore. Never would have guessed. If you try this with a different key, and it is not on the very bottom of the keybinds, then it was previously mapped to something else. Just look for Command="GBA_LastWeapon", and you will find it (assuming you had it bound to Last Used Weapon).

http://gtm.steamproxy.vip/sharedfiles/filedetails/?id=668130568
http://gtm.steamproxy.vip/sharedfiles/filedetails/?id=424641626