Skins. Codes. Clear answers.

Guides/Game settings

Game settings

Rust keybinds not saving: review the bind, then writecfg

Facepunch documents writecfg after F1 keybind changes and keys.cfg inside the Rust installation. Back up your current bindings, change one key and verify it after a restart.

3 min read
Published Revised

THE QUICK ANSWER

Keep the original binding, run writecfg after a deliberate change and test persistence. A semicolon or missing plus sign can change what a copied bind does.

01

Preserve the controls you already use

Before replacing a key, note its existing function and keep a copy of your configuration. Facepunch identifies keys.cfg inside the Rust installation; Steam Library → Rust → Manage → Browse local files opens the relevant installation.

Locate that file by name rather than assuming every installation uses your friend’s drive or library path. Do not delete the complete configuration folder to investigate one binding.

STRIKEPOT / EXPLAINED

Make one binding change reviewable

  1. Before

    Keep the original action and a configuration copy.

  2. Change

    Inspect the complete new binding.

  3. Save

    Run the documented writecfg command.

  4. Reopen

    Check whether the intended action persisted.

Original persistence-check sequence; no configuration was changed.

Original explanation · not an account screenshot

02

Read the whole binding before applying it

The wiki’s general form is bind key action. A semicolon combines actions, while a plus-prefixed action is held only while the assigned button is pressed. A similar-looking bind can therefore continue movement rather than act only while held.

Facepunch also warns that a modifier combination is not independent of its component key: the original key action can still fire. Check those interactions before choosing a shared movement or interaction key.

Syntax changes behaviour
SemicolonMore than one action can run.
Plus prefixThe documented held-action form.
Modifier combinationDoes not create an independent replacement for the base-key action.

03

Use writecfg for the change you intend to keep

After setting the intended F1 binding, Facepunch instructs users to run writecfg so changes are written to configuration files. Its command reference describes the command as writing settings and keybinds.

Test the key in a quiet context, then close and reopen Rust normally and check it again. Record whether the action worked before restart, after restart, or neither; those are different failures.

STRIKEPOT / EXPLAINED

Small syntax differences matter

  1. Single action

    One key action under the general bind form.

  2. Semicolon list

    Several actions are combined.

  3. Held form

    A plus-prefixed action follows the held-key rule.

  4. Modifier form

    The base key may still activate its own action.

A conceptual syntax comparison, not a ready-made automation script.

Original explanation · not an account screenshot

04

Restore one binding rather than reset everything

The wiki documents clearing a single binding with an empty quoted action, such as bind x "". That removes the custom binding; it does not reconstruct whatever action you had there before.

Restore the original action from your own note when you want the old behaviour back, then save it deliberately. For an unknown command use the documented find lookup. Keep administrator-only examples separate from ordinary player controls.

BEFORE YOU CONTINUE

Quick checklist

  • Back up the current binding and configuration.
  • Read every action and modifier.
  • Run writecfg for the intended change.
  • Compare before and after a normal restart.

Official sources

English primary documentation reviewed on 26 October 2026. Historical release notes are dated; current-client observations are not implied.

Documentation review only. No personal game client, account, server, download or setting was tested. The comparison and evidence suggestions are original editorial guidance.

KEEP READING

A useful next read.

All guides
New guide

Game troubleshooting · 4 min read

Read your Rust combat log

Open Rust’s F1 console and run combatlog to review recent damage dealt and received. Check who the row describes before reading its weapon, hit location, distance and health change.

Read guide

Game troubleshooting · 3 min read

Rust: find crash evidence

Find Rust’s Windows client crash folder, sort by Date modified and keep the .dmp that matches the crash time for a private Facepunch support report.

Read guide

Support · 3 min read

A better support ticket

Include the affected order or trade, the exact status and a dated timeline. Use the template to explain what happened and ask for the next step.

Read guide