#140841: "Make completed orders visible"

• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.
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.
• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete
• Hvilken browser bruger du?
Google Chrome v129

• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Google Chrome v129

• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v129

• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)
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.
• Hvilken browser bruger du?
Google Chrome v129

• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen
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.
• Er regel-brudddet synligt i e
• Hvilken browser bruger du?
Google Chrome v129

• Hvad var den spilhandling du ønskede at udføre?
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.
• Hvad forsøgte du at gøre for at udløse denne spilhandling?
• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v129

• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?
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.
• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?
• Hvilken browser bruger du?
Google Chrome v129

• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
• Hvilken browser bruger du?
Google Chrome v129

• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.
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.
• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?
• Hvilken browser bruger du?
Google Chrome v129

• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.
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.
• Hvilken browser bruger du?
Google Chrome v129

Hvad handler denne rapport om?

Hvad skete der? Vær venlig og vælg nedenunder

Hvad skete der? Vær venlig og vælg nedenunder

Vær sød at undersøge, om der allerede er sendt en besked om emnet

Detaljeret beskrivelse

Rapporthistorik

Tilføj noget til denne rapport

skift rapport status til:

Hjælp

Bidrag

Følg os