Configs / CFGs

Get the .cfg file and put it into your CS 1.6 game folder: cstrike (or cstrike_russian for localized versions). Then open the game console and run exec filename.cfg (replace filename with the config name). To load it automatically, add that same exec line to autoexec.cfg.

All config files go in the cstrike folder of your Counter-Strike 1.6 installation. In localized Russian versions, the priority folder is cstrike_russian. Put the .cfg file there, then load it with exec in the console.

Place the .cfg file in cstrike or cstrike_russian. In the console, type exec filename.cfg (using the actual file name). You can also bind a key to load it: bind "F1" "exec filename.cfg". After loading, check your sensitivity and other settings, as pro configs may need adjusting for your hardware.

Check that the file has a .cfg extension, not .txt, and is in cstrike or cstrike_russian. Make sure you type exec filename.cfg correctly in the console. If you edited config.cfg directly, the game may overwrite it on exit; use autoexec.cfg for permanent settings instead.

Close the game and delete or rename config.cfg in cstrike (and cstrike_russian if present). Also remove or rename autoexec.cfg and userconfig.cfg if you added custom settings there. When you launch the game again, it will create a fresh config.cfg with default values.

Client-side settings like sensitivity, cl_crosshair, and key binds work on most servers. Server-side settings (sv_*, mp_*) and some rate commands may be forced by the server and override your config. Config files do not cause consistency issues, as they only change settings and not game files.

Put your commands in autoexec.cfg or userconfig.cfg inside cstrike (or cstrike_russian). These files are executed automatically when the game starts. Do not put permanent settings only in config.cfg, because the game overwrites it when you exit.