#140841: "Make completed orders visible"

• Kopioi/liitä virheilmoitus näytöltäsi, jos sait sellaisen.
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.
• Selitä mitä halusit tehdä, mitä teit ja mitä tapahtui
• Mikä on selaimesi?
Google Chrome v129

• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähä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.
• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Google Chrome v129

• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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.
• Mikä on selaimesi?
Google Chrome v129

• Mitä näytöllä näkyi kun olit estettynä (Tyhjä ruutu? Osa pelin käyttöliittymästä? Virheilmoitus?)
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.
• Mikä on selaimesi?
Google Chrome v129

• Mitä osaa säännöistä BGA:n sovellus ei noudattanut
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.
• Onko sääntörikkomus nähtävillä pelin toistossa? Jos kyllä, mikä on siirron numero?
• Mikä on selaimesi?
Google Chrome v129

• Minkä pelin toiminnon halusit suorittaa?
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.
• Mitä yritit tehdä tämän pelitoiminnon käynnistymiseksi?
• Mitä tapahtui kun yritit tehdä tämän (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Google Chrome v129

• Missä vaiheessa peliä ongelma ilmeni (mikä oli silloinen pelin ohje)?
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.
• Mitä tapahtui kun yritit tehdä tämän pelin toiminnon (virheilmoitus, pelin tilapalkin viesti, ...)?
• Mikä on selaimesi?
Google Chrome v129

• Kuvaile näyttöongelmaa. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähä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.
• Mikä on selaimesi?
Google Chrome v129

• Ole hyvä ja kopioi teksti englanniksi oman kielesi sijasta. Jos sinulla on kuvankaappaus tästä bugista, voit käyttää Imgur.com:a sen lähettämiseksi. Kopioi ja liitä linkki tähä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.
• Onko tämä teksti saatavilla käännösjärjestelmässä? Jos on, onko sen käännöksestä yli 24 tuntia?
• Mikä on selaimesi?
Google Chrome v129

• Selitä ehdotuksesti tarkasti ja ytimekkäästi, jotta se on ymmärrettävissä niin helposti kuin mahdollista.
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.
• Mikä on selaimesi?
Google Chrome v129

Mitä tämä raportti koskee?

Mitä tapahtui? Valitse alta

Mitä tapahtui? Valitse alta

Ennen ilmoituksen tekoa, tarkista onko sellainen jo olemassa samasta aiheesta

Tarkka kuvaus

Raportin historia

Lisää jotain tähän raporttiin

Vaihda raportin tilanne:

Ohje

Tue

Seuraa meitä