• Por favor copie e cole a mensagem de erro que aparece na tela, se possível.

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 explique o que queria fazer, o que fez e o que aconteceu

• Qual navegador você está usando?

• Por favor copie/cole o texto em inglês em vez de sua língua. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.

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 texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?

• Qual navegador você está usando?

• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.

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.

• Qual navegador você está usando?

• O que estava presente na tela quando você estava bloqueado (tela em branco? Parte da imagem do jogo? Mensagem de erro?)

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.

• Qual navegador você está usando?

• Que parte das regras não foi respeitada pela adaptação do 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.

• A violação de regras está visível na revisão do jogo? Se sim, em que número de jogada?

• Qual navegador você está usando?

• Qual era a ação de jogo que queria fazer?

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.

• O que você tentou fazer para provocar esta ação de jogo?

• O que aconteceu quando tentou fazer isto(mensagem de erro, mensagem na barra de estado do jogo)?

• Qual navegador você está usando?

• Em que passo do jogo ocorre o problema(qual era a instrução corrente do jogo)?

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.

• O que aconteceu quando tentou fazer essa ação de jogo (mensagem de erro, mensagem na barra de estado do jogo)?

• Qual navegador você está usando?

• Por favor descreva o problema de visualização. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.

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.

• Qual navegador você está usando?

• Por favor copie/cole o texto em inglês em vez de sua língua. Se tiver uma captura de ecrã/tela deste problema (boa prática), pode usar Imgur.com para carregá-la e copiar/colar o endereço aqui.

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 texto está disponível no sistema de traduções? Se sim, foi traduzido há mais de 24 horas?

• Qual navegador você está usando?

• Por favor, explique sua sugestão precisamente e de forma concisa, de forma que fique o mais fácil possível, entender o que você quer dizer.

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.

• Qual navegador você está usando?