-
-
Notifications
You must be signed in to change notification settings - Fork 73
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
1.19.30 Example Server Not Sending Chunks Properly #301
Comments
Dupe #158 |
Wait, even if I'm replaying existing chunk packets? |
You need to replay all the packets in the exact order they were received by a client with caching off. Otherwise for a number of reasons (chunk/server cache mismatch, client chunk requests not responded to) you will indeed get no world. |
I am sending them in the same order as they were recieved, and cache_enabled is false in all of them |
Not according to your example code. |
ok, I'm stupid with node, but readdirSync returns in ascending order, right? |
since the files were saved in the order that they were sent to the client, with a number attached for the order |
You need to send all the packets in the exact order with the exact same time delta in order to get a vanilla effect. The server example is intended to offer a basic server for the purpose of development, it won't mimic a vanilla server-client relationship 1:1. |
Is it possible to somehow convert these packets back into a vanilla world using bedrock-provider? |
Closing as dupe also of #163 |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I am using somewhat modified example server code to work with 1.19.30, and I am not loading the world from DB, instead, I am replaying existing chunk packets obtained with the dumper, so world loading 1.18+ should not be an issue, however, all I see is an empty world when I connect.
Any help would be greatly appreciated.
My modified server.js:
The text was updated successfully, but these errors were encountered: