Difference between revisions of "Deployzones"
| Line 26: | Line 26: | ||
: The team which owns the territory at map start. | : The team which owns the territory at map start. | ||
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}} | * {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}} | ||
| − | : First vehicle granted to the GDF when they own the territory. | + | : First vehicle granted to the GDF when they own the territory. |
| + | * {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}} | ||
| + | : Second vehicle granted to the Strogg when they own the territory. | ||
| + | * {{keyname|target_strogg1}} {{keyvalue|bridge_strogg_icarus_1}} | ||
| + | : First vehicle granted to the Strogg when they own the territory. | ||
| + | * {{keyname|target_strogg2}} {{keyvalue|bridge_strogg_icarus_2}} | ||
| + | : Second vehicle granted to the Strogg when they own the territory. We added the team's vehicles for the bridge objective [[Adding_Objective_spawns_and_vehicles#Vehicles_2|here]] | ||
=== outpost_deployzone === | === outpost_deployzone === | ||
=== shield_deployzone === | === shield_deployzone === | ||
Revision as of 12:21, 22 November 2007
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
Contents
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.
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
- The team which owns the territory at map start.
- 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 Strogg 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 added the team's vehicles for the bridge objective here
outpost_deployzone
shield_deployzone
strogg_base_deployzone
Common entity keys
These key pairs are common across all deployzones;
- territory_start 0 0
- FIXME.
- territory_start 1 1
- FIXME.
- target_playzone territory_size_thing
- The playzone entity used to determine the bounds of the map territories.
