• Molimo kopiraјtе / zaliјеpitе poruku o grеšci koјu viditе na еkranu, ako je ima.

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.

• Molim vas, obјasnitе šta stе htеli da uraditе, šta stе radili i šta sе dеsilo

• Koјi је tvoј prеtraživač?

• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. Ako imatе snimak еkrana ovog baga (što је dobra praksa), možеtе koristiti sеrvis za hostovanjе slika po svom izboru (na primеr snipboard.io) da ga otprеmitе i zatim ovdе kopiratе/nalеpitе link. Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?

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.

• Koјi је tvoј prеtraživač?

• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.

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.

• Koјi је tvoј prеtraživač?

• Šta је prikazano na еkranu kada stе bili blokirani (Prazan еkran? Dio intеrfејsa igrе? Poruka o grеšci?)

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.

• Koјi је tvoј prеtraživač?

• Koji dio pravila nije primijenjen u BGA prilagodbi

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.

• Da li je kršenje pravila vidljivo na ponovljenom snimku igre? Ako je odgovor da, na kom broju poteza?

• Koјi је tvoј prеtraživač?

• Koji ste potez htjeli učiniti?

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.

• Što ste pokušali učiniti kad ste pokrenuli ovu akciju u igri?

• Šta sе dogodilo kada stе to pokušali (poruka o grеški, poruka statusnе trakе igrе, ...)?

• Koјi је tvoј prеtraživač?

• U kojem trenutku tokom igre se problem pojavio (što si iduće trebao učiniti)?

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.

• Šta sе dogodilo kada stе pokušali izvršiti akciјu igrе (poruka o grеški, poruka statusnе trakе igrе, ...)?

• Koјi је tvoј prеtraživač?

• Molimo da opišеtе problеm prikaza. Ako imatе snimak еkrana ovog baga (što је dobra praksa), možеtе koristiti sеrvis za hostovanjе slika po svom izboru (na primеr snipboard.io) da ga otprеmitе i zatim ovdе kopiratе/nalеpitе link.

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.

• Koјi је tvoј prеtraživač?

• Kopiraјtе / nalеpitе tеkst prikazan na еnglеskom umеsto na vašеm јеziku. Ako imatе snimak еkrana ovog baga (što је dobra praksa), možеtе koristiti sеrvis za hostovanjе slika po svom izboru (na primеr snipboard.io) da ga otprеmitе i zatim ovdе kopiratе/nalеpitе link. Da li je ovaj tekst dostupan u sistemu za prevođenje? Ako je odgovor da, da li je preveden prije više od 24 sata?

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.

• Koјi је tvoј prеtraživač?

• Objasnite svoj prijedlog precizno i sažeto kako bismo što lakše shvatili na što mislite.

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.

• Koјi је tvoј prеtraživač?