CS 1.6 config not saving: find where the setting changes
“My config does not save” can describe three different failures: the file never executes, a value changes later, or a saved value is not loaded next time. Follow one visible setting through the session to find the point where your result diverges.
1. Prove that the intended file executes
Use the installation associated with your actual shortcut or Steam Library entry. Put the marker below in atlas-practice.cfg inside its cstrike folder, then start the game and run exec atlas-practice.cfg in the console.
If ATLAS_CONFIG_LOADED never appears, inspect the filename and folder. Show extensions to catch atlas-practice.cfg.txt. Solving this loading problem comes before investigating whether a setting is saved.
echo ATLAS_CONFIG_LOADED2. Identify when a working value changes
Add one setting you understand after the marker. Note its initial value, execute the file and check the result immediately. Repeat the check after opening the settings menu, loading a local map and restarting the game.
| Observation | Investigate next |
|---|---|
| Marker missing | Wrong folder, name or file extension |
| Marker appears; command is unknown | Command belongs to another game, bot or plugin |
| Value changes during the session | A later menu action, config or component |
| Value changes only after restart | The startup-loading path and saved files |
3. Inspect the competing source
Search your own custom CFG files and launch options for the same setting or an exec command that loads another file. Temporarily remove one conflicting custom entry, keep a backup and retest. Do not assume every client loads user-created files in the same order.
If your text editor cannot save, close the game and check that the file is writable by your account. Do not make the whole game folder read-only as a general fix; that can prevent legitimate settings changes.
4. Confirm a clean restart
Once the manual test succeeds, verify the automatic-loading method documented for your installation. Restart, check the value before joining a server, then repeat after a local map.
Keep the working file and a short note of how it loads. If the problem returns only after a specific add-on or server session, you now have a repeatable comparison to investigate instead of replacing every config.
Sources and further reading
Choose your next step
Find the moment a value changes
Set one harmless option, leave the game normally and restart it. Compare the value immediately after launch and again after joining a server. That sequence helps distinguish an unwritable file, an automatically executed config and a server-related change. Also confirm that your shortcut launches the installation whose files you have been editing.
Questions before you play
Should I make config.cfg read-only immediately?
Not as the first diagnostic step. Read-only files can block intended changes too. Identify what overwrites the value before deciding how that specific setting should be stored.