Difference between revisions of "Template:Control Point Timing/doc"

From Team Fortress Wiki
Jump to: navigation, search
m (add missing cats)
(Updated documentation for new template option)
Line 1: Line 1:
 
This template will generate a control point breakdown for up to six points.  Using values from the raw map info.  The entity '''trigger_capture_area''' contains two values needed, ''area_time_to_cap'' and ''team_numcap_2/3''  The value for ''area_time_to_cap'' is used for the AREAX parameters, and the ''team_numcap_2/3'' is used for the TEAMX parameters.
 
This template will generate a control point breakdown for up to six points.  Using values from the raw map info.  The entity '''trigger_capture_area''' contains two values needed, ''area_time_to_cap'' and ''team_numcap_2/3''  The value for ''area_time_to_cap'' is used for the AREAX parameters, and the ''team_numcap_2/3'' is used for the TEAMX parameters.
  
There are 10 sections available for this template, 0 though 9, and the multiplier count can be shown by setting ROWS, which defaults to 4.
+
There are 10 sections available for this template, 0 though 9, and the multiplier count can be shown by setting the global ROWS, which defaults to 4, or individual ROWS0 - ROWS9 to tune for varied maps.
  
 
For example, using values for Badlands:
 
For example, using values for Badlands:
Line 16: Line 16:
 
| AREA3 = 10
 
| AREA3 = 10
 
| TEAM3 = 1
 
| TEAM3 = 1
| ROWS = 24
+
| ROWS = 4
 +
| ROWS3 = 5
 
}}
 
}}
 
</pre>
 
</pre>
Line 32: Line 33:
 
| AREA3 = 10
 
| AREA3 = 10
 
| TEAM3 = 1
 
| TEAM3 = 1
| ROWS = 24
+
| ROWS = 4
 +
| ROWS3 = 5
 
}}
 
}}
  

Revision as of 06:55, 12 August 2010

This template will generate a control point breakdown for up to six points. Using values from the raw map info. The entity trigger_capture_area contains two values needed, area_time_to_cap and team_numcap_2/3 The value for area_time_to_cap is used for the AREAX parameters, and the team_numcap_2/3 is used for the TEAMX parameters.

There are 10 sections available for this template, 0 though 9, and the multiplier count can be shown by setting the global ROWS, which defaults to 4, or individual ROWS0 - ROWS9 to tune for varied maps.

For example, using values for Badlands:

{{Control Point Timing
| MAPNAME = Badlands
| NAME1 = Control points 1 & 5
| AREA1 = 1
| TEAM1 = 1
| NAME2 = Control points 2 & 4
| AREA2 = 8
| TEAM2 = 1
| NAME3 = Control point 3
| AREA3 = 10
| TEAM3 = 1
| ROWS  = 4
| ROWS3 = 5
}}

Generates

Badlands
Control Point Multiplier Seconds
Control points 1 & 5 ×1
2 .000
×2
1 .333
×3
1 .091
×4
0 .960
Control points 2 & 4 ×1
16 .000
×2
10 .667
×3
8 .727
×4
7 .680
Control point 3 ×1
20 .000
×2
13 .333
×3
10 .909
×4
9 .600
×5
8 .759


Caution! Caution: This is a fairly complex template and the following templates must remain intact for this to continue to operate.