yamayaki1
commented
1 month ago now that I've done proper tests, there's only a ~1 second difference in speed.
Most of the time in Cesium is spent on decompressing data, reducing the compression level of Zstd in the config might provide better results. Speed isn't really a concern for this mod anyway.
What'd you suggest doing if the mod became discontinued
So far there hasn't been any serious breaking changes while updating to newer versions of Minecraft, except maybe the world upgrader changes in 24w04a, and anyways, force-upgrading your world isn't really needed after Mojang fixed the performance of DFU. For the foreseeable future I plan on improving this mod and/ or at least doing the basic task of porting it to newer versions.
Could a message be put in vanilla world files in such a way that vanilla wouldn't make a new world over all your progress, make people remember to go back and convert the world should this mod ever become discontinued?
That's something I have been thinking a lot the past days, but I haven't really come to a solution to solve this problem. Thankfully Vanilla can't really "overwrite" the data saved by Cesium, so if people realise in hindsight that they have to convert their world, it shouldn't be too big of a problem. I'll have to do some more experiments on that part.
I included this mod in a modpack that I was making not fully aware of whether it'd be helpful for improving chunk performance, now that I've done proper tests, there's only a ~1 second difference in speed. What'd you suggest doing if the mod became discontinued? Could a message be put in vanilla world files in such a way that vanilla wouldn't make a new world over all your progress, make people remember to go back and convert the world should this mod ever become discontinued?