All reports
Coloretto reports
#109470: "unfair game; poor design"
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.
your game is soo bad:
your game gives lower elo players unfair disatvantage that would never happen in real time game. I just played a game (and it happened in other games often as well) where a player with 3s and 4s spots on the board had 2x more rolls of 3s and 4s than the players with 6s and 8s. Unfair, poor design and absolutely frustrating to play. You should consider improving the game. I would also like a return of my premium membership since I don't wish to be part of this community.
Thanks• Which browser are you using?
Safari v16
Report history
dudaa123 • This suggestion has not been analyzed by the developers yet:
Jan 4th 2024 11:29 • your game is soo bad:
your game gives lower elo players unfair disatvantage that would never happen in real time game. I just played a game (and it happened in other games often as well) where a player with 3s and 4s spots on the board had 2x more rolls of 3s and 4s than the players with 6s and 8s. Unfair, poor design and absolutely frustrating to play. You should consider improving the game. I would also like a return of my premium membership since I don't wish to be part of this community.
Thanks
your game gives lower elo players unfair disatvantage that would never happen in real time game. I just played a game (and it happened in other games often as well) where a player with 3s and 4s spots on the board had 2x more rolls of 3s and 4s than the players with 6s and 8s. Unfair, poor design and absolutely frustrating to play. You should consider improving the game. I would also like a return of my premium membership since I don't wish to be part of this community.
Thanks
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.