Skip to content
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

Support Caves and Cliffs #8

Closed
ATXLtheAxolotl opened this issue Dec 10, 2021 · 5 comments · Fixed by #13
Closed

Support Caves and Cliffs #8

ATXLtheAxolotl opened this issue Dec 10, 2021 · 5 comments · Fixed by #13

Comments

@ATXLtheAxolotl
Copy link

No description provided.

@TaylorDale
Copy link
Contributor

Is 1.18 supported with the 2.0.0 release? I'm still getting subchunk count = -1 in the level_chunk event (I note there is a comment to say this is for loading biomes, but I don't get any subchunk_count > -1).

@ATXLtheAxolotl
Copy link
Author

Not really sure. I think the latest commit adds some 1.18 functionality though.

@TaylorDale
Copy link
Contributor

TaylorDale commented Jan 8, 2022

Hmm still getting sub_chunk_count:-1 with 2.1.0 unfortunately. Any ideas @extremeheat ?

@extremeheat
Copy link
Member

extremeheat commented Jan 8, 2022

1.18 level format is now supported here, and there are examples for on-disk support in this repo. For network support the chunk fetching procedure has changed and depending on how the server wants to provide chunks (there are about 4 ways to do this now...), the client may have to raycast and request data for the individual subchunks that it needs opposed to the server sending everything in one packet. Will be implemented inside of mineflayer, progress can be tracked in PrismarineJS/bedrock-protocol#116

So if your server is running pocketmine, the sub_chunk_count should be not -1 and networkDecodeNoCache will work as usual.

@TaylorDale
Copy link
Contributor

Interesting, thanks. So essentially there is now a client request command that would take parameters like {cX, cY, cZ, subIdx} ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants