• Si us plau, copia i enganxa el missatge d'error que veus a la pantalla, si és que n'hi ha algun.

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.

• Si us plau, què volies fer, què vas fer i que va succeir

• Quin és el meu navegador?

• Si us plau, copieu/enganxeu el text mostrat en anglès en comptes del teu idioma. 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. És aquest text disponible al sistema de traducció? Si és així, ha sigut traduït fa més de 24 hores?

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.

• Quin és el meu navegador?

• Si us plau, expliqueu el vostre suggeriment de manera precisa i concisa, per que sigui el més fàcil d'entendre possible.

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.

• Quin és el meu navegador?

• Què es mostrava a la pantalla quan estaves bloquejat (pantalla en blanc? Part de la interfície del joc? Missatge d'error?)

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.

• Quin és el meu navegador?

• Quina part de les regles no s'han respectat per l'adaptació de 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.

• És visible la violació de les normes durant la repetició de la partida? Si es així, en quin número de moviment?

• Quin és el meu navegador?

• Quina va ser l'acció del joc que volies fer?

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.

• Què intentes fer per dur a terme aquesta acció del joc?

• Què va passar quan ho vas intentar fer (missatge d'error, missatge de la barra d'estat de la partida, ...)?

• Quin és el meu navegador?

• A quina fase del joc va passar l'error (quina era la ordre en curs)?

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.

• Què va passar quan vas intentar dur a terme l'acció del joc (missatge d'error, missatge de la barra d'estat del joc, ...)?

• Quin és el meu navegador?

• Si us plau, descriviu el problema de visualització. 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.

• Quin és el meu navegador?

• Si us plau, copieu/enganxeu el text mostrat en anglès en comptes del teu idioma. 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. És aquest text disponible al sistema de traducció? Si és així, ha sigut traduït fa més de 24 hores?

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.

• Quin és el meu navegador?

• Si us plau, expliqueu el vostre suggeriment de manera precisa i concisa, per que sigui el més fàcil d'entendre possible.

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.

• Quin és el meu navegador?