mcaselector VS sodium-fabric

I'm going to guess there's no backup but it might still be possible to salvage. Based on the error, at least two chunks have malformed data that can't be decompressed. The first thing to try would be to attempt to open the world with MCA Selector. If it can identify and cope with the bad chunks, you can delete them and get back into the world.

Hello all! This is a screenshot of the terminal for MCA selector when I try to install it on my Mac using these instructions: https://github.com/Querz/mcaselector/wiki/Installation

edit : MCA Selector is the solution i found it here after googling a while https://github.com/Querz/mcaselector

Try using a program like MCASelector: https://github.com/Querz/mcaselector/releases

I use MCASelector on my long run survival, it works pretty good

Correct, that's the only thing left from that world. If you can load the region folder in MCASelector you'll get a top-down view of what's there.

If it is caused by your explorers going out 20,000 blocks you could try using a tool like MCASelector to trim the world back down to a manageable size.

Use MCAselector to prune the chunks you want to delete then load the world in 1.20 when it’s released and those chunks will regenerate.

In case you don't know, there's https://github.com/Querz/mcaselector which can do this fairly easily: You can even filter chunks by how long players have been in them.

[22:52:47] [Render thread/WARN]: If the game crashes immediately after this point, please make a bug report: https://github.com/CaffeineMC/sodium-fabric/issues

I googled "fabric crashes with falling block" and found this GitHub Issue in the Sodium Repo. Solution: install Indium, because continuity relies on it to bridge over to sodium.

It`s Indium. https://github.com/CaffeineMC/sodium-fabric/issues/1324

GitHub link

if https://github.com/CaffeineMC/sodium-fabric/issues/1006 is what you are talking about, it is an upstream issue for any forge port of the sodium mod

Wow, a reasonable criticism! According to this issue, transparency sorting hasn’t been implemented, and so the behavior is inconsistent. Surprised to see a pull request linked that had fixed it, but was never merged and is now incompatible. Definitely affects users who have farms and stained glass builds though!

The problem with the multithreaded version of Optifine is that OpenGL doesn't officially support multithreading (at least not with older versions of OpenGL; Sodium (for modern versions) uses a "multidraw" function to get up to 10x the FPS but also uses OpenGL 4+, and even then it has issues on many drivers. Note that using such modern features would require a "core profile", precluding the use of all legacy fixed-function methods so the entire renderer would have to be rewritten).