Blogger Builds

1. Download and unpack the build archive.
2. Make a backup copy of your cstrike folder.
3. Copy the folders and files from the archive into cstrike, confirming replacement of existing files.
4. Launch the game.

If your game uses the localized folder cstrike_russian, copy the files there instead - files in it have priority over cstrike.

Keep the folder structure from the archive. Player models go to cstrike/models/player/NAME/NAME.mdl, where the folder and file names must match. Weapon models go to cstrike/models, sprites and HUD to cstrike/sprites, sounds to cstrike/sound, and the settings file to cstrike/config.cfg.

There is nothing to enable in the menu: custom models and skins replace the standard files, so they appear automatically after you copy them and restart the game. If a model does not show up, check that the files are in the correct folder and that the folder and file names of player models match.

• Check that all files were copied into the correct folders inside cstrike.
• Restore your backup of cstrike and install the build again, copying files one part at a time.
• Delete config.cfg so the game creates a fresh one if the settings cause problems.
• Make sure the build matches your game version.

Restore the backup of the cstrike folder that you made before installing the build. If you have no backup, delete the replaced files and restore the original ones, or reinstall the game. Deleting config.cfg also resets your settings to default.

Client-side visuals such as skins, sprites, HUD and menu work locally and are seen only by you. On other servers, custom models and sounds may be replaced by the server's own files or cause a consistency kick. Server settings can also override the values from the build's config.cfg.

Keep a separate copy of the cstrike folder for each build and swap them when needed, or install each build into its own copy of the game. Always back up the current cstrike folder before replacing files with a new build.