You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client version: 1.12.2
Server OS: Raspbian Linux raspberrypi 4.19.97+ #1294 Thu Jan 30 13:10:54 GMT 2020 armv6l GNU/Linux
Cuberite Commit id: cfedb03
Expected behavior
If player lost network connection on the login state, he should be able to log in after bringing network back.
Attempt to kick a plyer should kick him even when he is in the login state.
Actual behavior
If player lost network connection on the login state, each time he attempts to log in again, he gets the message A player of the username is already logged in.
Attempt to kick ghost player prints out Kicking player @p for "You have been kicked." and player stays in the login state (but he still can not join).
Steps to reproduce the behavior
Try to join the server and turn the network off when Logging in message appears.
Then server log displays Player @p joined server and after network returns, player can not join anymore.
Server log
[13:05:33] Startup complete, took 10748ms!
Info [13:05:48] Player bitrate16 has joined the game
[13:07:43] Executing console command: "kick bitrate16"
Info [13:07:43] Kicking player bitrate16 for "You have been kicked."
Info [13:11:31] Kicking player bitrate16 for "Server shutdown"
[13:11:32] Shutting down server...
The text was updated successfully, but these errors were encountered:
Also happens outside the login state, when a player has played for a bit. If they disable their network connection, Cuberite tries to disconnect the client repeatedly after 30 seconds (Nooooo!! You timed out! D: Come back!) until Cuberite gives up.
This problem may be caused by natural behavior of the raspberry pi zero w, on which the server was running.
TCp/UDP sockets may stay in WAITING or CONNECTING state for very long time because of very slow cpu.
Client version: 1.12.2
Server OS: Raspbian Linux raspberrypi 4.19.97+ #1294 Thu Jan 30 13:10:54 GMT 2020 armv6l GNU/Linux
Cuberite Commit id: cfedb03
Expected behavior
If player lost network connection on the login state, he should be able to log in after bringing network back.
Attempt to kick a plyer should kick him even when he is in the login state.
Actual behavior
If player lost network connection on the login state, each time he attempts to log in again, he gets the message A player of the username is already logged in.
Attempt to kick ghost player prints out Kicking player @p for "You have been kicked." and player stays in the login state (but he still can not join).
Steps to reproduce the behavior
Try to join the server and turn the network off when Logging in message appears.
Then server log displays Player @p joined server and after network returns, player can not join anymore.
Server log
The text was updated successfully, but these errors were encountered: