• אנא העתק/הדבק את הודעת השגיאה המופיעה במסך, אם יש כזו.

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.

• בבקשה הסבר מה רצית לעשות,מה עשית ומה קרה

• מה הדפדפן שלך?

• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. האם טקסט זה זמין במערכת התרגום? אם כן, האם היא תורגמה במשך יותר מ -24 שעות?

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.

• מה הדפדפן שלך?

• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.

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.

• מה הדפדפן שלך?

• מה הוצג על המסך כאשר נחסמה (מסך ריק? חלק ממשק המשחק? הודעת שגיאה?)

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.

• מה הדפדפן שלך?

• איזה חלק של הכללים לא היה מכובד על ידי עיבוד 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.

• האם אפשר לראות את הפרת החוק בשידור החוזר? אם כן, באיזה מספר מהלך?

• מה הדפדפן שלך?

• מה היה המהלך במשחק שרצית לבצע?

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.

• מה ניסית לעשות שגרם לפעולה הזו

• מה קרה כאשר את/ה מנסה לעשות את זה (הודעת שגיאה, הודעת פס סטטוס משחק, ...)?

• מה הדפדפן שלך?

• באיזה שלב במשחק הבעייה קרתה (מה היו ההוראות הנכונות)

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.

• מה קרה כאשר את/ה מנסה לבצע פעולת משחק (הודעת שגיאה, הודעת פס סטטוס משחק, ...)?

• מה הדפדפן שלך?

• אנא תאר/י את הנושא המוצג. 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.

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.

• מה הדפדפן שלך?

• בבקשה העתק והדבק את הטקסט המוצג באנגלית במקום בשפה שלך. 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. האם טקסט זה זמין במערכת התרגום? אם כן, האם היא תורגמה במשך יותר מ -24 שעות?

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.

• מה הדפדפן שלך?

• אנא הסבר את ההצעה שלך במדויק ותמצית כדי שיהיה קל ככל האפשר להבין למה אתה מתכוון.

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.

• מה הדפדפן שלך?