Template:Tournament data

Purpose

This is the dispatcher for the tournament single-source system. Each festival has one named record, for example Template:Tournament data/Riverside I, and its article contains only:

{{Tournament data/Riverside I}}

Editing that record updates the article, infobox, prose, chronology, categories and Tournaments together

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=
|render={{{render|article}}}
}}</includeonly>

For 1v1 results use winner, second and third. For team events, team names are optional but member fields are required. To record two joint third-place finishers, put the second player or team in jointthird, jointthirdteam and the matching member fields

If one festival contains a second bracket, keep one record and repeat event fields with the event2 prefix, such as event2date, event2format, event2winnerteam and event2winner1. Shared festival details such as host, runners, image and forums post stay unprefixed

For the 1v1 champion title use championoutcome as established, retained, transferred or no-show, and put the resulting title holder in champion. Incoming champions and prior tournaments are resolved automatically

Parameters

Group	Parameters
Festival	name, image, type, host, continent
Event	date, format, mode, challonge
Links	post, youtube, youtube2, youtube3 and matching label/explicit fields
Runners	runner1-runner6
Podium	winner/winnerteam, second/secondteam, third/thirdteam, jointthird/jointthirdteam and member fields 1-3
Champion	champion, championoutcome; reigningchampion is an exceptional override
Second event	Any event or result field above prefixed with event2
Chronology overrides	previous, next, townprevious, townnext