• Mohon salin/tempel pesan error yang Anda lihat di layar, jika ada.

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.

• Mohon jelaskan apa yang ingin Anda lakukan, apa yang kemudian Anda lakukan, dan apa yang terjadi

• Apa browser yang Anda gunakan?

• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. 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. apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam

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.

• Apa browser yang Anda gunakan?

• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.

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.

• Apa browser yang Anda gunakan?

• Apa yang tampil di layar ketika Anda tidak dapat berjalan (Layar kosong? Hanya tampil sebagian antar-muka? Pesan error?)

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.

• Apa browser yang Anda gunakan?

• Bagian mana dari peraturan yang tidak diterapkan dengan tepat oleh 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.

• Apakah kesalahan peraturan dapat dilihat dari ulangan permainan? Jika ya, pada langkah ke berapa?

• Apa browser yang Anda gunakan?

• Aksi permainan apa yang ingin Anda lakukan?

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.

• Apa yang Anda coba lakukan untuk memunculkan aksi permainan ini?

• Apa yang terjadi ketika Anda melakukannya (pesan error, pesan status permainan, ...)?

• Apa browser yang Anda gunakan?

• Pada langkah ke berapa masalah tersebut muncul (apa petunjuk permainan saat itu)?

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.

• Apa yang terjadi ketika Anda mencoba untuk melakukan aksi permainan (pesan error, pesan status permainan, ...)?

• Apa browser yang Anda gunakan?

• Mohon jelaskan masalah tampilannya. 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.

• Apa browser yang Anda gunakan?

• Harap salin/tempel teks yang ditampilkan dalam bahasa Inggris alih-alih bahasa anda. 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. apakah teks ini tersedia dalam translation system? jika iya, itu bisa diartikan lebih dari 24 jam

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.

• Apa browser yang Anda gunakan?

• Tolong jelaskan saran Anda secara tepat dan ringkas sehingga semudah mungkin untuk memahami apa yang Anda maksud.

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.

• Apa browser yang Anda gunakan?