Creating a Hostage Rescue Map
It is covered here for historical and technical reference.
This page covers only the special requirements for Hostage Rescue Scenarios in a Classic Competitive map in Counter-Strike: Source and Counter-Strike: Global Offensive.
For the other map requirements, see Creating a Classic Counter-Strike Map.
Map Requirements
Hostage Rescue maps require hostages for the Counter-Terrorists to rescue, and a hostage rescue zone.
Hostages
Create entities and change their classname to hostage_entity ( or info_hostage_spawn). This is where hostages will spawn.
If such an entity exists, the game will care about the rest, such as appropriate round endings and a time bonus when the first hostage is reached by a CT.
The official maps have 4 of these entities. Every one of these entities spawns a hostage NPC.
The official maps have at least 2 of these entities and usually more. The game will try to pick 2 of the available spawn points to spawn hostages, respecting exclusion groups.
Rescue Zones
Create a brush and texture it with the tools/toolstrigger
texture. Select the brush, press Ctrl+T to tie it to an entity and change the entity class to func_hostage_rescue.
Create at least one in the map to make rescuing hostages possible.
Competitive Aspects
- Hostages are located closer to the Terrorist's spawn area so that they can get into a defensive position before Counter-Terrorists arrive.
- Usually the rescue zone is placed near the Counter-Terrorist spawn.
- Use the
NO HOSTAGES
NAV attribute which can be toggled with nav_no_hostages to force hostages to not use specific nav areas. - Hostages sharing any
Hostage Spawn Exclusion Group
in its properties will not spawn together. - The
Hostage Spawn Random Factor
property is the number of times a spawn point is put into the pool for the hostages to spawn at. Raising this number makes it more likely for a spawn point to be picked.