Data generated from DH is no longer being referenced
The folder of the DH database for the server is no longer being used for LODs on the server I am on. Why was there a new GUID made in a separate folder? What are the conditions where it stops using the one I have underlined in the image?

9 Replies
Looking through the source a bit, does it have something to do with similarity matching?
And apparently copying and pasting the database file to the other folder isnt doing anything.. just generates a new folder instead :destruction:
interestingly, going to a different area of my map does make it go back to the large file.... this is very strange. why do those subfolders exist to begin with?
If you have multiverse support active DH will look through each folder and attempt to find a level that matches the chunk you loaded into. If it doesn’t find one then it will create a new folder.
Don’t have multiverse support enabled unless you need to.
so i assume, if i want to have it pull from a specific database, can i just delete the other folders in there and it will only attempt to match from the one database?
I don’t understand your question.
LOD files are stored in:
/lodfile
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/
Deleting, renaming, or moving the database should be enough to cause it to build a new database for testing
Well, one of my questions is why there is a UUID in the path
i dont understand the point of that uuid, or the case where it decides it needs to generate a NEW uuid
You have multiverse similarity enabled. When that’s enabled it will generate a new folder based on if the system can’t find an existing level that matches.
In general you shouldn’t use multiverse support unless you have to.
gotcha. yeah I unfortunately have to.
It was just confusing why it decided to make a new database to begin with since i hadnt changed worlds, and I had just relogged
it seems to be fine now, it may have been a weird edge case where the chunk i signed out at hadn't been saved to the DB yet so it didnt find a matching chunk anywhere