• Please copy/paste the error message you see on your screen, if applicable.

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.

• Please explain what you wanted to do, what you did and what happened

• Which browser are you using?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com 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.

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• Which browser are you using?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

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.

• Which browser are you using?

• What was displayed on the screen when you were blocked (Blank screen? Part of the game interface? Error message?)

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.

• Which browser are you using?

• Which part of the rules was not followed by the BGA adaptation?

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.

• Is the rules violation visible on game replay? If yes, at which move number?

• Which browser are you using?

• What was the game action you wanted to do?

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.

• What did you try to do to trigger this game action?

• What happened when you tried to do this (error message, game status bar message, ...)?

• Which browser are you using?

• At which step of the game did the problem occur? What was the current game instruction?

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.

• What happened when you tried to do this game action (error message, game status bar message, ...)?

• Which browser are you using?

• Please describe the display issue. If you have a screenshot of this bug (good practice), you can use Imgur.com 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.

• Which browser are you using?

• Please copy/paste the text displayed in English instead of your language. If you have a screenshot of this bug (good practice), you can use Imgur.com 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.

• Is this text available in the translation system? If yes, has it been translated for more than 24 hours?

• Which browser are you using?

• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.

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.

• Which browser are you using?