Mod Wiki - User contributions [en-gb]

Necessary map declarations

2007-12-11T14:30:05Z

DavidE:

{{first etqwmap toc}}
== Materials ==

Here is a list of materials for assets created later on. Simply copy the text from the boxs below and save to {{filename|materials/yourmapname.mtr}} Don't forget to find/replace 'etqwmap' with yourmapname.

This is needed for some codey reason:

#include <materials/commandmaps.include>

These are the megatexture materials. They are only one line of text as they use a template elsewhere:

material megatextures/etqwmap { useTemplate megatextures/default_ambient_spec< "etqwmap" > }
material megatextures/etqwmap_noshadows { useTemplate megatextures/default_ambient_spec_noshadows< "etqwmap" > }

These are the [[Creating a command map|command map materials]]. One for the regular command map, one for out of bounds:

material commandmaps/etqwmap
{
templates/game/maps/cmMap( "commandmaps/etqwmap.tga" )
}

material commandmaps/etqwmap_oob
{
templates/game/maps/cmMap( "commandmaps/etqwmap_oob.tga" )
}

These are the territory materials (the greyscale territory lines which the game makes red/green):

material commandmaps/etqwmap_territory_01 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter01.tga ) )
}

material commandmaps/etqwmap_territory_02 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter02.tga ) )
}

material commandmaps/etqwmap_territory_03 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter03.tga ) )
}

material commandmaps/etqwmap_territory_04 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter04.tga ) )
}

material commandmaps/etqwmap_territory_05 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter05.tga ) )
}

The level shot (loading screen image) material:

material levelshots/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/etqwmap"
}
}

The material for the small thumbnail of your map:

material levelshots/thumbs/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/thumbs/etqwmap"
}
}

== Definitions ==

Here are the map definitions needed for a functioning map. Save these to def/yourmapname.def

#include "def/pathfinder.include"

heightMap heightmaps/etqwmap {
heightMap "heightmaps/etqwmap.tga"
}

deployMask masks/etqwmap/mcp {
mask "masks/etqwmap/mcp.tga"
}

deployMask masks/etqwmap/default {
mask "masks/etqwmap/default.tga"
}

deployMask masks/etqwmap/mcp_route {
mask "masks/etqwmap/mcp_route.tga"
}

deployMask masks/etqwmap/playzone {
mask "masks/etqwmap/playzone.tga"
}

stringMap pathfinder_etqwmap {
_pathfinder_default( "etqwmap", 20 )
"playzone_0" "etqwmap_playzone_path_and_heightmap"
"resolution_x_playzone_0" "1280"
"resolution_y_playzone_0" "1280"
"mg_resolution_x_playzone_0" "1280"
"mg_resolution_y_playzone_0" "1280"
}

[[Category:Basic Level Design]]

Necessary map declarations

2007-12-11T11:54:01Z

DavidE: /* Materials */

{{first etqwmap toc}}
== Materials ==

Here is a list of materials for assets created later on. Simply copy the text from the boxs below and save to {{filename|materials/yourmapname.mtr}} Don't forget to find/replace 'etqwmap' with yourmapname.

This is needed for some codey reason.

#include <materials/commandmaps.include>

These are the megatexture materials. They look pretty as as they use a template.

material megatextures/etqwmap { useTemplate megatextures/default_ambient_spec< "etqwmap" > }
material megatextures/etqwmap_noshadows { useTemplate megatextures/default_ambient_spec_noshadows< "etqwmap" > }

These are the command map materials. One for the regular command map, one for out of bounds.

material commandmaps/etqwmap
{
templates/game/maps/cmMap( "commandmaps/etqwmap.tga" )
}

material commandmaps/etqwmap_oob
{
templates/game/maps/cmMap( "commandmaps/etqwmap_oob.tga" )
}

These are the territory materials.

material commandmaps/etqwmap_territory_01 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter01.tga ) )
}

material commandmaps/etqwmap_territory_02 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter02.tga ) )
}

material commandmaps/etqwmap_territory_03 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter03.tga ) )
}

material commandmaps/etqwmap_territory_04 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter04.tga ) )
}

material commandmaps/etqwmap_territory_05 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter05.tga ) )
}

The level shot (loading screen image) material.

material levelshots/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/etqwmap"
}
}

The material for the small thumbnail of your map.

material levelshots/thumbs/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/thumbs/etqwmap"
}
}

== Definitions ==

Here are the map definitions needed for a functioning map. Save these to def/yourmapname.def

#include "def/pathfinder.include"

heightMap heightmaps/etqwmap {
heightMap "heightmaps/etqwmap.tga"
}

deployMask masks/etqwmap/mcp {
mask "masks/etqwmap/mcp.tga"
}

deployMask masks/etqwmap/default {
mask "masks/etqwmap/default.tga"
}

deployMask masks/etqwmap/mcp_route {
mask "masks/etqwmap/mcp_route.tga"
}

deployMask masks/etqwmap/playzone {
mask "masks/etqwmap/playzone.tga"
}

stringMap pathfinder_etqwmap {
_pathfinder_default( "etqwmap", 20 )
"playzone_0" "etqwmap_playzone_path_and_heightmap"
"resolution_x_playzone_0" "1280"
"resolution_y_playzone_0" "1280"
"mg_resolution_x_playzone_0" "1280"
"mg_resolution_y_playzone_0" "1280"
}

[[Category:Basic Level Design]]

Creating a simple terrain

2007-11-23T14:24:57Z

DavidE:

{{First etqwmap toc}}
For now a flat terrain is fine to drive and run around on. The example map already has a flat terrain set up. The terrain mesh was added to a map via the [[Terrain Editor]]. Pick the Terrain Editor inspector and right click on the empty left hand dialog. Then choose New > Tree... Then choose the following terrain model "models/terrain/sdk/etqwmap.lwo". Some guidelines on making your own terrain model can be found on [[Terrain|here]].

[[Category:Basic Level Design]]

Creating a simple terrain

2007-11-23T14:24:07Z

DavidE:

Deployzones

2007-11-23T14:11:05Z

DavidE:

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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 ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}}
* {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}}
* {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}}
* {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the outpost territory]]

=== shield_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_04}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_icarus_2}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_hog}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_4|vehicles associated with the shield territory]]

=== strogg_base_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_05}}
* {{keyname|start_team}} {{keyvalue|strogg}}

=== Common entity keys ===

These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|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;

* {{keyname|"script_gdf_base_territory"}} {{keyvalue|gdf_base_deployzone}}
* {{keyname|"script_bridge_territory"}} {{keyvalue|bridge_deployzone}}
* {{keyname|"script_outpost_territory"}} {{keyvalue|outpost_deployzone}}
* {{keyname|"script_shield_territory"}} {{keyvalue|shield_deployzone}}
* {{keyname|"script_strogg_base_territory"}} {{keyvalue|strogg_base_deployzone}}

Info Objectives

2007-11-23T14:08:49Z

DavidE:

{{first etqwmap toc}}
Info_objective entities provide objective information to the player such as;

* The objective description the player will see in the limbo menu and in game.
* The icon to display in the world
* The icon and objective number on the command map

Their lateral position in the world determine the objective position on the command map. An info_objective has been placed for each of the four objectives in the example map. Their vertical position is not important, but for neatness just place them somewhere easily selectable.

== Entity keys ==

=== Bridge info_objective ===

* {{keyname|objective_index}} {{keyvalue|0}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{keyname|mtr_icon}} {{keyvalue|hud/icons/missionsystem/obj_build}}
: Icon used to represent the current objective.
* {{keyname|mtr_icon_number}} {{keyvalue|hud/objectives/marker_01}}
: Objective number to show on the command map.
* {{keyname|text_objective_gdf}} {{keyvalue|maps/valley/obj01_gdf}}
: Objective text for GDF.
* {{keyname|text_objective_strogg}} {{keyvalue|maps/valley/obj01_strogg}}
: Objective text for Strogg.
* {{keyname|text_short_objective_gdf}} {{keyvalue|maps/valley/obj01_gdf_short}}
: Shortened objective text for GDF.
* {{keyname|text_short_objective_strogg}} {{keyvalue|maps/valley/obj01_strogg_short}}
: Shortened objective text for Strogg.
* {{keyname|mtr_objective_gdf}} {{keyvalue|hud/icons/missionsystem/obj_build}}
: Icon used to represent the objective to the GDF.
* {{keyname|mtr_objective_gdf_desat}} {{keyvalue|hud/icons/missionsystem/obj_build_desat}}
: Icon used to represent an inactive objective to the GDF.
* {{keyname|mtr_objective_world_icon_gdf}} {{keyvalue|hud/icons/missionsystem/obj_build}}
: World icon used to represent the objective to the GDF.

=== MCP info_objective ===

* {{keyname|objective_index}} {{keyvalue|1}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{keyname|mtr_icon}} {{keyvalue|hud/icons/missionsystem/obj_mcp}}
: Icon used to represent the current objective.
* {{keyname|mtr_icon_number}} {{keyvalue|hud/objectives/marker_02}}
: Objective number to show on the command map.
* {{keyname|text_objective_gdf}} {{keyvalue|maps/valley/obj02_gdf}}
: Objective text for GDF.
* {{keyname|text_objective_strogg}} {{keyvalue|maps/valley/obj02_strogg}}
: Objective text for Strogg.
* {{keyname|text_short_objective_gdf}} {{keyvalue|maps/valley/obj02_gdf_short}}
: Shortened objective text for GDF.
* {{keyname|text_short_objective_strogg}} {{keyvalue|maps/valley/obj02_strogg_short}}
: Shortened objective text for Strogg.
* {{keyname|mtr_objective_gdf}} {{keyvalue|hud/icons/missionsystem/obj_goal}}
: Icon used to represent the objective to the GDF.
* {{keyname|mtr_objective_gdf_desat}} {{keyvalue|hud/icons/missionsystem/obj_goal_desat}}
: Icon used to represent an inactive objective to the GDF.
* {{keyname|mtr_objective_world_icon_gdf}} {{keyvalue|hud/icons/missionsystem/obj_goal}}
: World icon used to represent the objective to the GDF.

=== Shield generator info_objective ===

* {{keyname|objective_index}} {{keyvalue|2}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{keyname|mtr_icon}} {{keyvalue|hud/icons/missionsystem/obj_hack}}
: Icon used to represent the current objective.
* {{keyname|mtr_icon_number}} {{keyvalue|hud/objectives/marker_03}}
: Objective number to show on the command map.
* {{keyname|text_objective_gdf}} {{keyvalue|maps/valley/obj03_gdf}}
: Objective text for GDF.
* {{keyname|text_objective_strogg}} {{keyvalue|maps/valley/obj03_strogg}}
: Objective text for Strogg.
* {{keyname|text_short_objective_gdf}} {{keyvalue|maps/valley/obj03_gdf_short}}
: Shortened objective text for GDF.
* {{keyname|text_short_objective_strogg}} {{keyvalue|maps/valley/obj03_strogg_short}}
: Shortened objective text for Strogg.
* {{keyname|mtr_objective_gdf}} {{keyvalue|hud/icons/missionsystem/obj_hack}}
: Icon used to represent the objective to the GDF.
* {{keyname|mtr_objective_gdf_desat}} {{keyvalue|hud/icons/missionsystem/obj_hack_desat}}
: Icon used to represent an inactive objective to the GDF.
* {{keyname|mtr_objective_world_icon_gdf}} {{keyvalue|hud/icons/missionsystem/obj_hack}}
: World icon used to represent the objective to the GDF.

=== Destruction info_objective ===

* {{keyname|objective_index}} {{keyvalue|3}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{keyname|mtr_icon}} {{keyvalue|hud/icons/missionsystem/obj_destroy}}
: Icon used to represent the current objective.
* {{keyname|mtr_icon_number}} {{keyvalue|hud/objectives/marker_043}}
: Objective number to show on the command map.
* {{keyname|text_objective_gdf}} {{keyvalue|maps/valley/obj04_gdf}}
: Objective text for GDF.
* {{keyname|text_objective_strogg}} {{keyvalue|maps/valley/obj04_strogg}}
: Objective text for Strogg.
* {{keyname|text_short_objective_gdf}} {{keyvalue|maps/valley/obj04_gdf_short}}
: Shortened objective text for GDF.
* {{keyname|text_short_objective_strogg}} {{keyvalue|maps/valley/obj04_strogg_short}}
: Shortened objective text for Strogg.
* {{keyname|mtr_objective_gdf}} {{keyvalue|hud/icons/missionsystem/obj_destroy}}
: Icon used to represent the objective to the GDF.
* {{keyname|mtr_objective_gdf_desat}} {{keyvalue|hud/icons/missionsystem/obj_destroy_desat}}
: Icon used to represent an inactive objective to the GDF.
* {{keyname|mtr_objective_world_icon_gdf}} {{keyvalue|hud/icons/missionsystem/obj_destroy}}
: World icon used to represent the objective to the GDF.

== Common entity keys ==
These are common entity key pairs across all info_objectives in all ETQW maps.
* {{keyname|icon_size_cm}} {{keyvalue|24}}
: Size of objective type icon on command map
* {{keyname|icon_size_number_cm}} {{keyvalue|24}}
: Size of objective number icon on command map
* {{keyname|icon_offset_cm}} {{keyvalue|8 8 0}}
: Offset of objective type icon on command map
And since strogg defend this map, they will get defend icons for each info_objective;
* {{keyname|mtr_objective_strogg}} {{keyvalue|hud/icons/missionsystem/obj_defend}}
: Icon used to represent the current objective to the Strogg
* {{keyname|mtr_objective_strogg_desat}} {{keyvalue|hud/icons/missionsystem/obj_defend_desat}}
: Icon used to represent an inactive objective to the Strogg
* {{keyname|mtr_objective_world_icon_strogg}} {{keyvalue|hud/icons/missionsystem/obj_defend}}
: World icon used to represent the current objective to the Strogg.

== Worldspawn keys ==

The info_objective entities require the following worldspawn keys;

* {{keyname|"script_obj1_marker"}} {{keyvalue|info_objective_1}}.
* {{keyname|"script_obj2_marker"}} {{keyvalue|info_objective_2}}.
* {{keyname|"script_obj3_marker"}} {{keyvalue|info_objective_3}}.
* {{keyname|"script_obj4_marker"}} {{keyvalue|info_objective_4}}.

Info Objectives

2007-11-23T14:04:25Z

DavidE: /* Entity keys */

Levelshot

2007-11-22T19:15:45Z

DavidE:

{{first etqwmap toc}}
The map image used on the loading screen. Typically a 256x256 pixel image using a normal aspect ratio image as the source.

Levelshot

2007-11-22T19:14:49Z

DavidE:

Simple the image used on the loading screen. Typically 256x256 pixels (squashed image) using a normal aspect ratio image as the source.

Creating a command map

2007-11-22T19:13:27Z

DavidE:

{{first etqwmap toc}}
Command maps are created by using the [[mapshots|mapshot]] command from the game. Check the [[mapshots]] page for more information.
Once you are happy with your command maps they are specified in the [[playzones#playzone_commandmap|playzone_commandmap]] entity. By default a mapshot will create an image of the full 40960 unit bounds of the map. This is the image to be used by the oob command map. Since the playable area is 32768 units we only want to keep the inside 80% of the image for the regular command map. Within Photoshop the canvas size command (Image > Canvas Size) is used to crop the image. Be sure to set the anchor to the middle of the image and make the new size 80 percent. There is also a .psd in the commandmaps folder, in the sdk to be used to make the oob commandmap. Copy your mapshot result into the layer above "for_Slipgate" and save your oob command map.

Creating a command map

2007-11-22T19:12:46Z

DavidE:

Command maps are created by using the [[mapshots|mapshot]] command from the game. Check the [[mapshots]] page for more information.
Once you are happy with your command maps they are specified in the [[playzones#playzone_commandmap|playzone_commandmap]] entity. By default a mapshot will create an image of the full 40960 unit bounds of the map. This is the image to be used by the oob command map. Since the playable area is 32768 units we only want to keep the inside 80% of the image for the regular command map. Within Photoshop the canvas size command (Image > Canvas Size) is used to crop the image. Be sure to set the anchor to the middle of the image and make the new size 80 percent. There is also a .psd in the commandmaps folder, in the sdk to be used to make the oob commandmap. Copy your mapshot result into the layer above "for_Slipgate" and save your oob command map.

Creating a command map

2007-11-22T19:08:05Z

DavidE:

Creating a command map

2007-11-22T18:59:49Z

DavidE:

Command maps are created by using the [[mapshot|mapshots]] command from the game. Check the [[mapshots]] page for more information.
Once you are happy with your command maps it is specified in the [[playzone_commandmap|playzones#playzone_commandmap]] entity.

Masks

2007-11-22T18:56:12Z

DavidE:

{{first etqwmap toc}}
There are four different types of masks used in ETQW maps;

* The deploy mask - Mask to used to specify where deployables may be deployed.
* The MCP deploy mask - Mask to used to specify where the MCP can be deployed.
* The MCP Route mask - Mask to used to specify where the MCP may be driven before it is deemed off course.
* The Playable area mask - Mask where the player may travel.

They are all 128x128 pixel images, usually saved in the masks/mapname folder. The example map has all white masks so you can deploy and drive the mcp anywhere. Obviously this isn't ideal for a final map, so the white areas are usually built up using the [[mask editor]].
The paths to the masks are specified on the [[playzones|playzone]].

Masks

2007-11-22T18:56:00Z

DavidE:

Masks

2007-11-22T18:44:03Z

DavidE:

{{first etqwmap toc}}
There are four different types of masks used in ETQW maps.

Masks

2007-11-22T18:40:04Z

DavidE:

There are four different types of masks used in ETQW maps.

Playzones

2007-11-22T18:33:21Z

DavidE: /* playzone_deploy */

{{first etqwmap toc}}
Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, a 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area (oob), so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a [[masks|mask]] is specified. It is the [[masks]] themselves which control where aspects of the game may take place.

In the example map there are the following playzone entities;

== playzone_commandmap ==

There are two playzone_commandmap entities used. One for the main gameplay area, and one for the oob. They are used to specify a command map based on the players position. This is so that when the player enters the oob, their command map can change to one with a red border. The oob playzone covers the whole 40960 bounds of the map, whereas the regular playzone is 32768 units. Since the player is often under both playzone_commandmap brushes, the oob playzone_commandmap has a lower priority.

=== Entity keys ===

* {{keyname|mtr_commandmap}} {{keyvalue|commandmaps/etqwmap}}
: Material name of the command map to use when the player is under this playzone.
* {{keyname|priority}} {{keyvalue|0}}
: If the player is under multiple playzones, the playzone with highest priority is used.

== playzone_deploy ==

Used to specify where the following three masks should be taken into account;
* Deploy mask (dm_default)
* MCP Deploy mask (dm_mcp)
* MCP Route mask (dm_mcp_route)

=== Entity keys ===

* {{keyname|dm_default}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where deployables may be deployed.
* {{keyname|dm_mcp}} {{keyvalue|masks/etqwmap/mcp}}
: Mask to used to specify where the MCP can be deployed.
* {{keyname|dm_mcp_route}} {{keyvalue|masks/etqwmap/mcp_route}}
: Mask to used to specify where the MCP may be driven before it is deemed off course.

== playzone_path_and_heightmap ==

Used to generate heightmap data used by the magog sky crane, precipitation system and some other things.

=== Entity keys ===

* {{keyname|hm_default}} {{keyvalue|masks/etqwmap/default}}
: Where to write the heightmap image.

== playzone_play ==

Used to specify the mask where players may travel around the map

=== Entity keys ===

* {{keyname|dm_playzone}} {{keyvalue|masks/etqwmap/playzone}}
: Mask where the player may travel.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T18:20:27Z

DavidE:

{{first etqwmap toc}}
Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, a 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area (oob), so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a [[masks|mask]] is specified. It is the [[masks]] themselves which control where aspects of the game may take place.

In the example map there are the following playzone entities;

== playzone_commandmap ==

There are two playzone_commandmap entities used. One for the main gameplay area, and one for the oob. They are used to specify a command map based on the players position. This is so that when the player enters the oob, their command map can change to one with a red border. The oob playzone covers the whole 40960 bounds of the map, whereas the regular playzone is 32768 units. Since the player is often under both playzone_commandmap brushes, the oob playzone_commandmap has a lower priority.

=== Entity keys ===

* {{keyname|mtr_commandmap}} {{keyvalue|commandmaps/etqwmap}}
: Material name of the command map to use when the player is under this playzone.
* {{keyname|priority}} {{keyvalue|0}}
: If the player is under multiple playzones, the playzone with highest priority is used.

== playzone_deploy ==

Used to specify where the following three masks should be taken into account;
* Deploy mask
* MCP Deploy mask
* MCP Route mask

=== Entity keys ===

* {{keyname|dm_default}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where deployables may be deployed.
* {{keyname|dm_mcp}} {{keyvalue|masks/etqwmap/mcp}}
: Mask to used to specify where the MCP can be deployed.
* {{keyname|dm_mcp_route}} {{keyvalue|masks/etqwmap/mcp_route}}
: Mask to used to specify where the MCP may be driven before it is deemed off course.

== playzone_path_and_heightmap ==

Used to generate heightmap data used by the magog sky crane, precipitation system and some other things.

=== Entity keys ===

* {{keyname|hm_default}} {{keyvalue|masks/etqwmap/default}}
: Where to write the heightmap image.

== playzone_play ==

Used to specify the mask where players may travel around the map

=== Entity keys ===

* {{keyname|dm_playzone}} {{keyvalue|masks/etqwmap/playzone}}
: Mask where the player may travel.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T18:07:37Z

DavidE:

{{first etqwmap toc}}
Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, a 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area (oob), so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a [[masks|mask]] is specified. It is the [[masks]] themselves which control where aspects of the game may take place.

In the example map there are the following playzone entities;

== playzone_commandmap ==

There are two playzone_commandmap entities used. One for the main gameplay area, and one for the oob. They are used to specify a command map based on the players position. This is so that when the player enters the oob, their command map can change to one with a red border. The oob playzone covers the whole 40960 bounds of the map, whereas the regular playzone is 32768 units. Since the player is often under both playzone_commandmap brushes, the oob playzone_commandmap has a lower priority.

=== Entity keys ===

* {{keyname|mtr_commandmap}} {{keyvalue|commandmaps/etqwmap}}
: Material name of the command map to use when the player is under this playzone.
* {{keyname|priority}} {{keyvalue|0}}
: If the player is under multiple playzones, the playzone with highest priority is used.

== playzone_deploy ==

Used to specify where the following three masks should be taken into account;
* Deploy mask
* MCP Deploy mask
* MCP Route mask

=== Entity keys ===

* {{keyname|dm_default}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where deployables may be deployed.
* {{keyname|dm_mcp}} {{keyvalue|masks/etqwmap/mcp}}
: Mask to used to specify where the MCP can be deployed.
* {{keyname|dm_mcp_route}} {{keyvalue|masks/etqwmap/mcp_route}}
: Mask to used to specify where the MCP may be driven before it is deemed off course.

== playzone_path_and_heightmap ==

Used to generate heightmap data used by the magog sky crane, precipitation system and some other things.

* {{keyname|hm_default}} {{keyvalue|masks/etqwmap/default}}
: Heightmap image.

=== Entity keys ===

== playzone_play ==

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T17:46:19Z

DavidE:

{{first etqwmap toc}}
Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, a 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area (oob), so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a [[masks|mask]] is specified. It is the [[masks]] themselves which control where aspects of the game may take place.

In the example map there are the following playzone entities;

== playzone_commandmap ==

There are two playzone_commandmap entities used. One for the main gameplay area, and one for the oob. They are used to specify a command map based on the players position. This is so that when the player enters the oob, their command map can change to one with a red border. The oob playzone covers the whole 40960 bounds of the map, whereas the regular playzone is 32768 units. Since the player is often under both playzone_commandmap brushes, the oob playzone_commandmap has a lower priority.

=== Entity keys ===

* {{keyname|mtr_commandmap}} {{keyvalue|commandmaps/etqwmap}}
: Material name of the command map to use when the player is under this playzone.
* {{keyname|priority}} {{keyvalue|0}}
: If the player is under multiple playzones, the playzone with highest priority is used.

== playzone_deploy ==

Used to specify where the following three masks should be taken into account;
* Deploy mask
* MCP Deploy mask
* MCP Route mask

=== Entity keys ===

* {{keyname|dm_default}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where deployables may be deployed.
* {{keyname|dm_mcp}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where the MCP can be deployed.
* {{keyname|dm_mcp_route}} {{keyvalue|masks/etqwmap/default}}
: Mask to used to specify where the MCP may be driven before it is deemed off course.

== playzone_path_and_heightmap ==

== playzone_play ==

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T17:37:56Z

DavidE:

Playzones

2007-11-22T17:11:09Z

DavidE:

Playzones

2007-11-22T17:07:24Z

DavidE:

{{first etqwmap toc}}
Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, the 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area, so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a mask is specified. It is the masks themselves which control where aspects of the game may take place.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T17:07:07Z

DavidE:

Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, the 32768 unit square. However, a typical ETQW map is larger due to an out of bounds area, so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a mask is specified. It is the masks themselves which control where aspects of the game may take place.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T17:04:33Z

DavidE:

Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, the 32768 unit square. A typical ETQW map is larger due to an out of bounds area, so actual bounds of a map are a 40960 unit square. Playzone brushes are used to specify the main gameplay bounds of a map. It is on these brushes that a mask is specified. The themselves control where the different aspects of the game may take place.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Playzones

2007-11-22T16:46:10Z

DavidE:

Many aspects of the game (such as deploying and traveling before being warned of leaving the battlefield) take place in the main gameplay area of the map, the 32768 unit square. A typical ETQW map is larger due to an out of bounds area, so actual bounds of a map are a 40960 unit square. Playzones are used to specify the main gameplay area where the deploymask is to be used.

== See Also ==
* [[Portal Basics]]
* [[Entity playzone_commandmap|playzone_commandmap]]
* [[Entity playzone_deploy|playzone_deploy]]
* [[Entity playzone_marker|playzone_marker]]
* [[Entity playzone_path_and_heightmap|playzone_path_and_heightmap]]
* [[Entity playzone_play|playzone_play]]

[[Category:Advanced Level Design]]

Deployzones

2007-11-22T14:43:49Z

DavidE: /* shield_deployzone */

Deployzones

2007-11-22T14:37:47Z

DavidE: /* strogg_base_deployzone */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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 ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}}
* {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}}
* {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}}
* {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the outpost territory]]

=== shield_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_04}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_icarus_2}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_hog}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the shield territory]]

=== strogg_base_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_05}}
* {{keyname|start_team}} {{keyvalue|strogg}}

=== Common entity keys ===

These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:37:04Z

DavidE: /* Vehicles and deployzones */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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 ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}}
* {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}}
* {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}}
* {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the outpost territory]]

=== shield_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_04}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_icarus_2}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_hog}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the shield territory]]

=== strogg_base_deployzone ===

=== Common entity keys ===

These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:36:38Z

DavidE: /* Vehicles and deployzones */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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, so they game knows which vehicles to spawn/destroy when territory changes hands.

== Entity keys ==

=== gdf_base_deployzone ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}}
* {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}}
* {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}}
* {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the outpost territory]]

=== shield_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_04}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_icarus_2}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_hog}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the shield territory]]

=== strogg_base_deployzone ===

=== Common entity keys ===

These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:33:26Z

DavidE:

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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.

== Entity keys ==

=== gdf_base_deployzone ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_03}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|outpost_gdf_badger}}
* {{keyname|target_gdf2}} {{keyvalue|outpost_gdf_trojan}}
* {{keyname|target_gdf3}} {{keyvalue|outpost_gdf_titan}}
* {{keyname|target_gdf4}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_gdf5}} {{keyvalue|outpost_gdf_husky}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_strogg_hog}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_strogg_desecrator}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg4}} {{keyvalue|outpost_icarus_2}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the outpost territory]]

=== shield_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_04}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_strogg1}} {{keyvalue|outpost_icarus_1}}
* {{keyname|target_strogg2}} {{keyvalue|outpost_icarus_2}}
* {{keyname|target_strogg3}} {{keyvalue|outpost_hog}}

We have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_3|vehicles associated with the shield territory]]

=== strogg_base_deployzone ===

=== Common entity keys ===

These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:27:22Z

DavidE: /* outpost_deployzone */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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.

== Entity keys ==

=== gdf_base_deployzone ===

* {{keyname|objective_index}} {{keyvalue|0}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|objective_index}} {{keyvalue|1}}
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|mcp_stay_deployed}} {{keyvalue|1}}
: MCP is deployed in this deployzone.
* {{keyname|objective_index}} {{keyvalue|2}}
* {{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 outpost territory]]

=== shield_deployzone ===
=== strogg_base_deployzone ===
=== Common entity keys ===
These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:26:18Z

DavidE: /* Entity keys */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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.

== Entity keys ==

=== gdf_base_deployzone ===

* {{keyname|objective_index}} {{keyvalue|0}}
: The game uses objective_index to determine which objective this is. First objective is 0, second is 1 ect.
* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|objective_index}} {{keyvalue|1}}
* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== outpost_deployzone ===

* {{keyname|objective_index}} {{keyvalue|2}}
* {{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 outpost territory]]

=== shield_deployzone ===
=== strogg_base_deployzone ===
=== Common entity keys ===
These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:24:54Z

DavidE: /* Entity keys */

{{first etqwmap toc}}
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 [[Common Textures#common/trigger|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.

== Entity keys ==

=== gdf_base_deployzone ===

* {{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.
* {{keyname|start_team}} {{keyvalue|gdf}}
: The team which owns the territory at map start.

=== bridge_deployzone ===

* {{keyname|mtr_territory}} {{keyvalue|commandmaps/etqwmap_territory_02}}
* {{keyname|start_team}} {{keyvalue|strogg}}
* {{keyname|target_gdf1}} {{keyvalue|bridge_gdf_badger}}
: First vehicle granted to the GDF when they own the territory.
* {{keyname|target_gdf2}} {{keyvalue|bridge_gdf_husky}}
: Second vehicle granted to the GDF 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 have already added the [[Adding_Objective_spawns_and_vehicles#Vehicles_2|vehicles associated with the bridge territory]]

=== 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 ===
=== strogg_base_deployzone ===
=== Common entity keys ===
These key pairs are common across all deployzones;
* {{keyname|territory_start}} {{keyvalue|0 0}}
: FIXME.
* {{keyname|territory_end}} {{keyvalue|1 1}}
: FIXME.
* {{keyname|target_playzone}} {{keyvalue|territory_size_thing}}
: The playzone entity used to determine the bounds of the map territories.

Deployzones

2007-11-22T14:11:52Z

DavidE: /* Common entity keys */

Deployzones

2007-11-22T12:25:20Z

DavidE: /* bridge_deployzone */

Deployzones

2007-11-22T12:25:11Z

DavidE: /* bridge_deployzone */

Deployzones

2007-11-22T12:22:50Z

DavidE: /* Entity keys */

Deployzones

2007-11-22T12:22:06Z

DavidE: /* bridge_deployzone */

Deployzones

2007-11-22T12:21:45Z

DavidE:

Deployzones

2007-11-22T12:14:00Z

DavidE:

Deployzones

2007-11-22T12:03:03Z

DavidE:

{{first etqwmap toc}}
Deployzone entities are used to determine where territories exist within a map. They are brush based entities using the [[Common Textures#common/trigger|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.

== Entity keys ==

=== gdf_base_deployzone ===
=== bridge_deployzone ===
=== outpost_deployzone ===
=== shield_deployzone ===
=== strogg_base_deployzone ===
=== Common entity keys ===

Adding Objective spawns and vehicles

2007-11-22T11:51:09Z

DavidE: /* Entity keys */

{{first etqwmap toc}}
==Spawn masters==
Groups of spawn points are triggered throughout the map by the [[Entity info_spawn_master|info_spawn_master]] entity. When an [[Entity info_spawn_master|info_spawn_master]] is active, the spawn points associated with it are available to the team. When more than one [[Entity info_spawn_master|info_spawn_master]] is active, the one with higher priority becomes the default spawn for the player. For example, in the valley map, only one [[Entity info_spawn_master|info_spawn_master]] at the GDF base is active at map start. When the bridge is built, an [[Entity info_spawn_master|info_spawn_master]] at the bridge is activated with a priority of 2. This makes the spawn point default for the GDF since the priority number is higher. The priority of a GDF spawn master is defined by adding key of {{keyname|spawn_priority_gdf}} and a value being the priority number. To associate spawns with spawn masters we need to add a key {{keyname|owner}} and a value matching the name of the spawn master.

== Bridge objective ==

=== Spawn points ===

The initial spawn points for the GDF will have a priority of 1. An [[Entity info_spawn_master|info_spawn_master]] has been placed amongst the spawns at our GDF base, which we added here [[Adding player spawns]]. Its vertical position is not important, however its horizontal position will define where we see the flag on the command map, so place it near our spawns. To associate spawns with spawn masters we need to add a key {{keyname|owner}} and a value matching the name of the spawn master. We will call the [[Entity info_spawn_master|info_spawn_master]] at the gdf base "gdf_base_spawnmaster". The strogg will be spawning near the bridge. Their info_spawn_master is named "strogg_bridge_spawnmaster". Since we want the strogg spawning here by default, over the three other spawns, we will give this a priority of 4.

===== Entity keys =====

The following key pairs are used on each of the info_team_gdf_spawn entities:

* {{keyname|owner}} {{keyvalue|gdf_base_spawnmaster}}
: Which spawn master they belong to.

* {{keyname|parachute}} {{keyvalue|1}}
: Whether the player is dropped in by parachute (or landing shield for Strogg).

The following key pairs are used on each of the info_team_strogg_spawn entities:

* {{keyname|owner}} {{keyvalue|strogg_bridge_spawnmaster}}

* {{keyname|parachute}} {{keyvalue|1}}

The following key pair is used on the GDF's info_spawn_master entity:

* {{keyname|spawn_priority_gdf}} {{keyvalue|1}}
: Spawn priority.

The following key pair is used on the Strogg's info_spawn_master entity:

* {{keyname|spawn_priority_strogg}} {{keyvalue|4}}

=== Vehicles ===

During the first objective the GDF's vehicles spawn in their base. Adding vehicles which spawn at map start and are never triggered off (ie 'base vehicles') is explained here [[Adding base vehicles]].

Some vehicles are required to only be active when a team owns some territory. This is the case with the strogg vehicles during the first objective. To add one, use the entity deployable_spawn_<vehiclename>.

* [[Entity deployable_spawn_anansi|deployable_spawn_anansi]] - Anansi
* [[Entity deployable_spawn_badger|deployable_spawn_badger]] - Armadillo
* [[Entity deployable_spawn_bumblebee|deployable_spawn_bumblebee]] - Bumblebee
* [[Entity deployable_spawn_desecrator|deployable_spawn_desecrator]] - Desecrator
* [[Entity deployable_spawn_goliath|deployable_spawn_goliath]] - Goliath
* [[Entity deployable_spawn_hog|deployable_spawn_hog]] - Hog
* [[Entity deployable_spawn_hornet|deployable_spawn_hornet]] - Tormentor
* [[Entity deployable_spawn_husky|deployable_spawn_husky]] - Husky
* [[Entity deployable_spawn_icarus|deployable_spawn_icarus]] - Icarus
* [[Entity deployable_spawn_mcp|deployable_spawn_mcp]] - MCP
* [[Entity deployable_spawn_platypus|deployable_spawn_platypus]] - Platypus
* [[Entity deployable_spawn_titan|deployable_spawn_titan]] - Titan
* [[Entity deployable_spawn_trojan|deployable_spawn_trojan]] - Trojan

Two icarus' have been added for the strogg near their spawn;

* 2 x deployable_spawn_icarus named "bridge_strogg_icarus_1" and "bridge_strogg_icarus_2"

===== Entity keys =====
deployable_spawn_<vehiclename> entities do not have any required key pairs. However their name is important when they targeted by [[Deployzones]]

== MCP objective ==

=== Spawn points ===

Spawns have been placed at the bridge for the GDF. These will be available to the GDF once the bridge has been built. The spawn master here is called "gdf_bridge_spawnmaster", with a priority of 2. The strogg spawn master for the MCP objective is called "strogg_outpost_spawnmaster", with a priority of 3.

==== Entity keys ====

The following key pairs are used on each of the info_team_gdf_spawn entities:

* {{keyname|owner}} {{keyvalue|gdf_bridge_spawnmaster}}

* {{keyname|parachute}} {{keyvalue|1}}

The following key pairs are used on each of the info_team_strogg_spawn entities:

* {{keyname|owner}} {{keyvalue|strogg_outpost_spawnmaster}}

* {{keyname|parachute}} {{keyvalue|1}}

The following key pair is used on the GDF's info_spawn_master entity:

* {{keyname|spawn_priority_gdf}} {{keyvalue|2}}

The following key pair is used on the Strogg's info_spawn_master entity:

* {{keyname|spawn_priority_strogg}} {{keyvalue|3}}

=== Vehicles ===

For the MCP objective the GDF have the following vehicles;

* 1x deployable_spawn_badger named "gdf_bridge_badger"
* 1x deployable_spawn_husky named "gdf_bridge_husky"

When the capturable spawn is activated by the GDF they granted;

* 1x deployable_spawn_badger named "capturable_spawn_1_badger"
* 1x deployable_spawn_husky named "capturable_spawn_1_husky"

Vehicles are spawned at capturable spawns by targeting a deployable_spawn_<vehiclename> with the info_capturable_spawn_gdf entity we create in the next step.
The strogg have the following vehicles at their spawn;

* 1x deployable_spawn_hog named "outpost_strogg_hog"
* 1x deployable_spawn_desecrator named "outpost_strogg_desecrator"

=== GDF Capturable spawn ===

Capturable spawns are essentially spawn masters that can be toggled by either team. Capturable spawns can be active or inactive at the start of an objective (For example at the start of Volcano a capturable spawn is active for GDF but not for Strogg) A GDF capturable spawn has been added across the bridge for use during the MCP objective by adding a [[info_capturable_spawn_gdf]] entity. It is called "info_capturable_spawn_gdf_1"

==== Entity keys ====

The following key pairs are used on the GDF's info_capturable_spawn_gdf entity:

* {{keyname|spawn_priority_gdf}} {{keyvalue|3}}
: Spawn priority
* {{keyname|target_gdf1}} {{keyvalue|capturable_spawn_2_husky}}
: The first granted vehicle when GDF capture the spawn
* {{keyname|target_gdf2}} {{keyvalue|capturable_spawn_2_badger}}
: The second granted vehicle when GDF capture the spawn

== Shield objective ==

=== Spawn points ===

Spawns have been placed at the outpost for the GDF. These will be available to the GDF once the outpost has been captured. The spawn master here is called "gdf_outpost_spawnmaster", with a priority of 4. The strogg spawn master for the Shield generator objective is called "strogg_shield_spawnmaster", with a priority of 2.

==== Entity keys ====

The following key pairs are used on each of the info_team_gdf_spawn entities:

* {{keyname|owner}} {{keyvalue|gdf_outpost_spawnmaster}}

* {{keyname|parachute}} {{keyvalue|1}}

The following key pairs are used on each of the info_team_strogg_spawn entities:

* {{keyname|owner}} {{keyvalue|strogg_shield_spawnmaster}}

* {{keyname|parachute}} {{keyvalue|1}}

The following key pair is used on the GDF's info_spawn_master entity:

* {{keyname|spawn_priority_gdf}} {{keyvalue|4}}

The following key pair is used on the Strogg's info_spawn_master entity:

* {{keyname|spawn_priority_strogg}} {{keyvalue|2}}

=== Vehicles ===

For the Shield generator objective the GDF have the following vehicles;

* 1x deployable_spawn_badger named "gdf_outpost_badger"
* 1x deployable_spawn_husky named "gdf_outpost_husky"
* 1x deployable_spawn_titan named "gdf_outpost_titan"
* 1x deployable_spawn_trojan named "gdf_outpost_trojan"
* 1x deployable_spawn_bumblebee named "gdf_outpost_bumblebee"

Upon activating the capturable spawn the GDF are granted;
* 1x deployable_spawn_badger named "capturable_spawn_2_badger"
* 1x deployable_spawn_husky named "capturable_spawn_2_husky"

The strogg have the following vehicles;

* 1x deployable_spawn_hog named "shield_strogg_hog"
* 2x deployable_spawn_icarus named "shield_strogg_icarus_1" and "shield_strogg_icarus_2"

=== GDF Capturable spawn ===

A GDF capturable spawn has been added near the Shield for use during the Shield generator objective by adding a [[info_capturable_spawn_gdf]] entity. It is named "info_capturable_spawn_gdf_2". This capturable spawn will be the default spawn for the GDF during the final objective.

==== Entity keys ====

The following key pairs are used on the GDF's info_capturable_spawn_gdf entity:

* {{keyname|spawn_priority_gdf}} {{keyvalue|5}}
: Spawn priority
* {{keyname|target_gdf1}} {{keyvalue|capturable_spawn_1_husky}}
: The first granted vehicle when GDF capture the spawn
* {{keyname|target_gdf2}} {{keyvalue|capturable_spawn_1_badger}}
: The second granted vehicle when GDF capture the spawn

== Destruction objective ==

=== Spawn points ===

During the final objective we will have the Strogg spawning in their base. Since this is the furthest back they spawn, the priority is 1. The spawn master here is called "strogg_base_spawnmaster". The GDF will spawn at the previous capturable spawn.

==== Entity keys ====

The following key pair is used on the Strogg's info_spawn_master entity:

* {{keyname|spawn_priority_strogg}} {{keyvalue|1}}

=== Vehicles ===

During the final objective the following Strogg vehicles spawn in their base;

* 1x deployable_spawn_hornet
* 1x deployable_spawn_desecrator
* 1x deployable_spawn_hog
* 2x deployable_spawn_icaurus

The GDF will have the vehicles granted to them by the capturable spawn near the shield generator since this now their default spawn.

== Worldspawn keys ==

The info_spawn_master entities require the following worldspawn keys;

* {{keyname|"script_gdf_base_spawn"}} {{keyvalue|gdf_base_spawnmaster}}.
* {{keyname|"script_gdf_bridge_spawn"}} {{keyvalue|gdf_bridge_spawnmaster}}.
* {{keyname|"script_gdf_outpost_spawn"}} {{keyvalue|gdf_outpost_spawnmaster}}.
* {{keyname|"script_strogg_base_spawn"}} {{keyvalue|strogg_base_spawnmaster}}.
* {{keyname|"script_strogg_shield_spawn"}} {{keyvalue|strogg_shield_spawnmaster}}.
* {{keyname|"script_strogg_outpost_spawn"}} {{keyvalue|strogg_outpost_spawnmaster}}.
* {{keyname|"script_strogg_bridge_spawn"}} {{keyvalue|strogg_bridge_spawnmaster}}.

The info_capturable_spawn_gdf entities require the following worldspawn keys;

* {{keyname|"script_capturable_spawn_gdf_1"}} {{keyvalue|info_capturable_spawn_gdf_1}}.
* {{keyname|"script_capturable_spawn_gdf_2"}} {{keyvalue|info_capturable_spawn_gdf_2}}.

== See Also ==
* [[Entity info_spawn_master|info_spawn_master]]
* [[Entity info_team_gdf_spawn|info_team_gdf_spawn]]
* [[Entity info_team_strogg_spawn|info_team_strogg_spawn]]

Deployzones

2007-11-22T11:49:19Z

DavidE:

Deployzones

2007-11-22T11:45:10Z

DavidE:

{{first etqwmap toc}}
Deployzone entities are used to determine where territories exist within a map. They are brush based entities using the [[Common Textures#common/trigger|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

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.

== Entity keys ==

=== gdf_base_deployzone ===
=== bridge_deployzone ===
=== outpost_deployzone ===
=== shield_deployzone ===
=== strogg_base_deployzone ===

Deployzones

2007-11-22T11:43:22Z

DavidE:

{{first etqwmap toc}}
Deployzone entities 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

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.

== Entity keys ==

=== gdf_base_deployzone ===
=== bridge_deployzone ===
=== outpost_deployzone ===
=== shield_deployzone ===
=== strogg_base_deployzone ===

Info Objectives

2007-11-22T11:40:26Z

DavidE:

Necessary map declarations

2007-11-22T11:40:12Z

DavidE:

{{first etqwmap toc}}
Here is a list of materials for assets created later on. Simply copy the text from the box below and save to {{filename|materials/yourmapname.mtr}} Don't forget to find/replace 'etqwmap' with yourmapname.

#include <materials/commandmaps.include>

// ====================================================
// ETQW Map Megatexture materials
// ====================================================

material megatextures/etqwmap { useTemplate megatextures/default_ambient_spec< "etqwmap" > }
material megatextures/etqwmap_noshadows { useTemplate megatextures/default_ambient_spec_noshadows< "etqwmap" > }

// ====================================================
// ETQW Map Command map materials
// ====================================================

material commandmaps/etqwmap
{
templates/game/maps/cmMap( "commandmaps/etqwmap.tga" )
}

// larger scale map for out of bounds area
material commandmaps/etqwmap_oob
{
templates/game/maps/cmMap( "commandmaps/etqwmap_oob.tga" )
}

material commandmaps/etqwmap_territory_01 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter01.tga ) )
}

material commandmaps/etqwmap_territory_02 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter02.tga ) )
}

material commandmaps/etqwmap_territory_03 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter03.tga ) )
}

material commandmaps/etqwmap_territory_04 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter04.tga ) )
}

material commandmaps/etqwmap_territory_05 {
templates/game/maps/cmIcon( makealpha( commandmaps/etqwmap/etqwmap_ter05.tga ) )
}

material levelshots/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/etqwmap"
}
}

material levelshots/thumbs/etqwmap {
sort gui
{
blend blend
vertexColor
map nopicmip clamp "levelshots/thumbs/etqwmap"
}
}

Here are the map definitions needed for a functioning map. Save these to def/yourmapname.def

#include "def/pathfinder.include"

heightMap heightmaps/etqwmap {
heightMap "heightmaps/etqwmap.tga"
}

deployMask masks/etqwmap/mcp {
mask "masks/etqwmap/mcp.tga"
}

deployMask masks/etqwmap/default {
mask "masks/etqwmap/default.tga"
}

deployMask masks/etqwmap/mcp_route {
mask "masks/etqwmap/mcp_route.tga"
}

deployMask masks/etqwmap/playzone {
mask "masks/etqwmap/playzone.tga"
}

stringMap pathfinder_etqwmap {
_pathfinder_default( "etqwmap", 20 )
"playzone_0" "etqwmap_playzone_path_and_heightmap"
"resolution_x_playzone_0" "1280"
"resolution_y_playzone_0" "1280"
"mg_resolution_x_playzone_0" "1280"
"mg_resolution_y_playzone_0" "1280"
}

[[Category:Basic Level Design]]

Deployzones

2007-11-22T11:28:43Z

DavidE:

{{first etqwmap toc}}
Deployzones 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

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.

== Entity keys ==

=== gdf_base_deployzone ===
=== bridge_deployzone ===
=== outpost_deployzone ===
=== shield_deployzone ===
=== strogg_base_deployzone ===