Difference between revisions of "Template:Control Point Timing/doc"
m (Added caution message to documentation) |
m (Adjust documentation for Capture return) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | This template will generate a control point breakdown for up to | + | This template will generate a control point breakdown for up to ten 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 7: | Line 7: | ||
{{Control Point Timing | {{Control Point Timing | ||
| MAPNAME = Badlands | | MAPNAME = Badlands | ||
| − | | NAME1 = Control | + | | NAME1 = Control points 1 & 5 |
| AREA1 = 1 | | AREA1 = 1 | ||
| TEAM1 = 1 | | TEAM1 = 1 | ||
| − | | NAME2 = Control | + | | NAME2 = Control points 2 & 4 |
| AREA2 = 8 | | AREA2 = 8 | ||
| TEAM2 = 1 | | TEAM2 = 1 | ||
| − | | NAME3 = Control | + | | NAME3 = Control point 3 |
| AREA3 = 10 | | AREA3 = 10 | ||
| TEAM3 = 1 | | TEAM3 = 1 | ||
| − | | ROWS = | + | | ROWS = 4 |
| + | | ROWS3 = 5 | ||
}} | }} | ||
</pre> | </pre> | ||
| Line 23: | Line 24: | ||
{{Control Point Timing | {{Control Point Timing | ||
| MAPNAME = Badlands | | MAPNAME = Badlands | ||
| − | | NAME1 = Control | + | | NAME1 = Control points 1 & 5 |
| AREA1 = 1 | | AREA1 = 1 | ||
| TEAM1 = 1 | | TEAM1 = 1 | ||
| − | | NAME2 = Control | + | | NAME2 = Control points 2 & 4 |
| AREA2 = 8 | | AREA2 = 8 | ||
| TEAM2 = 1 | | TEAM2 = 1 | ||
| − | | NAME3 = Control | + | | NAME3 = Control point 3 |
| AREA3 = 10 | | AREA3 = 10 | ||
| TEAM3 = 1 | | TEAM3 = 1 | ||
| − | | ROWS = | + | | ROWS = 4 |
| + | | ROWS3 = 5 | ||
}} | }} | ||
{{Caution|This is a fairly complex template and the following templates must remain intact for this to continue to operate.}} | {{Caution|This is a fairly complex template and the following templates must remain intact for this to continue to operate.}} | ||
| − | |||
* [[Template:Control Point Timing/Row]] | * [[Template:Control Point Timing/Row]] | ||
| − | * [[Template:Decimal Align]] | + | * [[Template:Metrics/Capture return]] |
| + | * [[Template:Decimal Align]]<noinclude>[[Category:Template documentation]]</noinclude> | ||
Latest revision as of 23:15, 29 February 2012
This template will generate a control point breakdown for up to ten 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 |
| |||
| ×3 |
| |||
| ×4 |
| |||
| Control points 2 & 4 | ×1 |
| ||
| ×2 |
| |||
| ×3 |
| |||
| ×4 |
| |||
| Control point 3 | ×1 |
| ||
| ×2 |
| |||
| ×3 |
| |||
| ×4 |
| |||
| ×5 |
| |||
 Caution: | This is a fairly complex template and the following templates must remain intact for this to continue to operate. |
