• Merci de copier-coller le message d'erreur qui s'affiche à l'écran, s'il y a lieu.

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.

• Veuillez expliquer ce que vous vouliez faire, ce que vous avez fait et ce qu'il s'est passé

• Quel est votre navigateur ?

• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une impression écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour l'uploader et copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?

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.

• Quel est votre navigateur ?

• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.

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.

• Quel est votre navigateur ?

• Qu'affichait l'écran lorsque vous avez été bloqué(e) (Un écran vierge ? Une partie de l'interface du jeu ? Un message d'erreur ?)

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.

• Quel est votre navigateur ?

• Quelle partie des règles n'a pas été respectée par l'adaptation 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.

• La violation de règle est-elle visible dans le replay de la partie ? Si oui, à quel numéro de coup ?

• Quel est votre navigateur ?

• Quelle action de jeu vouliez-vous faire ?

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'avez-vous essayé de faire pour déclencher cette action de jeu ?

• Que s'est-il passé lorsque vous avez essayé de faire cela (message d'erreur, message dans la barre d'état du jeu...) ?

• Quel est votre navigateur ?

• À quelle étape de la partie le problème est-il apparu ? Quelles instructions le jeu affichait-il ?

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.

• Que s'est-il passé lorsque vous avez essayé de faire cette action de jeu (message d'erreur, message dans la barre d'état du jeu...) ?

• Quel est votre navigateur ?

• Veuillez décrire le problème d'affichage. Si vous disposez d'une impression écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour l'uploader et copier/coller le lien ici.

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.

• Quel est votre navigateur ?

• SVP copiez / collez ici le texte affiché en anglais au lieu de votre langue. Si vous disposez d'une impression écran du bug (bonne pratique), vous pouvez utiliser le service d'hébergement de votre choix (snipboard.io par exemple) pour l'uploader et copier/coller le lien ici. Ce texte est-il disponible dans le système de traduction ? Si oui, a-t-il été traduit depuis plus de 24 heures ?

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.

• Quel est votre navigateur ?

• Merci d'expliquer votre suggestion de manière précise et concise, de façon à ce qu'il soit aussi simple que possible de comprendre ce que vous voulez dire.

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.

• Quel est votre navigateur ?