Deathrun maps

Copy the map's .bsp file into cstrike/maps. If the map relies on custom textures, place the needed .wad files in cstrike. Sounds specific to the map go into cstrike/sound. In localized versions, the game folder might be cstrike_russian, and files there take priority.

Place the .nav file in cstrike/maps alongside the map's .bsp. The file name must match the map name exactly, for example deathrun_map.bsp and deathrun_map.nav. Bots use this file to find their way around the map.

Bring up the console with ~ and enter map mapname without the .bsp extension, or pick it from the New Game menu. Keep in mind that traps and team logic only function if the server is running a Deathrun plugin. A local listen server without the plugin will load the map's geometry but not the Deathrun mode.

Typical reasons are missing .wad textures or an incorrect folder. Check that the .bsp is in cstrike/maps and any required .wad is in cstrike. Also verify that the map file name contains no spaces or special characters.

Yes, provided the map has a .nav file placed in cstrike/maps with the same name as the .bsp. Without it, bots may remain idle or become stuck. Even with a valid .nav file, some Deathrun traps can still confuse bots.

Install AMX Mod X and a Deathrun plugin. Put the .amxx file into cstrike/addons/amxmodx/plugins and add its name to cstrike/addons/amxmodx/configs/plugins.ini. Then change the map or restart the server. The map itself only supplies the level geometry; the plugin manages teams, traps, and rules.

Yes, but the server needs to run Deathrun plugins and have the map installed. If the server lacks the map, you might download it or receive an error. Custom models or sounds on your client can be replaced by the server or lead to consistency errors.