Template:Tournament data: Difference between revisions
More actions
m Build reusable tournament data and rendering system |
m Build reusable tournament data and rendering system |
||
| Line 5: | Line 5: | ||
|image={{{image|}}} | |image={{{image|}}} | ||
|type={{{type|Player Run Festival}}} | |type={{{type|Player Run Festival}}} | ||
|format={{{format|}}} | |format={{{format|}}} | ||
|mode={{{mode|}}} | |mode={{{mode|}}} | ||
| Line 47: | Line 46: | ||
|image={{{image|}}} | |image={{{image|}}} | ||
|type={{{type|Player Run Festival}}} | |type={{{type|Player Run Festival}}} | ||
|format={{{format|}}} | |format={{{format|}}} | ||
|mode={{{mode|}}} | |mode={{{mode|}}} | ||
| Line 89: | Line 87: | ||
|image={{{image|}}} | |image={{{image|}}} | ||
|type={{{type|Player Run Festival}}} | |type={{{type|Player Run Festival}}} | ||
|format={{{format|}}} | |format={{{format|}}} | ||
|mode={{{mode|}}} | |mode={{{mode|}}} | ||
| Line 134: | Line 131: | ||
|image={{{image|}}} | |image={{{image|}}} | ||
|type={{{type|Player Run Festival}}} | |type={{{type|Player Run Festival}}} | ||
|format={{{format|}}} | |format={{{format|}}} | ||
|mode={{{mode|}}} | |mode={{{mode|}}} | ||
| Line 216: | Line 212: | ||
</pre> | </pre> | ||
For 1v1, use <code>winner</code>, <code>second</code>, and <code>third</code> instead of team names and member fields. | For 1v1, use <code>winner</code>, <code>second</code>, and <code>third</code> instead of team names and member fields. Upcoming status is derived automatically from <code>date</code>; leave result fields blank until the event has taken place. | ||
Chronology months are read from linked tournament records. The legacy <code>previousmonth</code>, <code>nextmonth</code>, and town equivalents are only fallbacks while older records are missing. | Chronology months are read from linked tournament records. The legacy <code>previousmonth</code>, <code>nextmonth</code>, and town equivalents are only fallbacks while older records are missing. | ||
| Line 227: | Line 223: | ||
! Group !! Parameters !! Use | ! Group !! Parameters !! Use | ||
|- | |- | ||
| Basic || <code>name</code>, <code>date</code>, <code>image</code>, <code>type | | Basic || <code>name</code>, <code>date</code>, <code>image</code>, <code>type</code> || Identity and date-derived status; <code>type</code> defaults to Player Run Festival | ||
|- | |- | ||
| Details || <code>format</code>, <code>mode</code>, <code>host</code>, <code>continent</code> || Format uses 1v1, 2v2, or 3v3; mode uses Potion or Barebones | | Details || <code>format</code>, <code>mode</code>, <code>host</code>, <code>continent</code> || Format uses 1v1, 2v2, or 3v3; mode uses Potion or Barebones | ||
Revision as of 22:23, 18 August 2026
Workflow
Tournament facts are stored once in a named record such as Template:Tournament data/Riverside I. That record supplies the article infobox, generated prose, chronology dates, and overview row.
- Create
Template:Tournament data/Tournament Nameusing the skeleton below - Put
{{Tournament data/Tournament Name}}on the article - Add
{{Tournament data/Tournament Name|render=row}}to Template:Tournament list
Only the record contains facts. The article and list contain references to it.
Record skeleton
<includeonly>{{Tournament data
|name=Tournament Name
|date=July 19, 2026
|image=
|format=3v3
|mode=Potion
|host=Town Name
|continent=Ascalon
|runner1=
|post=
|challonge=
|winnerteam=
|winner1=
|winner2=
|winner3=
|secondteam=
|second1=
|second2=
|second3=
|thirdteam=
|third1=
|third2=
|third3=
|previous=
|next=
|townprevious=
|townnext=
|render={{{render|article}}}
}}</includeonly>
For 1v1, use winner, second, and third instead of team names and member fields. Upcoming status is derived automatically from date; leave result fields blank until the event has taken place.
Chronology months are read from linked tournament records. The legacy previousmonth, nextmonth, and town equivalents are only fallbacks while older records are missing.
Overall previous and next links come from Template:Tournament chronology, generated from the newest-first registry. Use record-level values only to override an incomplete chronology. Town-specific chronology remains explicit.
Parameters
| Group | Parameters | Use |
|---|---|---|
| Basic | name, date, image, type |
Identity and date-derived status; type defaults to Player Run Festival
|
| Details | format, mode, host, continent |
Format uses 1v1, 2v2, or 3v3; mode uses Potion or Barebones |
| Links | post, challonge |
Numeric forums thread ID and Challonge ID |
| Runners | runner1-runner6 |
Up to six organizers |
| 1v1 results | winner, second, third |
Placed players |
| Team results | winnerteam, secondteam, thirdteam |
Team names for 2v2 or 3v3 |
| Team members | winner1-3, second1-3, third1-3 |
Players in each placed team |
| Overall chronology | previous, next |
Adjacent festivals overall |
| Town chronology | townprevious, townnext |
Adjacent festivals hosted by the same town |
Render modes
article— full article infobox and generated prose (default)card— compact card for tournament listsrow— one row in the chronological tournament listmonth— month and year derived fromdate