#140841: "Make completed orders visible"

• Por favor, copia e pega a mensaxe de erro que ves na túa pantalla, se houbera algún.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Por favor, explica o que querías facer, o que fixeche e o que pasou
• Cal é o teu navegador?
Google Chrome v129

• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes un pantallazo deste erro (boa práctica), podes usar Imgur.com para subilo e copiar/pegar a ligazón aquí.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
• Cal é o teu navegador?
Google Chrome v129

• 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.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Cal é o teu navegador?
Google Chrome v129

• Qué había na pantalla cando se quedou bloqueado? (mensaxe de erro?, pantalla en blanco?, unha parte da interface do xogo?)
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Cal é o teu navegador?
Google Chrome v129

• Qué parte das regras non se cumpriron na adaptación da BGA?
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• é visible a violación das regras na repetición? Se o é, en que número de movemento?
• Cal é o teu navegador?
Google Chrome v129

• Qué acción de xogo querías realizar?
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Qué é o que tratache de facer para activar esta acción do xogo?
• Qué sucedeu cando o fixeche (a mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
• Cal é o teu navegador?
Google Chrome v129

• En que paso do xogo ocorreu o problema (cal foi a instrucción actual do xogo)?
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Qué sucedeu cando tratache de facer unha acción de xogo (mensaxe de erro, mensaxe na barra de estado do xogo, ...)?
• Cal é o teu navegador?
Google Chrome v129

• Por favor, describe o problema de visualización. Se tes un pantallazo deste erro (boa práctica), podes usar Imgur.com para subilo e copiar/pegar a ligazón aquí.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Cal é o teu navegador?
Google Chrome v129

• Por favor, copia/pega o texto amosado en inglés no canto do teu idioma. Se tes un pantallazo deste erro (boa práctica), podes usar Imgur.com para subilo e copiar/pegar a ligazón aquí.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• É este o texto dispoñible no sistema de tradución? Se é así, foi traducido fai máis de 24 horas?
• Cal é o teu navegador?
Google Chrome v129

• 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.
The published rules for this game say that after deliveries are made, order cards should be turned face down. Hiding known information is an okay mechanic when playing around a table in real life, but it falls apart when playing online asynchronously (especially if you have more than one game in progress).

It's made even worse in asynchronous games because deliveries happen on other players' turns and are not reported in the gamelog, so the only way to find out what happened is either to keep copious notes on all the open orders players have and note the changes, or go back through the replay (which is always a fraught process on BGA, probably because of the load it puts on the server).

(For example, table 567892127 is on move 162. When I tried to do a replay from turn 17 (when an delivery was made), the screen displays the "Previously on..." message and then stops. I've had similar problems on other games, so I doubt this is an issue with the Coal Baron implementation.)

Though this is less of an issue playing playing live online, players can very easily take notes, and now, instead of a test of "memory", it's an advantage of players who have extra screen space and enjoy note-taking.
• Cal é o teu navegador?
Google Chrome v129

Sobre qué é este informe?

Qué aconteceu? Por favor selecciona debaixo

Qué aconteceu? Por favor selecciona debaixo

Por favor revisa se xa hai un informe sobre o mesmo tema

Descrición detallada

Historial de informes

Engade a este informe

Cambiar o estado do informe a:

Axuda

Contribuir

Síguenos