config.cfg Explained: Editing Your CS 1.6 Config

Nearly every "my settings reset every time I launch" complaint comes down to one fact people do not know: the game rewrites config.cfg when it exits. Edit it while CS is running and your changes are gone the moment you quit. Once you understand how the config files load, editing CS 1.6 becomes straightforward and permanent. This guide covers where the files are, the order they run in, and the right place to put your settings.

1. Where config.cfg lives

The file is inside your Counter-Strike install, in the game folder:

...\Steam\steamapps\common\Half-Life\cstrike\config.cfg

On Linux the path uses forward slashes but the layout is identical: Half-Life/cstrike/config.cfg. If you play a mod, that mod has its own folder (for example czero) with its own config.cfg.

2. What is inside it

config.cfg is a plain list of console commands the engine runs at startup. It holds your key binds, your rates, your mouse sensitivity and your video-related cvars — essentially your whole setup as commands:

bind "w" "+forward"
bind "mouse1" "+attack"
sensitivity "2.2"
rate "100000"
cl_updaterate "101"
cl_cmdrate "101"
ex_interp "0.01"
fps_max "300"

You can read it to see exactly what the game thinks your settings are — it is the source of truth the menu writes to.

3. The golden rule: edit with the game closed

The engine loads config.cfg at startup and writes it back on exit, overwriting your file with its in-memory state. So:

1. Fully quit Counter-Strike.
2. Open config.cfg in a plain text editor (Notepad, not a word processor).
3. Make your changes and save.
4. Launch the game.

Edit it while the game is open and you are wasting your time — this single mistake is behind the vast majority of "my config keeps resetting" reports.

4. Use autoexec.cfg for settings that must never reset

Because the game rewrites config.cfg, the durable place for your personal cvars is a file the game runs but does not overwrite. Create cstrike/autoexec.cfg:

rate 100000
cl_updaterate 101
cl_cmdrate 101
ex_interp 0.01
fps_max 300
net_graph 3
developer 0

autoexec.cfg is executed automatically at startup and, unlike config.cfg, the engine does not rewrite it on exit — so your values are reapplied every launch no matter what the menu did. This is the standard way to lock in rates and FPS settings.

5. userconfig.cfg and per-map configs

Some setups also run userconfig.cfg at startup; it works like autoexec.cfg and either is fine — pick one and keep everything in it rather than splitting your settings. You can also run a config on demand from the console:

exec myconfig.cfg

Any .cfg file in cstrike/ can be executed by name, which is handy for switching between, say, a scrim config and a public config.

6. Make config.cfg read-only (optional, blunt)

If you want the menu to stop clobbering a hand-tuned config.cfg, you can mark it read-only in the file properties. Be warned: this also stops the game saving any future menu changes, so binds you set through Options will not persist. The autoexec approach is cleaner because it layers on top without fighting the game.

Common errors

• Settings reset every launch — you edited config.cfg with the game open. Close the game first, or move the settings to autoexec.cfg.
• autoexec.cfg ignored — wrong folder (it must be in cstrike/, not the Half-Life root), or saved as autoexec.cfg.txt with a hidden extension. Turn on file-extension display and check.
• Edited the wrong config.cfg — you have several game folders (cstrike, czero). Edit the one matching the game you launch.
• Binds vanish but cvars stay — you set binds in-game after the config ran; save them by binding in autoexec.cfg or letting the game write config.cfg on a clean exit.

Verification

Put a distinctive line in autoexec.cfg, for example net_graph 3, launch the game, and confirm it took effect. Quit, relaunch, and confirm it is still there — that round-trip proves your settings survive the config rewrite. From there you can safely store your rates and FPS settings knowing they will persist.