Template:Tournament data: Difference between revisions

Revision as of 22:52, 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 Name using 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=
|reigningchampion=
|championattendance=
|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. Set championattendance to yes or no. The reigning champion is read from the previous 1v1 record automatically; use reigningchampion only while that older record is missing.

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
1v1 championship	`championattendance`, `reigningchampion`	Attendance uses `yes` or `no`; reigning champion is an optional historical override
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 lists
row — one row in the chronological tournament list
month — month and year derived from date

@@ Line 20: / Line 20: @@
 |second={{{second|}}}
 |third={{{third|}}}
+|reigningchampion={{{reigningchampion|}}}
+|championattendance={{{championattendance|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 61: / Line 63: @@
 |second={{{second|}}}
 |third={{{third|}}}
+|reigningchampion={{{reigningchampion|}}}
+|championattendance={{{championattendance|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 102: / Line 106: @@
 |second={{{second|}}}
 |third={{{third|}}}
+|reigningchampion={{{reigningchampion|}}}
+|championattendance={{{championattendance|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 126: / Line 132: @@
 |date={{{date|}}}
 |name={{{name|}}}
+|winner={{{winner|}}}
 |#default={{Infobox tournament
 |name={{{name|{{PAGENAME}}}}}
@@ Line 146: / Line 153: @@
 |second={{{second|}}}
 |third={{{third|}}}
+|reigningchampion={{{reigningchampion|}}}
+|championattendance={{{championattendance|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 192: / Line 201: @@
 |post=
 |challonge=
+|reigningchampion=
+|championattendance=
 |winnerteam=
 |winner1=
@@ Line 212: / Line 223: @@
 </pre>
-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.
+For 1v1, use <code>winner</code>, <code>second</code>, and <code>third</code> instead of team names and member fields. Set <code>championattendance</code> to <code>yes</code> or <code>no</code>. The reigning champion is read from the previous 1v1 record automatically; use <code>reigningchampion</code> only while that older record is missing.
+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.
@@ Line 232: / Line 245: @@
 |-
 | 1v1 results || <code>winner</code>, <code>second</code>, <code>third</code> || Placed players
+|-
+| 1v1 championship || <code>championattendance</code>, <code>reigningchampion</code> || Attendance uses <code>yes</code> or <code>no</code>; reigning champion is an optional historical override
 |-
 | Team results || <code>winnerteam</code>, <code>secondteam</code>, <code>thirdteam</code> || Team names for 2v2 or 3v3