-
-
Notifications
You must be signed in to change notification settings - Fork 693
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
Chunks don't unload on bedrock #2725
Comments
I'm not sure if there's anything we can do about this on our end; Bedrock doesn't have any packet to unload chunks and instead does this itself. |
(Though, currently we don't forward the client's render distance to the server. We are aware that we need to implement this) |
Can confirm - the server's render distance overrides the clients ( so you can get render distances of 64 on Switch where it should be 12 ). This does cause lag after a while. |
@Camotoy what about datapacks like terralith then? |
No. |
Describe the bug
As the title suggests when a bedrock client joins a Geyser server and roams around for a bit, the chunks that they have explored or loaded don't get unloaded. The chunks do get unloaded by the server however they are still rendered by the bedrock client. This causes severe lag in low end devices as the unloaded chunks can be 500 blocks long.
To Reproduce
Expected behaviour
Say that you have set your render distance set to two. Move in any direction for about 500 blocks. You shouldn't be able to see blocks further than two chunks away.
Screenshots / Videos
https://youtu.be/pXhN3PaevG4
Server Version and Plugins
Plugins
Geyser-Spigot.jar
floodgate-spigot.jar
Geyser Dump
https://dump.geysermc.org/ixmup2gabSaICVn2A7TcgNQFfbuDWlsT
Geyser Version
Build #977 (Dec 21, 2021, 4:02:24 AM)
Minecraft: Bedrock Edition Version
1.18.2
Additional Context
No response
The text was updated successfully, but these errors were encountered: