Pregen LODs for server in single player, chunks are messed up, biomes completely cut off at chunk.
Using DH 2.3.2-b mod for both client & server on Forge 1.20.1
I followed the instructions for pregenning on the wiki by creating and downloading a dedicated host multiplayer world then loading it into single player. Then I let it load overnight and the following day I uploaded the entire world into my server host through FTP. There was DistantHorizons.sqlite which was around 10 GBs but no .sqlite-wal or sqlite.shm present. However, after loading it into the server host and playing multiplayer, it ended up generating new wal and shm files but this ended up with huge chunks where biomes past the spawn area are completely cut off in a straight line. It also looked nothing like the world I generated in single player (except the spawn zone).
Did I do something wrong?
6 Replies
Seems like either the world seed, worldgen mods/datapacks or the MC version do not match
IDK if you have to do anything else apart from moving the world folder though
You can always just pregen directly on the server
As for the wal and shm files, they should only exist When the server is running and are temporal files
The note about them is important only if they exist after the server gets closed
Do you know if using the pregen will attempt to regenerate every chunk from the start radius? Or will it try to continue from what is already loaded. Mostly trying to avoid it because my computer's CPU is much stronger than the server host.
Also thanks for the info on the purpose of the wal and shm files
It will try to generate everything once more, but when it finds a chunk and LOD already exist it will skip it
If it finds LODs, it skips it. That means, if the LOD data exist for it but the chunk does not, it will still skip it.
When there is chunk updates (as in block placement, breaking, chunk creation, etc.), LOD updating will be processed.
Is there any way to prevent it from skipping?
You can delete the LODs, then there will be nothing to skip