All reports
Troyes reports
#22589: "Cube and meeple colors for the white/beige player and the neutral player should be consistent"
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.
The white player has their player name written in white, and their cubes are white, BUT their disc in the middle of the game board is beige, and their meeples are beige.
The neutral player has a light grey disc on the board which matches their meeple color, but their cubes are a darker grey. The light grey color of the disc and meeples is pretty close to being white.
My suggestion is to make the colors consistent for both the white/beige player and the neutral player.
Specifically, I would suggest making the player color be beige, and changing their cubes and player name to be displayed in beige. And I would suggest making the neutral player be dark grey (making their meeples also be this color).• Which browser are you using?
Google Chrome v84
Report history
Aug 13th 2020 23:42 • mitcharf • This suggestion has not been analyzed by the developers yet:
The color confusion has led to one player thinking the game had scored the cathedral incorrectly (see zoid4's report in this bug: boardgamearena.com/bug?id=17879)
Feb 23rd 2021 20:48 • Geddy19 • This suggestion has not been analyzed by the developers yet:
Yes my group is encountering this now at table #145855433 and it's definitely a problem. Very confusing.
May 26th 2022 14:19 • der-spieler • This suggestion has not been analyzed by the developers yet:
This bug is open for quit some time now. It would be appreciated if this gets improved. The color inconsitency is very confusing for new players. It wouldn't be too much effort to change this.
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.
