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
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
ProtocolLib Version =< 5.0.1? ~ 5.2.0
Expected behavior
Chunk loading has been very slow since version 5.x.x, and even at the part where the chunk is supposed to load, the chunk does not load, and because it does not load, the player cannot even connect to the server.
This bug does not occur with protocol lib version 5.0.0.
Currently, this bug is still present in version 5.2.0.
Screenshots
Version Info
Probably 5.1.0 to 5.2.0 (latest)
Additional context
It's the same on minecraft versions 1.20.1 to 1.20.4, and it's the same on paper , purpur , and plazma.
I've tested with over a dozen builds.
I don't know if my bucket is weird or what, I even created a test server and reset all configs, same thing.
The text was updated successfully, but these errors were encountered:
That's not what I meant, If your using any plugin that listens for chunk packets async then it's related to #2545. For example some advanced anti-cheats are doing that so it would probably help you if you could please provide the /protocol dump file to check if that's the case.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Chunk loading has been very slow since version 5.x.x, and even at the part where the chunk is supposed to load, the chunk does not load, and because it does not load, the player cannot even connect to the server.
This bug does not occur with protocol lib version 5.0.0.
Currently, this bug is still present in version 5.2.0.
Screenshots
Version Info
Probably 5.1.0 to 5.2.0 (latest)
Additional context
It's the same on minecraft versions 1.20.1 to 1.20.4, and it's the same on paper , purpur , and plazma.
I've tested with over a dozen builds.
I don't know if my bucket is weird or what, I even created a test server and reset all configs, same thing.
The text was updated successfully, but these errors were encountered: