• Prosím, zkopíruj a vlož hlášení o chybě, které vidíš na monitoru, pokud to lze.

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Prosím popiš, co jsi měl v úmyslu udělat, co jsi udělal a co se nakonec stalo

• Jaký prohlížeč používáte?

• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazovky tohoto bugu (doporučený postup), můžeš použít libovolnou službu pro hostování obrázků (například snipboard.io), nahrát ho tam a odkaz sem zkopírovat/vložit. Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?

• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?

• Co bylo zobrazeno na monitoru, když došlo k tvému zablokování? (Černá obrazovka? Část herního prostředí? Hlášení o chybě?)

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?

• Která část pravidel nebyla dodržena adaptací hry na BGA

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Je vidět porušení pravidel na záznamu hry? Pokud ano, ve kterém tahu?

• Jaký prohlížeč používáte?

• O jakou herní akci ses pokoušel/a?

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Co ses pokoušel/a udělat, abys spustil/a tuhle herní akci?

• Co se stalo, když ses o tuto akci pokusil/a (vyskočila chybová hláška, lišta ve hře, ...)?

• Jaký prohlížeč používáte?

• V jaké fázi hry problém nastal (jaký byl poslední herní pokyn)?

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Co se stalo, když ses pokusil/a udělat akci (chybová hláška, oznámení stavového řádku hry, ...)?

• Jaký prohlížeč používáte?

• Prosím popište vyobrazený problém. Pokud máš snímek obrazovky tohoto bugu (doporučený postup), můžeš použít libovolnou službu pro hostování obrázků (například snipboard.io), nahrát ho tam a odkaz sem zkopírovat/vložit.

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?

• Prosíme, zkopíruj/vlož text zobrazený v angličtině namísto tvého jazyka. Pokud máš snímek obrazovky tohoto bugu (doporučený postup), můžeš použít libovolnou službu pro hostování obrázků (například snipboard.io), nahrát ho tam a odkaz sem zkopírovat/vložit. Je tento text k dispozici v systému pro překládání? Pokud ano, byl přeložen před více než 24 hodinami?

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?

• Prosím popiš svůj návrh přesně a konzistentně, aby bylo snadné pochopit, co máš na mysli.

In real-time games, it happens quiet frequently that a player is not playing because he did not receive the notification that it is his turn to play. It also happens that the game situation is screwed at his side only because of a lost notification.
It leads to wasted games and to many bug reports on games despite the game developer can not fix them.

Ideally, lost notifications should not exist (might be done using an acknowledgment to reissue a notification to a player if it browser did not acknowledge; normally TCP is doing it automatically at a lower level, I wonder if you are in UDP), but avoiding them would probably increase the server load.

At least, a mitigation for lost your turn notifications should be implemented: if a player is not playing for a given amount of time (either fixed or computed from average time needed to play in the game, or when going negative in time but that’s might be too late to reload and play without being expelled), a special framework specific "YourTurn" notification should be sent to its browser. When the browser receive it, the framework at client side should either:
- if it was knowing that the player should play (it has received the normal your turn notification), do nothing,
- if it was not knowing that the player should play, warn the player that he must reload the page (as the normal notification can have important lost data) and show a button to do it easily.

• Jaký prohlížeč používáte?