All reports
Quantum reports
#29855: "Insertion of a "time limit or shifts" to prevent the game from taking too long."
implemented: This suggestion has been implemented
7
What is this report about?
What happened? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
Quantum's problem is game length.
Especially if the players are good, it can take hours for a player to place all his cubes and win the game.
The idea is therefore to insert a "time or turn limit", so that when it is reached, the player in advantage automatically wins (or, if there is still a tie, the first to take the lead from that moment ).
This "time or turn limit" could be chosen as an option to choose when creating the game table.• Which browser are you using?
Opera browser
Report history
Dec 11th 2020 13:00 • 7456786 • This suggestion has not been analyzed by the developers yet:
nothing else
Dec 28th 2020 12:33 • ALA----IN • This suggestion has not been analyzed by the developers yet:
I confirm that it would be better to fix this problem.
Nov 23rd 2022 13:49 • ALA_IN • This suggestion has not been analyzed by the developers yet:
I confirm what is written above
Apr 29th 2023 12:15 • CraWleR • This suggestion has been implemented:
Unless you're playing with friends, you cannot even create a game without time limits. Therefore, BGA already has built in functionality for it and I doubt Quantum needs anything extra or special for it. I understand that it can be abused sometimes to delay the end of the game and that it can be frustrating, but this would always be a problem unless we started some sort of "committee" to start reviewing games and deciding when these things are being abused and when they are not. Therefore, marking this as "Implemented", because technically you already need to make a choice for time limits when creating a table.
Add to this report
Please add here anything that seems relevant in order to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appear several times? Every time? 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.
