Deployzones

Deployzone entities (also known internally as territory brushes) are used to determine where territories exist within a map. They are brush based entities using the textures/common/trigger texture. A player can only deploy inside a deployzone volume that is active for their team (and only on green areas of the deploy mask.) Team base deployzones do not change over the course of match, whereas in most other cases deployzones are granted to the attacking team when an objective is completed.

In the example map there are five deployzone entities;

• gdf_base_deployzone
• bridge_deployzone
• outpost_deployzone
• shield_deployzone
• strogg_base_deployzone

Vehicles and deployzones

The deployzones are also used to spawn vehicles for the attacking team when they gain territory. When the attacking team loses territory, any of their vehicles associated with the deployzone are destroyed. Vehicles are associated with deployzones by targeting deployable_spawn_<vehiclename> entities. In the example map you will see target paths, originating from the deployzone, leading to the vehicles. Note that they are targeted using target_gdf1,target_strogg1 and so on. This lets the game know which vehicles to spawn/destroy when territory changes hands.

Entity keys

gdf_base_deployzone

• mtr_territory commandmaps/etqwmap_territory_01

The greyscale territory image on the command map. This changes to red or green depending on which teams owns the territory.

• start_team gdf

The team which owns the territory at map start.

bridge_deployzone

• mtr_territory commandmaps/etqwmap_territory_02
• start_team strogg
• target_gdf1 bridge_gdf_badger

First vehicle granted to the GDF when they own the territory.

• target_gdf2 bridge_gdf_husky

Second vehicle granted to the GDF when they own the territory.

• target_strogg1 bridge_strogg_icarus_1

First vehicle granted to the Strogg when they own the territory.

• target_strogg2 bridge_strogg_icarus_2

Second vehicle granted to the Strogg when they own the territory. We have already added the vehicles associated with the bridge territory

outpost_deployzone

• mcp_stay_deployed 1

MCP is deployed in this deployzone.

• mtr_territory commandmaps/etqwmap_territory_03
• start_team strogg
• target_gdf1 outpost_gdf_badger
• target_gdf2 outpost_gdf_trojan
• target_gdf3 outpost_gdf_titan
• target_gdf4 outpost_gdf_husky
• target_gdf5 outpost_gdf_husky
• target_strogg1 outpost_strogg_hog
• target_strogg2 outpost_strogg_desecrator
• target_strogg3 outpost_icarus_1
• target_strogg4 outpost_icarus_2

We have already added the vehicles associated with the outpost territory

shield_deployzone

• mtr_territory commandmaps/etqwmap_territory_04
• start_team strogg
• target_strogg1 outpost_icarus_1
• target_strogg2 outpost_icarus_2
• target_strogg3 outpost_hog

We have already added the vehicles associated with the shield territory

strogg_base_deployzone

• mtr_territory commandmaps/etqwmap_territory_05
• start_team strogg

Common entity keys

These key pairs are common across all deployzones;

• territory_start 0 0

FIXME.

• territory_end 1 1

FIXME.

• target_playzone territory_size_thing

The playzone entity used to determine the bounds of the map territories.

Worldspawn keys

The deployzone entities require the following entity keys;

• "script_gdf_base_territory" gdf_base_deployzone
• "script_bridge_territory" bridge_deployzone
• "script_outpost_territory" outpost_deployzone
• "script_shield_territory" shield_deployzone
• "script_strogg_base_territory" strogg_base_deployzone