Getting started
The tournament feature allows anyone to create and manage Tournaments, from registration process to scoring and tournament Tree systems.
How does Tournaments work?
While configuring their tournaments, users are able to set the registrations start and end date,
the tournament's start and end date, and more configurations depending on their needs (teams min and
max size to register, registrations rules, what kind of tournament it is, is it public, ...).
After setting these configurations, the tournament can begin.
First, the tournament will open registrations when the start registrations date is reached.
Registrations will stay open until the end registrations date is reached. When this date is reached
and until the start tournament date is reached, the tournament will be in a inactive state.
Then, when the start tournament date is reached, the tournament will begin by setting the first
step as active. If automation settings are set, the step will be automatically generated and
seeded if needed. Tournament creators can also choose to generate and seed their steps themselves.
Tournament admins can now update game matches to set the current score for each team participating
in the tournament. When all steps groups have finished their matches, the step will be closed and
the next step is opened. By using automation rules, the Tournament creator, can set options to
automatically generate and seed the next step with the current winning (or loosing) teams.
Player Registrations
The player registrations process starts when reaching the start registrations date.
At this point, any player will be able to create his team to register to the Tournament. If it has
a valid team (depending on the tournament configurations) and all the team members met the
registration rules, the team will be automatically set to either awaiting for manual validation or
validated as participant to the tournament.
The manual validation state requires a manual validation of the team by a Tournament admin.
Registration rules​
Registration rules are a specific configuration part that can be enabled to provide very flexible
rules that users must meet to register to the tournament.
The requirements can range from player profile properties values set on a player profile to
having a specific external account linked to their player profile.
For example, it is possible to create a registration rule that requires that the player has
a League Of Legends account linked with, at least, a Diamond rank and/or a Twitch channel with a follower
count of 1,000.
The goal here is to provide the most flexible way to easily set registration requirements without
having to validate each teams manually.
Steps
Step represents each steps of a tournament. For example, you can create a Round robin step for
your qualifications, then create an Elimination Tree step for your Playoffs.
Steps can be linked together using automation or can be manually seeded. It is important to remember
that each Step is independent of each other and only automation rules, or manual seeding will
result in updating the Step participating teams.
There are currently 4 steps types available:
- Round-Robin groups
- Scoring FFA
- Tournament Trees (Single and double elimination)
- Custom
Custom steps​
Custom steps allows you to create your own custom configuration for a step.
This means that you will be able to create your own games and matches, and provide automation steps
to define how winning and losing teams are managed.
This is longer to create and harder to maintain, but allows you to completely decide how your
step is executed.
Groups
Group defines multiple team groups that will be able to match against each others.
For example, in a Round-Robin system, it will define each pool of teams that will match against
each others. In a Tree setting, each group represent a tournament tree, for example, for a double
elimination tree, there are two distinct groups, the initial tree and the loosing tree, players
that loses games are redirected through the loosing tree.
Automation rules can be added to groups to define what to do if a team loses or win its games.
Groups also defines how many teams are declared winners, and if they need to be seeded to another
group/step.
The same can be made with loosing teams.
Rounds
Each round represents an internal step for groups. It is typically the next games set for a
team or defines an important moment during the step (for example, switching to another game).
Typically, Rounds are used to generate the tournament tree, by defining where are currently the
players in the Group (semi finals, finals, ...).
Games
A game is composed of multiple Matches and defines which teams are getting against each others.
The game is typically defined by the maximum number of winning matches needed to define a winning team.
When the threshold of wined matches is reached, and the number of winning teams required to end
the game is reached, the game is set as ENDED and teams are transferred to other games depending
on their winning status.
Matches
A match represents the result of a in-game confrontation. It typically contains the current teams
scores and some variables (either to help for score calculations, or to show on the tournament page,
ex: kill count, golds won, ...).
A match is considered ended when all the teams that are participating in this match have a match
status set (either winner or loser).