Dashboard Glossary

Give this tournament template a name - this can be anything.

Select a type for the tournament. This will help you to organize your templates - you will be able to see an indicator for the type of tournament when viewing your list of tournament templates.

There are four types:

• Public - Anyone is be able to enter the tournament
• Premium - Players should pay an entry fee before entering or own premium pass
• Private - Invite only
• Testing - For testing (it is recommended that you create a test tournament initially. You can always change/update the type late once you're happy with what you've set up)

DELETE - Don't press this unless you have a really good reason to as it will permanently delete your template!

Change the selected language

Specify the name of the tournament. This should be something cool as this will be displayed to players in the tournaemtn list.

Provide the URL of the icon that will be displayed to players for this tournament.

Provide the URL of the image that will be shown to players to represent this tournament.

Specify a theme color that will be used. This color can be picked up through the in game SDK and used to change the visuals/highlight items in your game UI for this tournament.

Provide a brief description of the tournament that will be shown to players. You can also use this to explain the rules of the tournaments or advertise the prizepool a bit more.

Provide some additional information about the tournament.

Select how long before a tournament you want players to be able to register. Options:

• Immediately
• 2 weeks before start
• 1 week before start
• 2 days before start
• 12 hours before start
• 2 hours before start
• 1 hour before start

For invitation-only or high-value tournaments, allow longer registration periods. Public tournaments should have shorter registration periods as players tend to register right up until the tournament starts.

Select how long before a tournament you want to close registration. Options:

• 2 minutes before start
• 2 hours before start
• 12 hours before start
• 1 day before start
• 2 days before start
• 1 week before start

For invitation-only or high-value tournaments, allow longer registration periods. Public tournaments should have shorter periods. Ensure the registration open and close settings are compatible.

Specify the maximum number of players for the tournament. Use lower numbers (e.g., 32, 64, 128, 256) for high-value or streamed tournaments to keep them elite and manageable. Tournament SDK handles situations when the maximum number of players is not met or some players don't show up. The maximum number may also depend on the tournament format.

Specify the number of players per team, determined by the game type.

Make the tournament available to all players with no restrictions. Specify when players can register:

• Immediately
• 1 hour after registration opens
• 2 hours after registration opens
• 12 hours after registration opens
• 1 day after registration opens
• 2 days after registration opens
• 1 week after registration opens

Invite a specific list of players. Specify when they can register. Options are the same as above. Add players by clicking "add user" and searching for them.

Invite only players with a private code. Specify when they can register. Options are the same as above. The private code is generated when the tournament is scheduled. Public tournaments require a private code for registration, which can be shared via social platforms or influencers. Private tournaments remain hidden unless the player has the code.

Invite players successful in previous tournaments. Specify when they can register. Options are the same as above.

• Number of Invites: Set the maximum number of invites.
• Invite based on item [ID]: Send invites to players who have won a specific item (e.g., virtual tournament chip). The system will look for players with this item.
• Add Tournaments: Search for tournaments within a date range and add them.
• Best score from [Number] of results: Prioritize invites based on the best scores from a set number of tournaments, encouraging players to participate more to improve their scores.

Invite players successful in a particular tournament series. Specify when they can register. Options are the same as above.

• Number of Invites: Set the maximum number of invites.
• Invite based on item [ID]: Send invites to players who have won a specific item.
• Add Tournaments: Search for tournaments within a date range and add them.
• Best score from [Number] of results: Prioritize invites based on the best scores from a set number of tournaments in the series, encouraging participation.

Enable or disable registration rules. "Enabled" appears in green when active. Hover over "enabled" to see "disable" in red, and click to disable the rule.

Specify the number of teams that will be in this phase.

Specify the minimum number of teams that will play in a match. You'll need to set this (as appropriate) for your type of game.

Specify the maximum number of teams that can play in a match. You'll need to set this (as appropriate) for your type of game (and may be the same as the minimum number).

Specify the maximum number of losses a player/team can have (i.e. if you lose more than this number of games, then you're automatically out). In team games, it is possible to have multiple winners so a "loss" is any game when a player doesn't score any match points. In a bracket phase, "max losses" is pre-set to "1" (i.e. lose and you're out) so this setting is not shown.

Click on the "show advanced settings" link to show these. By default, these settings are automatically set. The settings define how to award points to players who finish in certain positions within a game and/or match, you might want to alter these if each game/match has large numbers of players.

This is specified as a comma-delimited list. In a head-to-head game, this value will be set to "1" i.e. 1 point is awarded to the winner of a game. In a more complex scenario (i.e., battle royale type game), you may choose to give 5 points to the winner of a game, 2 points to the runner-up, and 1 point each to the 3rd-5th placed finishers. This would be specified as follows: 5,2,1,1,1.

When all the games in a match have been played, the platform will rank players based on the number of points awarded across all games. Match points will then be awarded according to the ranked order (i.e. anyone who is categorized as a "winner" will get at least one match point so, if your top 3 players are "winners", you might specify the match point distribution as: 3,2,1). The awarding of match points will determine if players progress to future rounds and, in an arena, who they are matched against.

You must select how each round (match) will be decided. There are options for Best Of (BO) 1-5 (i.e. how many games should the players/teams play against each other to determine the winner of their match). There is also an option for "Custom". If you select this item you must also enter:

• Score to Win - the score that a player/team requires to win the match
• Maximum number of games - the maximum number of games that the teams can play

Enter the minimum amount of time that a game will take to be played. This setting helps to ensure that players will get to play all of the games in an individual round. I.e. if the first game in a best of 3 lasts for a long time, messages can be sent through SDK to kill/end the first game to allow time for subsequent, minimum length, games to be played.

To ensure the tournament is over in a manageable time, specify the maximum duration for each round. This must be more than the sum of the minimum times of the games in the round. When you're setting this you should think about the number of games in a round, the minimum (and average) length of a game and then think about (potentially) adding an appropriate safety margin (i.e. in your game, a typical gameplay session might last between 1 and 3(ish) minutes). You would specify the minimum game time as 1. Then, if your round/match was the best of 3 games, you might specify the maximum round time as 9 minutes (2 mins average game time * 3 games + 3 minutes buffer/safety margin).

Remember that all matches in a round must be completed before the next round can begin so you may have some players who complete their match early and then have time when they are waiting for their next match to begin. Whilst there is no exact science, it's important to consider this carefully and set an appropriate limit.

Phase tiebreakers are always resolved. At the end of each phase players are sorted according to these stats:

• Points - higher is better - accumulated from winning match points (rounds)
• Match wins - higher is better - accumulated from winning matches (rounds)
• Match losses - lower is better - accumulated from losing matches (rounds)
• Game wins - higher is better - accumulated from winning games (in each match)
• Game losses - lower is better - accumulated from losing games (in each match)
• Tiebreaker stat 1 (optional) - accumulated from played games
• Tiebreaker stat 2 (optional) - accumulated from played games
• Phase seed - lower is better - final position from the previous phase
• Lose weight - lower is better - accumulated from losing matches and weight increases with each round

You may specify two custom tiebreaker stats to be used to break the tie. For example (depending on your game): most kills, furthest distance traveled, total goals scored, etc. This must be passed by the game through the SDK, statistics will be set up in the "Game settings, Statistics" section (see below).

Tick this box if you want to resolve match tiebreakers. This is only used in scenarios where you set up a round to be the "Best of" an even number of games - in this scenario, you may specify another statistic to be used to break the tie. For example (depending on your game): most kills, furthest distance traveled, total goals scored, etc. This must be passed by the game through the SDK, statistics will be set up in the "Game settings, Statistics" section (see below).

In case of a tiebreaker, the match points are split between all teams that occupy tiebreaker positions. For example, if 2 teams finish with the same amount of game points in a match and they tiebreak for 2 match points then the points are split equally between them so each gets 1 match point.

You should always resolve tiebreakers in a bracket phase or you run the risk of a random player being put through to the next round.