Follow us on Twitter @LiquipediaSC2 if you'd like to be kept up to date on all things StarCraft II!

Template:Infobox league/doc

From Liquipedia StarCraft 2 Wiki
[e][h]Julmust's awesome tournament
League Information
Start Date:
End Date:
Liquipedia tier:
Player breakdown
Number of players:

Adding an infobox to your tournament page[edit]

An Infobox is one of the standard features of any Liquipedia page and it's no different for tournaments and leagues. The {{Infobox league}}-template should come be before the article text start, but perhaps after other templates such as Tabs or Stub, and also after a banner that you'd like to add to the top. Following will be the explanation of the code, and some templates for you to use on a tournament page.

Code Explanation[edit]

{{Infobox league

This brings out the template you will be using.

|name=Julmust's awesome tournament
|organizer= Julmust

Tournament name, link to the banner (upload to LP), and name of organizer, the organizer automatically looks if ther is an LP page with that name and if it finds one it will link to it. You can add up to 4 organizers like this: organizer2 - organizer4 And they'll do the search for each one. Or you can make it into an external link. Also to note: at the moment, Name and Organizer are the only fields that will be displayed even if they are left empty.

|sponsor= [ madeupsite]
|server= EU

Either eu, na, kr, cn, tw, ru, sea, la, and eu/na for both Europe and N. America.

|type= Weekly Online

Either offline, online, or weekly online.

|format= 1v1, Single Elimination

Sponsor of the event, which server it is played on (NA, KR, etc.) the type of event (offline, online or weekly online, etc.) you should add country to offline events, or online too if it indicates which language that is used in most casts and info etc. The format variable should be a short description of the match format and the tournament format (like "1v1, Round Robin" or "Bo7 All-Kill, Double Elimination"). Country2 and city2 are for tournaments which are played out offline at two different locations (eg 2015 WCS Season 1).

|prizepool= 5000

The size of the prize pool for the tournament.

|localcurrency= EUR

The currency of the local prize pool. See Template:Local currency for a list of local currencies.

|prizepoolusd= 5000

The size of the prize pool for the tournament if prizepool is in a currency different to USD. The value can be automatically calculated, if prizepoolusd is left blank and date/edate, prizepool and localcurrency is set

|date= 2010-10-10
|sdate= 2010-10-10
|edate= 2010-10-17

Date of event or if it spans multiple days, you can instead add start and end date. Please try to use the ISO date standard (YYYY-MM-DD) with the normal "hyphen-minus" (-) as a seperator.

|liquipediatier= Minor

The tier/classification of the tournament : Premier, Major, Minor, Monthly, Weekly, Show Match
If team tournament: Premier, Major, Minor, 2v2, Show Match

|liquipediatiertype= Qualifier

The tiertype of the tournament : weekly, biweekly, monthly, charity, qualifier, 2v2, 3v3, 4v4, 1v2, archon, daily, ffa

--> |game= wol (wol, hots, lotv or mod)
|modname= will be displayed if game is set to mod
|patch= Patch 1.5.3

If the game version is set as lotv the patch can be calculated automatically if the patch parameter is left blank (or not used at all) and date/sdate is set.
You can deactivate the automated patch calculation by using |autopatch=false.

|general= true

Since StarCraft 2 is divided into 3 parts, WoL, HotS, and LotV it's a good idea to mark the tournaments to which bigger game version the tournament belonged, the colours of the infobox will also change depending on which game version is used. The patch version is even more specific than the game version making it easier for people down the ages to know what rules were in play for a specific tournament since the game does change a lot between certain patches. If the infobox isn't used for a specific tournament but rather a tournament series or an overview page for a tournament organizer, where you can't set a game or patch version, you can give general the value true to not add the tournament page to the category Category:Competitions without game or patch version.


TLPD page and official webpage for the tournament/league, add complete URLs for them to work propperly no title for the links can be given.

|player_number= 3
|protoss_number= 1
|terran_number= 1
|zerg_number= 1

Total number of players, and number for each of the indiviual races. If you've set the number of players by races it's not needed to set the player_number variable as the template will calculate the number for you if you don't. If you do not know the amount of different races in a tournament due to not all spots having been assigned put in the intended number of participants as player_number.


These are to be used for team tournaments team_number sets the number of teams playing in the league. team1 - team16 lists up to 16 possible teams, for a league with more teams than this just leave these fields blank and make a list on the page. For team tournaments it's not necessary to fill in player_number or the "race"_number variables.

|map1= Lost Temple
|map1= Kulas Ravine

Map pool of the tournament. With map1 - map15 you can add up to 15 maps. They will be linked automatically but if you want show a different name than the one that will be linked, you can use the | template in this fashion "LINKNAME|SHOWN NAME".
If the tournament has two map pools there's a second set of 15 map variables 2map1 - 2map15 that can be used. There is also the option to change the titles for the map pool lists with maptitle and 2maptitle or they'll be set to their default "Maps" and "2v2 Maps" respectively.


Links to the previous and next editions of the serie/tournament.


Ends the use of the template, without this the template will not work.

Copy & Paste Templates[edit]

You'll find three templates and a full variables list below. Chose the one that suits your needs the best.

NOTE: After you've entered all the information you have, do not add: 0, N/A, TBD etc. to empty variable fields, instead it is oftentimes best to just remove the empty ones, unless you know this information will be coming in the future but then you can just leave the fields blank.