No products in the cart.
As part of the MSO Grand Prix we will be holding several tournaments on the BoardGameArena website using their own tournament system. Using BoardGameArena allows us to hold tournaments that do not require a dedicated arbiter to organise them, allowing us to offer more tournaments for our players to play in than we otherwise could.
For anyone taking the competition seriously it is worth understanding how BoardGameArena will handle the running of the tournaments. It’s also important for all players to understand how they should behave, particularly in regard to what you can and can’t do if a player in your game runs out of time.
Hereafter BoardGameArena will be shortened to “BGA”.
BGA will determine who will play against who each round using the Swiss pairing system. In short this means that players will play against an opponent who is on the same score as themselve in the tournament that they have not played against already, so far as is possible. BGA does not track colour parity like many swiss system software’s do. Each round it will determine the pairings and then randomly decide who will be the first player. Some tournaments you might get unlucky and play 2nd a lot, other times you might get lucky.
In multiplayer games BGA will group the leading players onto board 1, the next group onto board 2 and so on. Repeated opponents are not avoided as this option can produce some very strange pairings in later rounds. Again the player order is randomised for each game.
BGA allots each player a share of the total time allowed for each game and players should always play to complete the game before their time runs out.
The way the clocks are programmed on BGA it’s possible for the clock that one player sees to be a few seconds out from what other players or BGA itself considers the timer to say. Players should therefore consider any amount of time remaining less than 10 seconds to mean they are at risk of being out of time.
BGA will automatically end a game once the total time allowed has expired in order to move on to the next round. The time allowed is usually the sum of the thinking time given to each player plus 5 minutes grace to allow time for players to join the game at the start. If a game runs out of time to complete the result will be determined based on who used the least amount of time.
In 2-Player games players should use the “skip turn of players out of time” option which will present itself if your opponent goes into negative time. This does not force an instant resignation but gives that player ~20 seconds to make a move before being resigned. If the player continues to make moves in negative time and the game is completed then the result of the game will stand. In other words, it is possible to win a game even if you have ran out of time.
If your opponent has used far more than their allotted time, you are allowed to stop making moves and wait for the total time allowed for the game to expire. If this happens and you still have more time remaining, you will be declared the winner. Be careful though as it is possible for both players to go into negative time and for the game to continue for a little while longer (as BGA allows 5 minutes plus the time on each players clocks). Do this at your own risk, if you end up with less time than your opponent it will be you that loses!
In Multiplayer games players must not use the “skip turn of players out of time” option, except for circumstances outlined below. Any player who mis-uses this option will be scored 0 points for the game (penalty applied retrospectively at the end of the tournament). This rule is in place because BGA does not allow the game to continue once a player has timed out, spoiling the result for all other players involved in the game. Players are reminded that they should not be using more than their allocated time and the MSO reserves the right to apply a penalty to players who exceed their time allowance.
Note that manually ran tournaments have a different policy as custom games can be continued after a player timed out. Please refer to the tournament specific rules in these cases (available from the event page).
Should a player disconnect from a game we ask that players are considerate towards this and give their opponent a chance to re-join and complete the game, even if the disconnect causes them to use more than their allotted time.
In multiplayer games please wait 10 minutes to allow the player a chance to re-connect to the game. If they have not been able to re-join after 10 minutes the remaining players may “skip turn of players out of time” and force the game to end. Please do ensure you’ve allowed 10 minutes, otherwise you may be penalised for dropping a player in accordance with the above rules. You are welcome to check with an administrator via Discord before you drop the player if you are unsure when it’s ok to end the game.
The MSO tiebreak system for BGA automated tournaments will be as follows:
Ties settled using Buchholz (also known as Sum of Opponents Scores). BGA will display a sum of opponents score tiebreak however in some instances this will not be correct as BGA currently doesn’t account for byes and players who have withdrawn from the tournament. The following must be added to the BGA displayed tiebreak in order to evaluate the true Buchholz tiebreak.
The purpose of these adjustments is to fairly adjust for players who were given a bye or played against players who did not play the entire tournament.
We will only re-evaluate BGA’s calculation of a buchholz tiebreak at the end of a tournament to determine medals or if the decision determines which player(s) will advance or be eliminated from the tournament. If both players are advancing and the tiebreak only affects seeding we rank players in the order given by BGA using their tiebreak calculations.
Ties settled using Buchholz (also known as Sum of Opponents Scores). BGA will display a sum of opponents score tiebreak however in some instances this will not be correct as BGA currently doesn’t account for byes and players who have withdrawn from the tournament. We will correct the tiebreak as follows: