Template:Tournament data: Difference between revisions

Revision as of 00:07, 19 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=
|championoutcome=
|championprevious=
|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 championoutcome to retained, transferred, or no-show. The prior champion and 1v1 event are read from the registry automatically; use reigningchampion and championprevious 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	`championoutcome`, `reigningchampion`, `championprevious`	Outcome uses `retained`, `transferred`, or `no-show`; the other fields are temporary historical overrides
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
champion — resulting champion derived from the 1v1 title outcome

@@ Line 22: / Line 22: @@
 |reigningchampion={{{reigningchampion|}}}
 |championoutcome={{{championoutcome|}}}
+|championprevious={{{championprevious|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 65: / Line 66: @@
 |reigningchampion={{{reigningchampion|}}}
 |championoutcome={{{championoutcome|}}}
+|championprevious={{{championprevious|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 108: / Line 110: @@
 |reigningchampion={{{reigningchampion|}}}
 |championoutcome={{{championoutcome|}}}
+|championprevious={{{championprevious|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 156: / Line 159: @@
 |reigningchampion={{{reigningchampion|}}}
 |championoutcome={{{championoutcome|}}}
+|championprevious={{{championprevious|}}}
 |winnerteam={{{winnerteam|}}}
 |secondteam={{{secondteam|}}}
@@ Line 204: / Line 208: @@
 |reigningchampion=
 |championoutcome=
+|championprevious=
 |winnerteam=
 |winner1=
@@ Line 224: / Line 229: @@
 </pre>
-For 1v1, use <code>winner</code>, <code>second</code>, and <code>third</code> instead of team names and member fields. Set <code>championoutcome</code> to <code>retained</code>, <code>transferred</code>, or <code>no-show</code>. The reigning champion is read from the previous 1v1 record automatically; use <code>reigningchampion</code> only while that older record is missing.
+For 1v1, use <code>winner</code>, <code>second</code>, and <code>third</code> instead of team names and member fields. Set <code>championoutcome</code> to <code>retained</code>, <code>transferred</code>, or <code>no-show</code>. The prior champion and 1v1 event are read from the registry automatically; use <code>reigningchampion</code> and <code>championprevious</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.
@@ Line 247: / Line 252: @@
 | 1v1 results || <code>winner</code>, <code>second</code>, <code>third</code> || Placed players
 |-
-| 1v1 championship || <code>championoutcome</code>, <code>reigningchampion</code> || Outcome uses <code>retained</code>, <code>transferred</code>, or <code>no-show</code>; reigning champion is an optional historical override
+| 1v1 championship || <code>championoutcome</code>, <code>reigningchampion</code>, <code>championprevious</code> || Outcome uses <code>retained</code>, <code>transferred</code>, or <code>no-show</code>; the other fields are temporary historical overrides
 |-
 | Team results || <code>winnerteam</code>, <code>secondteam</code>, <code>thirdteam</code> || Team names for 2v2 or 3v3