All reports
#31816: "Non elimination tournaments results:tiebreaks should be based on head-to-head results where possible"
What is this report about?
BGA website
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the website
Detailed description
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Currently ties at the end of round robin (& Swiss) tournaments appear to be broken by how long a person has had a BGA account.
• What is your browser?
Google Chrome v87
Report history
13. Jan 2021 12:15 • eddiec • This suggestion has not been analyzed by delopers yet:
10. May 2021 11:37 • thoun • This suggestion has not been analyzed by delopers yet:
Or maybe we play a new game when there is a tie in a turnament
10. May 2021 20:55 • twenty9oh7 • This suggestion has not been analyzed by delopers yet:
I like thoun's idea
4. Nov 2022 3:17 • Mathew5000 • This suggestion has not been analyzed by delopers yet:
But what about three-way ties with non-transitive results (e.g. A won against B, who won against C, who won against A)?
18. Nov 2024 23:00 • BananaHarambe • This suggestion has not been analyzed by delopers yet:
For Round Robin Stage tiebreakers, 1st breaker should be head-to-head.
After head-to-head there should be a penalty to losses that were timeout rather than completed. Whoever has less timeout loss wins breaker.
Final breaker should be score difference, as currently implemented, but have any players that lost on timeout highly penalized because it could be considered as "cheating" to optimize the score difference by losing by only 1 instead of by 20 for example.
After head-to-head there should be a penalty to losses that were timeout rather than completed. Whoever has less timeout loss wins breaker.
Final breaker should be score difference, as currently implemented, but have any players that lost on timeout highly penalized because it could be considered as "cheating" to optimize the score difference by losing by only 1 instead of by 20 for example.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
