Example keys replace existing binds. Test changes safely before saving.
Save tested changes
writecfg
How to use, save and remove binds
PC Rust. Example keys can conflict with your controls. Test one change at a time somewhere safe, then save only what you want to keep.
+ means held; no + can keep an action running. ~ cycles values. A continual action is not automatically a press-again toggle.
writecfg also saves removals. Copying here only copies text; Rust runs it after you paste and press Enter.
To restore a previous control, re-enter its original bind or reassign it in Rust's Options, then run writecfg. Clearing a key does not restore defaults. Back up keys.cfg and client.cfg in Rust's cfg folder before larger changes.
Mode 2 waits for server feedback instead of local prediction, so ordinary hit feedback can arrive later. It does not change hit registration or damage.
hitnotify.notification_level 2
Statically verified in PC client build 25903346 and server build 25902425 on 20 October 2026; not tested in-game.
Stop or undo
Before changing it, enter hitnotify.notification_level with no value in F1 and record the current value. To undo, enter the same setting with that recorded value, then writecfg if you want to save it.
Docs reviewed 20 October 2026. Examples below are documented or statically checked; they are not labelled as tested in-game.
Facepunch's wiki documents binding syntax, stopping continual actions, clearing keys and saving. The command reference documents combatlog, perf, FPS, ping and console tools. Server rules and later updates can still affect a command.
The hit-notification setting was checked in PC client build 25903346 and server build 25902425 on 20 October 2026. Client prediction runs only at level 1; the server RPC supplies feedback at level 2. This static check does not establish in-game latency or change hit registration.
1
Save only the changes you want to keep
Open the console with F1, paste one command and press Enter. A command that starts with bind changes a key's action; a direct command runs immediately. The examples use PC keyboard names, so adapt the key to your keyboard and existing controls.
Test the result before running writecfg. This writes the current settings and keybinds to disk, including any bindings you removed. Back up keys.cfg and client.cfg in Rust's cfg folder before making many changes.
2
A cleared key is not a restored default
bind x "" removes X's action. It does not restore its previous action or stop an action that is already running. Use the stop instruction beside the example first, then remove the binding.
For an exact return, re-enter the original bind or reassign the control in Rust's Options, restore any changed setting to its previous value, then run writecfg. Record the original value before experimenting; a suggested example is not your saved default.
Every bind replaces that key's existing action. Multi-key binds can also activate the constituent key's action. Avoid overwriting movement, attack or console controls unless you know how to restore them.
3
Held actions, continual actions and cycling values
A + action runs while the bound key is held. Without +, movement, crouch and attack can continue until your ordinary control overrides them. The continual examples are not press-again toggles.
A ~ bind cycles through the listed actions on successive presses. The FOV example alternates between 70 and 90; it changes the camera field of view, not the weapon's optical magnification. Restore your previous FOV in Options when you remove it.
?
Common questions
How do I open the Rust console?
On PC, press F1. Paste or type one command, then press Enter. This guide covers the PC client, not Rust Console Edition.
How do I save or remove a Rust bind?
Run writecfg to save tested settings and bindings. To remove the example on X, run bind x "" and then writecfg. Clearing does not restore X's old action; re-enter the original bind or use Options to reassign it.
Why does auto-run keep going after I release the key?
bind x forward;sprint starts continual movement. Press your ordinary forward key to stop. Use bind x +forward;+sprint instead if you want movement only while X is held.
Are these commands tested in-game?
The entries cite Facepunch documentation or a dated static check of client code. A source check is not an in-game test. Later client updates and server rules can affect behavior.
Comments
Loading comments…