• Venligst kopier/indsæt fejlmeddelelsen du ser på din skærm, hvis der er en.

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.

• Venligst forklar hvad du ønsker at gøre, hvad du gjorde og hvad der skete

• Hvilken browser bruger du?

• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.

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.

• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?

• Hvilken browser bruger du?

• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.

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.

• Hvilken browser bruger du?

• Hvad blev der vist på skærmen, da du blev blokeret (Blank skærm? Noget af spilbrugerfladen? Fejlmeddelelse?)

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.

• Hvilken browser bruger du?

• Hvilken del af reglerne blev ikke respekteret ved BGA-tilpasningen

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.

• Er regel-brudddet synligt i e

• Hvilken browser bruger du?

• Hvad var den spilhandling du ønskede at udføre?

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.

• Hvad forsøgte du at gøre for at udløse denne spilhandling?

• Hvad skete der, da du forsøgre at gøre dette (fejlmeddelelse, meddelelsesstatusbjælke, ...)?

• Hvilken browser bruger du?

• I hvilket stadie af spillet opstod problemet (hvad var den daværende spilinstruktion)?

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.

• Hvad skete der, da du forsøgte at udføre denne spilhandling (fejlmeddelelse, meddelelsesstatusbjælke, ...)?

• Hvilken browser bruger du?

• Venligst beskriv display problemet. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.

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.

• Hvilken browser bruger du?

• Venligst kopier/indsæt tekst vist på engelsk i stedet for dit sprog. Hvis du har et skærmbillede af denne fejl (god øvelse), kan du bruge Imgur.com til at uploade den og kopiere/indsætte linket her.

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.

• er der adgang til denne tekst i oversættelsessystem? Hvis ja, er det blevet oversat inden for 24 timer?

• Hvilken browser bruger du?

• Forklar venligst dit forslag præcist og sammenfattende, så det er så let som muligt at forstå, hvad du mener.

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.

• Hvilken browser bruger du?