Difference between revisions of "Deployzones"
(→Common entity keys) |
(→Entity keys) |
||
Line 17: | Line 17: | ||
=== gdf_base_deployzone === | === gdf_base_deployzone === | ||
+ | |||
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_01}} | * {{keyname|mtr_territory}} {{keyvalue|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. | : The greyscale territory image on the command map. This changes to red or green depending on which teams owns the territory. | ||
* {{keyname|start_team}} {{keyvalue|gdf}} | * {{keyname|start_team}} {{keyvalue|gdf}} | ||
: The team which owns the territory at map start. | : The team which owns the territory at map start. | ||
+ | |||
=== bridge_deployzone === | === bridge_deployzone === | ||
+ | |||
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}} | * {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}} | ||
* {{keyname|start_team}} {{keyvalue|strogg}} | * {{keyname|start_team}} {{keyvalue|strogg}} | ||
Line 34: | Line 37: | ||
=== outpost_deployzone === | === outpost_deployzone === | ||
+ | |||
+ | * {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}} | ||
+ | * {{keyname|start_team}} {{keyvalue|strogg}} | ||
+ | * {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}} | ||
+ | : First vehicle granted to the GDF when they own the territory. | ||
+ | * {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}} | ||
+ | : Second vehicle granted to the GDF when they own the territory. | ||
+ | * {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}} | ||
+ | : Third vehicle granted to the GDF when they own the territory. | ||
+ | * {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}} | ||
+ | : Fourth vehicle granted to the GDF when they own the territory. | ||
+ | * {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}} | ||
+ | : Fifth vehicle granted to the GDF when they own the territory. | ||
+ | * {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}} | ||
+ | : First vehicle granted to the Strogg when they own the territory. | ||
+ | * {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}} | ||
+ | : Second vehicle granted to the Strogg when they own the territory. | ||
+ | * {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}} | ||
+ | : Third vehicle granted to the Strogg when they own the territory. | ||
+ | * {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}} | ||
+ | : Fourth vehicle granted to the Strogg when they own the territory. We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the bridge territory]] | ||
+ | |||
=== shield_deployzone === | === shield_deployzone === | ||
=== strogg_base_deployzone === | === strogg_base_deployzone === |
Revision as of 14:24, 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
- 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
- mtr_territory commandmaps/etqwmap_territory_03
- start_team strogg
- target_gdf1 outpost_gdf_badger
- First vehicle granted to the GDF when they own the territory.
- target_gdf2 outpost_gdf_trojan
- Second vehicle granted to the GDF when they own the territory.
- target_gdf3 outpost_gdf_titan
- Third vehicle granted to the GDF when they own the territory.
- target_gdf4 outpost_gdf_husky
- Fourth vehicle granted to the GDF when they own the territory.
- target_gdf5 outpost_gdf_husky
- Fifth vehicle granted to the GDF when they own the territory.
- target_strogg1 outpost_strogg_hog
- First vehicle granted to the Strogg when they own the territory.
- target_strogg2 outpost_strogg_desecrator
- Second vehicle granted to the Strogg when they own the territory.
- target_strogg3 outpost_icarus_1
- Third vehicle granted to the Strogg when they own the territory.
- target_strogg4 outpost_icarus_2
- Fourth vehicle granted to the Strogg when they own the territory. We have already added the vehicles associated with the bridge territory
shield_deployzone
strogg_base_deployzone
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.