1.18.2 support

[fizzrepo]

A temporary fix is to:

• Go to your site-packages folder
• Find quarry
• go to data, packets
• Copy 0757_1.18.csv to 0758_1.18.2.csv
• Go back and go into data_packs
• Copy 0757_1.18.nbt to 0758_1.18.2.nbt

Worked for me

[thatITfox]

what is the path if i'm using a virtual environment?

[Lars-Thestorf]

If you have installed quarry using pip you can execute pip show quarry to figure out the exact install path

[thatITfox]

ah alr, thanks man

[fizzrepo]

I don't know if anything really changed in the 1.18.2 release other than the protocol number so I can try to get a PR out.

[dries007]

I think more changed because I had trouble with the NBT data on server join, that's why there is no version released yet.

If you make a PR I'll test it and merge if it does work (then I likely did something else wrong).

[lewisakura]

I did the above 'solution' and got a nastily large error message upon connecting, which I assume is the client rejecting the NBT data that its been sent. wiki.vg does actually have a SNBT version of the data for 1.18.2, although I have no clue how to convert this to regular NBT for Quarry.

https://gist.github.com/joserobjr/d877abd88767eda006ee2d1d8779b176

[dries007]

This is also what I'm struggeling with. The minecraft screen doesn't let me see the entire error message and it's nog logged to console either :(

[lewisakura]

From what I can tell, the error is just saying the NBT is invalid for 1.18.2 -- there's new attributes in this version, annoyingly.

[ArachnidAbby]

I did the above 'solution' and got a nastily large error message upon connecting, which I assume is the client rejecting the NBT data that its been sent. wiki.vg does actually have a SNBT version of the data for 1.18.2, although I have no clue how to convert this to regular NBT for Quarry.

Unsure if this helps? I found this while trying to search around to fix this myself, but my experience is very limited when it comes to mc protocol. https://github.com/TkTech/Burger

[DocterDum]

I tried the fix mentioned above, but joining got the following error (In the proxy terminal and a similar one on the client):

Auth failed: [<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]

[lewisakura]

Using the NBT dumping example (https://github.com/barneygale/quarry/blob/master/examples/client_data_pack_dumper.py) and a modified version of Quarry to disregard the version difference, I have an NBT file that will now no longer cause the massive disconnect error, but the client will never seem to finish loading terrain. This NBT file was pulled from a fresh, vanilla 1.18.2 server.

I see two major differences with this file, however:

• The file name is included in the NBT file itself, which I'm not too sure how it manages to get there considering none of the code in this process would ever reference it from what I can tell, and none of the other NBT files have it.
• It appears this is in a different format to what Quarry would expect, which might cause my bug from earlier. It seems to require a combination of data pack and dimension data. I don't know what script generates this, but I wish it was distributed so that we could do this manually. @JLyne, as the person who does the protocol data, can you please release a guide on how we can do this ourselves?

[dries007]

Release for 1.18.2 created. See release notes on the github release to see how to deal with the "Loading terrain..." issue.