Todos os informes
Informes de biyi_displayed
#26719: "Highlight the 4 dragons responsible for losing a game in purple"
acknowledged: Os desenvolvedores cren que é unha boa idea e teñen a intención de traballar nela
Sobre qué é este informe?
Qué aconteceu? Por favor selecciona debaixo
Suxestión: na miña opinión, esta idea pode mellorar moito a implementación do xogo
Descrición detallada
• Por favor explica a túa suxestión de maneira precisa e concisa para que sexa o máis sinxelo posible entender o que queres dicir.
When starting a turn with 4 dragons next to each other (or two groups of 2 dragons next to each other), one loses the game. This situation brings a bit of confusion among newcomers, and it may discourage some of them to continue playing the game and get better at it.• Cal é o teu navegador?
Google Chrome v86
Historial de informes
23. Out 2020 10:19 • abstrack • Esta suxestión aínda non foi analizada polos desenvolvedores:
Similarly to how the token moving on top of the opponent's biyi is highlighted in purple, when winning the game, I suggest to highlight the 4 dragons responsible for a loss.
Maybe is purple not the right color, as it is currently used to show a winning move, and not a losing condition. In any case, I think highlighting these dragons, however it is done, would highly enhance the gameplay.
Maybe is purple not the right color, as it is currently used to show a winning move, and not a losing condition. In any case, I think highlighting these dragons, however it is done, would highly enhance the gameplay.
23. Out 2020 22:43 • abstrack • Esta suxestión aínda non foi analizada polos desenvolvedores:
Actually, red is used right now to highlight connected pure dragons of the same color. It then might be more appropriate to use this color instead.
Also, in this particular case, I think the color should be displayed on the screen of both players.
Also, in this particular case, I think the color should be displayed on the screen of both players.
24. Out 2020 20:28 • Razvogor • Os desenvolvedores cren que é unha boa idea e teñen a intención de traballar nela:
We are looking to implement a solution that will also semi-solve issue #25019 at the same time right now.
Engade a este informe
Por favor engade aquí calquera cousa que sexa relevante para reproducir este erro ou entender a túa suxestión:
- Outro DI de mesa / ID de movemento
- Premer F5 resolveu o problema?
- Apareceu o problema varias veces? Tódalas veces? Aleatoriamente?
- Se tes un pantallazo deste erro (boa práctica), podes usar Imgur.com para subilo e copiar/pegar a ligazón aquí.
