Now I’ve seen a few posts pop up every now and again about setting certain actions (eg. long-jump / super-jump, etc.) to Custom Keybinds, so for the sake of newcomers I decided to make this short and simple guide; since none exists on the forums that I can find.
First, and foremost, you should know the specific designations of each keybinding in relation to Unreal Engine 3’s (i.e. UE3) terminology. Without knowing the correct terms the commands to set these Custom Keybinds will not work. For the sake of reference here is a link, straight from the official documentation for UE3, that has a list of the available Key Bindings.
Unreal Engine 3 Keybinds
Basics of Custom Keybinds
Now with regards to actually creating the Keybind for the action in question, in this case we will use long-jumps as an example and bind it to the Left Alt key, normally you would launch the game and open the console. After doing so you would input, into the console, the following command line:
SetBind LeftAlt “Duck | Jump” 1
Now whenever you press the Left-hand Alt button you will perform a long-jump on demand. Using this method, however, you are required to re-enter the command line any time there is a major update to the game that would reset the “.ini” files containing the in-game settings. So for the sake of convenience we will create an auto-executable (ie. AutoExec) file that will automatically run the command line every time the game is launched.
Creating an AutoExec File
Now to start off open up Notepad, or any other basic text-editing software available, and type the same command line in. After this save the document but do not confirm the save just yet. You want to first navigate through your main Hard-drive to the programs folder for Steam. After that follow through the corresponding path of “SteamApps>Common>Dirty Bomb>Binaries” and than go down to the file format. Upon clicking it should show a drop-down menu, click “All Files”. Now input the name you will save it as, which is “autoexec.cfg”, and confirm the save. You will want to make sure to enter the file extension otherwise this doesn’t work. Last thing you need to do is go to your Steam Library and right-click on Dirty Bomb. This will open a drop-down menu once more, click on “Properties” and finally on “Set Launch Options”. This will now open up an input box into which you will enter the following command line:
Now when you launch your game whatever commands are currently inside that file will automatically be run which means you will never lose your Custom Keybind.
Special Thanks to:
Sgt. Peperoni for his Steam Guide on the subject. It is part of what prompted me to make a similar guide here where it is more immediately visible to new players.
You can find his guide here:
If any errors are present in this guide or you have a question feel free to post a comment and I’ll get back to you as soon as I can.
Frequently Asked Questions (F.A.Q.)
Question: I’ve set the Custom Keybind to and it isn’t working. Why?
Answer: There are a few things that can cause the Custom Keybind to not function properly, so the easiest way to solve the problem is by eliminating the possibilities one-by-one:
The most basic of causes is that the Custom Keybind in question is bound to a Key Binding already in use for another action in-game; simply Unbind it via the in-game Control Settings and then restart Dirty Bomb.
Another possibility is that the Command Line was entered incorrectly (improper syntax or structure, etc.).
The last notable possibility is that the Key Bind Name that was entered was incorrect, and didn’t correspond to any of the Key Bindings that Unreal Engine 3 (i.e. UE3) recognizes; be sure to double check ,via the associated link in the guide, and ensure the Key Bind Name matches up with the one listed in the linked UE3 Documentation.
Question: I’ve set everything up properly but it still isn’t working. What do I do?
Answer: Make sure you completed the final step mentioned in the Guide properly, and that the associated Launch Option Command Line is entered correctly; the Auto-Executable is inactive without this Command Line as it prompts Steam to direct the Game Client to load & run the file in question before launching.
Question: Does the name of the .cfg file matter?
Answer: No, it doesn’t. The name used in this guide is merely for the sake of convenience in explaining the topic; as long as it is a .cfg file, and is stored in the proper location on your Hard Drive, it shouldn’t matter what you name the file. It should be noted that the name of the file must match the one you use in the Launch Option Command Line, otherwise it will not load the Auto-Executable and run its Command Lines.
February 4, 2018
- Updated the layout slightly
- Improved emphasis to key points of the guide
- Added the missing step for setting up the “AutoExec” file.
June 4, 2018
- Added a F.A.Q. section to the guide
- Slight alterations to layout
- Improved emphasis to key points of the guide