Sharing SQLite for server issue.
Hello, I'm running into some trouble getting distant horizons to work how I would like on an Aternos server.
I had an idea to preload the world in single player with something like chunky, and then sharing the .SQLite with them so that they can have a farther view distance without having to travel and load chunks on their client.
However we are getting an error when loading in, and I think it is either one of two things, either people have built structures on the world, so DH is noticing a disparity between the .SQLite and the world save, or the SQLite is rendered out to 3000 (Blocks i believe is what chunky uses), while the world itself was only loaded out to 1000 (Blocks?), and DH is noticing the difference between that and causing an error.
If it was the first one I would assume DH would overwrite the old data and be no issue, the second idea I am not sure how it would handle that.
If I delete the preloaded SQLite it creates a smaller one and works no problem.
I also am only moving one SQL, labeled DistantHorizons.SQLite
I am not using any shaders.
It worked initially when I first started the server and imported the SQLite, it seemed once changes were made to the world is where the issue arises.
The Server and Client are both on Fabric 1.20.1, Loader 0.16.2 Attached are mods associated with the server, client, and the error message received with the preloaded SQLite.
Any insight into why it's not working how I expect, and any ways to get it to work as intended is appreciated.
12 Replies
Don't use chunky to pregen just use the dh world generator when pregenerating .sqlite files
Just a tip for next time
I did read that could cause an issue, but I didnt have the error when I first loaded the server, and the error came up after the third player joined, and some changes to the world had been made, which makes me believe chunky didnt cause the issue. I added this to the original post.
There is an even easier way to pregen chunks for everyone and that is by using the server side fork located here #Server-side support
/chunky
Chunky is known to cause LODs to turn into swiss cheese and bloat up world size, as can be seen in the attached screenshot.
We recommend you enable "Distant Generation" in Distant Horizons' settings and wait.
If you actually want to pre-generate vanilla chunks along with LOD data, disable Distant Horizons, wait for chunky to finish, then re-enable Distant Horizons.
You should bew moving all 3 DB files
DH built in generator should generate everything up to your DH RD if you give it enought time, but you might have slow it down a lot by using chunky
Chunky is 50% slower then DH generator
I had tried this while I was in server while I was at work but it didn't work, I probably shouldve done it in the single player version of the world. Didn't have the swiss cheese issue though.
Thank you, I was thinking this was the issue but I wanted to double check, will mark as solved once I get it to work for other's.
Another question, I see there are three folder locations that have DH SQlite files, the only ones that need moved should be the three in (WorldName)>data, not (WorldName)>DIM1 >data and (WorldName)>DIM-1>data?
As far as i know DIM1 is the nether and DIM-1 is the end but i am not certain
/lodstore
Single Player:
- Overworld:
.minecraft/saves/WORLD_NAME/data/DistantHorizons.sqlite
- Nether: .minecraft/saves/WORLD_NAME/DIM-1/data/DistantHorizons.sqlite
- End: .minecraft/saves/WORLD_NAME/DIM1/data/DistantHorizons.sqlite
- Custom Dimensions: .minecraft/saves/WORLD_NAME/DIMENSION_FOLDER/data/DistantHorizons.sqlite
Multiplayer:
- .minecraft/Distant_Horizons_server_data/SERVER_NAME/
Depends if you care about nether and end
But I have no idea where to put them
You would have to visid those dimentions for DH to generate the files and replace those
Gotcha, I'm not bothered by it at the moment, Just wasn't sure what those files were used for.