• Будь ласка, скопіюйте/вставте повідомлення про помилку, якщо ви бачите якесь на своєму екрані.

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Будь ласка, опишіть, що ви намагалися зробити, що зробили, та що трапилось

• Який у вас браузер?

• Будь ласка, скопіюйте/вставте текст відображений англійською замість вашої мови. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Чи цей текст доступний у системі перекладів? Якщо так, то чи перекладали його понад 24 години тому?

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?

• Будь ласка, поясніть вашу пропозицію точно й лаконічно, щоб було якомога легше зрозуміти, що ви маєте на увазі.

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?

• Що було на екрані до того, як ваша гра заблокувалася (Порожній екран? Частина ігрового інтерфейсу? Повідомлення про помилку?)

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?

• Які саме правила були порушені адаптацією гри на BGA

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Чи видні порушення правил на повторі гри? Якщо так, на якому кроці?

• Який у вас браузер?

• Яку ігрову дію ви намагалися виконати?

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Що ви намагались зробити, щоб активувати цю ігрову дію?

• Що сталося, коли Ви намагалися виконати цю дію (текст помилки, статус на панелі повідомлень, ...)?

• Який у вас браузер?

• На якому етапі гри виникла проблема (яка була на той момент вказівка в грі)?

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Що стається, коли ви намагаєтесь зробити ігрову дію (повідомлення про помилку, повідомлення на панелі статусу гри і т.п.)?

• Який у вас браузер?

• Будь ласка, опишіть візуальну помилку. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here.

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?

• Будь ласка, скопіюйте/вставте текст відображений англійською замість вашої мови. If you have a screenshot of this bug (good practice), you can use a picture hosting service of your choice (snipboard.io for example) to upload it and copy/paste the link here. Чи цей текст доступний у системі перекладів? Якщо так, то чи перекладали його понад 24 години тому?

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?

• Будь ласка, поясніть вашу пропозицію точно й лаконічно, щоб було якомога легше зрозуміти, що ви маєте на увазі.

This is between a suggestion and a bug.

As per the rules, players 2 to 6 are supposed to make their choice simultaneously and they add that if some people want to wait and see what the others are doing, then people should play in turn order.

I think that the best way to enforce simultaneity is to do as for Railroad Ink and make it so that you cannot see what other players (2 to 6) have done this round (both in log and by looking at their sheet, both before and after F5) until you have done your own round.

( And ensure that you don't get problems as in "It's a wonderful world" where players are interrupted in their actions and get weird refreshes when someone else is playing their turn. )

This kind of simultaneity usually requires some work on the architecture of the code and is best done (or at least foreseen) early in the development.

• Який у вас браузер?