Hostage

From Source Entities
Jump to navigation Jump to search

For CTs to win a Css.pngCsgo-small.pngHostage game, they must:

  • Rescue at least half of the hostages, and have no remaining hostages held captive (either through killing or rescuing) (In CS:GO, this rule is changed to saving any hostage), or
  • Kill all terrorists (logically saving all hostages).

For Terrorists to win, they must:

  • Prevent CTs from rescuing half (or any in CS:GO) of the hostages before the timer runs out, or
  • Kill all CTs.

Spawns[edit | edit source]

Spawn players with info_player_terrorist and info_player_counterterrorist. The exact location players spawn in can sometimes impact gameplay. Players sometimes take whatever route is closest to them, due to the amount of time spent walking to a meeting point being important. In CSGO, spawnpoints can be given a priority to mark which are more or less desirable. Since servers can go up to 32 players, each team should have 16 spawns, otherwise players will spawn inside other players.

To create the zones for buying weapons and equipment, create a brush around the spawn points for each team, select the brush, and press Ctrl+T to tie it to an entity. Change the entity class to func_buyzone.

Hostage Spawns and Rescue Zones[edit | edit source]

Place hostages with hostage_entity (CS:GO has an entity called info_hostage_spawn as well. It appears to be identical to hostage_entity but this is not confirmed.) Logically, hostages should be placed close to terrorist spawns so they can defend easily. Define the hostage rescue zone with func_hostage_rescue.

Miscellaneous[edit | edit source]

Though your Hostage Rescue map will work correctly with any prefix (or with none at all), using the cs_ prefix allows the game to correctly identify the type of map as a bomb scenario during loading screens.

The convar game_type should be 0 and game_mode should be 0 for casual or 1 for competitive.