CS 1.6 Builds

A build typically comes as a complete game folder, so use 7-Zip or WinRAR to extract the archive into its own directory rather than unpacking it over an existing installation.

After that, start the game using the provided shortcut, or run hl.exe with the -game cstrike parameter. Avoid merging files from two different builds into a single folder - combining models, sprites, and configs from different versions frequently leads to crashes.

The mod's game folder is cstrike. If a cstrike_russian folder is also present, its contents take precedence.

• Maps: cstrike/maps (*.bsp), associated *.wad files go into cstrike, and map sounds into cstrike/sound.
• Weapon models: cstrike/models.
• Player models: cstrike/models/player/NAME/NAME.mdl.
• Sounds: cstrike/sound (preserve the original subfolders, such as weapons).
• Sprites, crosshairs, HUD: cstrike/sprites.

Weapon skins take the place of the default files in cstrike/models: v_*.mdl for the first-person view, p_*.mdl for the model seen in the player's hands, and w_*.mdl for the model on the ground.

Player models need to go into cstrike/models/player/NAME/NAME.mdl, where the folder name and file name are identical. Before replacing anything, make copies of the original files; otherwise, you'll need to reinstall the build to restore the default skins.

1. Check that the archive was fully extracted and no files are missing.
2. Launch the game as administrator and verify that the shortcut points to the correct hl.exe.
3. Delete or rename cstrike/config.cfg so the game generates a new one.
4. Store custom settings in userconfig.cfg or autoexec.cfg rather than modifying the main config.

If the crash began right after you added a map or model, remove that file - a corrupted or incompatible file is the most frequent cause.

A build is a separate copy of the game, so you can just delete its folder and start your original installation instead.

If you overwrote files in an existing install, restore them from the backup you made earlier, or reinstall the game. Also inspect the cstrike_russian folder - files there override those in cstrike and can keep custom content showing even after you clean the main folder.

Client-side content like weapon view models, HUD, and sounds works locally, but a server can override your custom player models and sounds with its own if consistency checking is on.

Modifying files that the server checks may result in a kick for a file mismatch. Maps and server-side plugins only function if they are installed on the server itself, not on the client.

Begin with the in-game graphics settings and reduce the resolution and detail level.

Store your personal settings in cstrike/userconfig.cfg or cstrike/autoexec.cfg so a new cstrike/config.cfg doesn't overwrite them. Heavy custom skins and high-detail sprites can also reduce performance, so test the build with the default files before adding extras.