-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bedrock shows large amount of online players and refuses connection #19
Comments
That's strange, I cannot reproduce on my setup. |
I get the same message when joining from Xbox. Just tried it. |
I’m on version 1.16.210 as well, on an IPad. |
Could be something to do with the Protocols being changed and info being read from packets where it shouldn't. Of course I could be completely wrong, but this gives me a good idea.. |
Hi ! Maybe you could join our discord support private chat and try to debug it together, unfortunatly, I don't have a Xbox One to try it. |
I am having the same issue on the mobile Bedrock Edition. When the server is asleep there is a huge amount of players online, preventing joining (also, setting the max player count to -1 does not work). I am on the most recent version of Bedrock (v1.16.220) and the most recent version of the sleep system. |
Most plugins would not matter as the issue here is present while the server is offline, if that makes sense |
I added a web-gui so mobile player can launch the server since bedrock support is still WIP by the library. |
There is a new version to support bedrock: |
When I have the server sleeping, if someone tries to connect via bedrock edition through LAN, the amount of online players shows an extremely large number that clips into the green circle next to it, and when you try to connect, the client says “This server is too popular, wait a bit for it to free up some space”. This renders starting the server via LAN bedrock impossible. I am unable to get some example screenshots for more info right now, but I will try and get some as soon as possible.
The text was updated successfully, but these errors were encountered: