DDNet client has a multitude of commands and settings that can be bound to nearly any key or mouse button. You can enter commands into the console, which by default is accessed by pressing F1.
bind [key] [command/setting] [value]
This is the basic syntax for simple binds.
- [key] is the key on your keyboard/mouse you want to bind a command to.
- [command/setting] A full list of all commands and settings can be found here.
- [value] is the variable you want to set your setting to or an argument for a command. Not all commands require arguments
You can find keycodes here, or just type the key temporarily into one of the controls in the Settings > Controls page in DDNet client and it will show the key name. You can also use modifier keys with binds.
bind ctrl+[key] [command/setting] [value]
you can use ctrl, alt, and shift.
You can also chain commands/settings together by separating them using a semicolon and wrapping them in quotes. You can add as many commands to this chain as you want.
bind [key] "[command/setting] [value]; [command/setting] [value]"
It's important to know that when chaining things together like this, all commands/settings get executed by the game at the exact same time, meaning they will not execute in the order you write them. There is no sleep or delay type command to space things out the way you want them. The best way to make things happen in an ordered sequence is to either bind a different key for each step of the sequence, or to use config files to press one key multiple times to read multiple files.
You can nest multiple quoted strings in a single line by escaping each new set of quotes with backslashes.
bind [key] "bind [key] \"[command/setting] [value]; bind [key] \\\"[command/setting] [value] \\\"\""
As the quoted strings go deeper, you also need to escape the backslash. Since each new layer will again un-escape them, you need to double the amount of backslashes per layer. The third layer will require 3 backslashes, the 4th will require 7, etc. If this is confusing to look at, try making a new line for each escaped quote to get a more clear visual idea of what's happening.
bind [key] "bind [key] \"[command/setting] [value]; bind [key] \\\"[command/setting] [value]; bind [key] \\\\\\\"[command/setting] [value] \\\\\\\" \\\" \" "
Toggles are a way to use a single key to alternate between 2 values for a setting. There are two types of toggles.
- toggle is used so that each time you press a key, it will change between one of the two values for the setting
- +toggle is used so that your first value is set only while the key is being pressed, and the second value is set while the key is not being pressed.
bind [key] "toggle [setting] [value1] [value2]"
bind [key] "+toggle [setting] [value1] [value2]"
Toggles only work for client settings. They cannot be used for client or chat commands.
Say is an important client command for binding. It allows you to incorporate chat commands into a bind as well as just send text to the chat.
bind [key] say /[chat command]
bind [key] say [chat message]
Some client commands allow you to set colors.
are a few examples.
To get the correct color values, go to Settings > Tee, and use the sliders to find the color you want. Go into the console and type the command for the color you're trying to set, by itself with no value. The number that comes after "Value:" is the relevant number.
It will also accept a few color values by name. red, yellow, green, blue, cyan, and magenta, all work.
You can use this command to print what's bound to a single key. Use it without a key at the end to get a full list of all your current binds.
Will unbind whatever key you specify.
Using Config Files
For more complicated binds, you can make text files containing settings/commands that get executed via a key press.
[command/setting] [value] [command/setting] [value] [command/setting] [value]; [command/setting] [value] [command/setting] [value]; [command/setting] [value] bind [key] [command/setting] [value] bind [key] exec [file.cfg]
Settings/commands can be chained together via a semicolon or by just using a new line. You can put as many commands/settings/binds as you want in these files.
Note: You don't need to use .cfg as the extension. You can actually use any file extension you want. .cfg just seems to be the standard.
In order to execute these files, you need to put them in correct directory and execute them with the exec command. The correct path depends on your operating system.
An easier way to find this folder is to press win+r to open the Run dialog, and paste the path above.
The library folder might be hidden by default. In Finder, click the Go menu in the menu bar. If you hold the alt key, the Library folder will appear.
Once the files are in the correct path, you can execute them in the game console with the exec command.
bind [key] exec [file.cfg]
You can use sub-directories within the 'Teeworlds' directory to organize files. Just include the path when you execute the file.
bind [key] exec [path/to/file.cfg]
Improved toggle with config files
The most common reason to use config files is to create a single-key toggle to alternate between two files.
[command/setting] [value] [command/setting] [value] [command/setting] [value] bind [key] exec file2.cfg
[command/setting] [value] [command/setting] [value] [command/setting] [value] bind [key] exec file1.cfg
In this case, [key] would be the same key in both files. This way each time you press the key, it will switch to the other file. Once you have both of these files in the correct path, you can exec either one just once and they will be bound forever until you unbind them.
bind [key] exec file1.cfg
You can use this method to cycle between any amount of files.
As a more clear way to show which file you're activating when you press a bind, you can use the echo command command to display which one is active.
[command/setting] [value] [command/setting] [value] echo setting ON bind [key] exec file1.cfg
To take this a step further, there is a command to change the color of the echo messages.
[command/setting] [value] [command/setting] [value] cl_message_client_color red echo setting OFF bind [key] exec file1.cfg
Having different colors for "on" and "off" binds makes it a bit easier to notice which setting you've activated.
You can put comments in your bind files too.
# These lines change some settings [command/setting] [value] [command/setting] [value] # This next line rebinds the key bind [key] exec file1.cfg
Hook line always on
The command cl_show_hook_coll_own, sets whether you will see your own hook collision line or not when you hold your +showhookcoll bind (defaulted to S). When set to 2, your hook collision line will always show only to you. Others players won't see it.
cl_show_hook_coll_own 2 cl_message_client_color green echo Hook Line ON bind x exec hook_line_off.cfg
cl_show_hook_coll_own 1 cl_message_client_color red echo Hook Line OFF bind x exec hook_line_on.cfg
Put both of these in the correct path, and in console:
bind x exec hook_line_on.cfg
The deep fly bind is a way to make your dummy hammer/fire toward you whenever you fire with your main tee. If your dummy is deep frozen, they can hammer back at you when you hammer them with this bind on. You can use this to fly with your dummy, but it takes practice. If your dummy is not deep frozen, you can just use this as a alternative version of the regular Dummy Hammerfly bind included in the games settings, where you can fire your pistol each time you want to be hammered. It offers better control since you can control the timing of your dummy's hammers.
The command cl_dummy_hammer 1 is what is used for the regular Dummy Hammerfly bind in the games control options. By using a toggle, you can make your dummy hammer you only when you fire, and can make an on/off switch with config files.
bind mouse1 "+fire; +toggle cl_dummy_hammer 1 0" cl_message_client_color green echo Deep Fly ON bind x exec deepfly_off.cfg
bind mouse1 +fire cl_message_client_color red echo Deep Fly OFF bind x exec deepfly_on.cfg
Put both of these in the correct path, and in console:
bind x exec deepfly_on.cfg
Note: This assumes mouse1 is your +fire bind
If your dummy isn't holding hammer when you turn the bind on, they will switch back and forth between pistol and hammer. If you want to fix this:
Now if they're holding pistol when you start using the bind, they will switch to hammer and stay there after 1 pistol shot. There are however some benefits of having this setting set to 1.
This will allow you to laser yourself with your dummy with perfect aim. It can also work with shotgun.
bind [key] "+weapon1; cl_dummy_restore_weapon 0"
bind [key] "+weapon5; cl_dummy_restore_weapon 1"
This of course only works if you have dedicated weapon binds as opposed to +nextweapon and +prevweapon which is by default bound to +mousewheelup and +mousewheeldown.
This bind allows you to only aim in 45° angles when holding down the key. This is useful for shooting rockets straight up for double rockets and a few other scenarios.
bind x "+toggle cl_mouse_max_distance 2 400; inp_mousesens 1 200; +showhookcoll"
Keep in mind that if you have changed cl_mouse_max_distance or inp_mousesens from the default, using the example above will reset those settings to default. Before you just enter the binds, check your settings for both first by typing cl_mouse_max_distance and inp_mousesens into the console.
bind x "+toggle cl_mouse_max_distance 2 [Your Value]; inp_mousesens 1 [Your Value]; +showhookcoll"
Note: the cl_show_hook_coll_own line is optional, it's just helpful to see which way you're aiming since your tee's eyes don't follow the 45° constraints.
You will sometimes see players rapidly changing color as they play. To do this you just have to bind a player_color_body change to each of your regular movement inputs.
bind a "+left; player_color_body red"
You can do this for several common inputs and get a variety of colors to cycle through.
bind a "+left; player_color_body red" bind d "+right; player_color_body yellow" bind space "+jump; player_color_body green" bind mouse1 "+fire; player_color_body blue" bind mouse2 "+hook; player_color_body cyan"
Here's an example of what a rainbow tee file looks like. You could save that in the correct path and execute it once.
Or if you want a key to toggle it on and off:
bind a "+left; player_color_body red" bind d "+right; player_color_body yellow" bind space "+jump; player_color_body green" bind mouse1 "+fire; player_color_body blue" bind mouse2 "+hook; player_color_body cyan" bind x exec rainbow_tee_off.cfg
bind a +left bind d +right bind space +jump bind mouse1 +fire bind mouse2 +hook bind x exec rainbow_tee_on.cfg
Put both of these in the correct path, and in console:
bind x exec rainbow_tee_on.cfg
You can of course get more creative with colors and use player_color_feet too. To learn more about how colors work, see colors
Note: This assumes you have default binds for left, right, jump, fire, and hook.