How to install a CS 1.6 config without losing your settings
Install a config as a controlled change to a working game. You need the active game folder, a plain-text editor and a backup of the files you intend to modify. The first test should prove that your file executes; automatic loading comes later.
1. Locate the correct cstrike folder
Keep the backup outside the working game folder and record its date. If several copies exist, note the full folder path alongside your test results.
- Close the game so your edits are not competing with settings written during exit.
- For Steam, use the game's Library entry to open its installed files. For a community copy, inspect the shortcut's target location.
- Find the cstrike folder belonging to that installation and copy any existing files you plan to change into a separate backup folder.
2. Create a separate test file
Open the downloaded CFG in a text editor and review its commands. For the first test, create atlas-practice.cfg containing only the marker below. Show filename extensions and confirm that the file is not actually named atlas-practice.cfg.txt.
- Save plain text, not a formatted document.
- Keep the simple filename identical in the folder and the console command.
- Do not replace an existing config.cfg for this test.
echo ATLAS_CONFIG_LOADED3. Execute it from the game console
Start this installation and open its console. Run the command below, then look for ATLAS_CONFIG_LOADED in the output. The marker confirms that this file executed; it does not validate other commands you later add.
- If the file cannot be executed, recheck the folder, extension and spelling.
- After the marker works, add one reviewed setting and execute the file again.
- Test the result on a local map before connecting to a public server.
exec atlas-practice.cfg4. Restart and keep a rollback path
Restart the game and check whether the intended setting remains. If manual execution works but restart does not, investigate the startup-loading path for your installation instead of repeatedly replacing files.
To undo your experiment, remove its automatic execution entry if you added one, close the game and restore only the files you changed from your backup. A separately named CFG also makes later comparison and sharing easier.
Sources and further reading
Choose your next step
Make the first execution visible
Save the file with a real .cfg extension in the intended game's cstrike directory. Use a recognisable filename and execute it explicitly with exec custom.cfg, replacing custom with your own name. Test a harmless setting before adding automatic loading, because startup behaviour differs between clients and existing configs can override later values.
Questions before you play
Why does exec fail even though the file is visible?
Check the active game folder and full filename. Windows can hide an extra .txt extension, and editing a second installation will not change the client you launched.