LOD database is not being converted when upgrading DH from 2.2.1a (1.21.1) to 2.3.0b-dev (1.21.4)
Just like what title said, recently I updated my Minecraft client while also updating Distant Horizons from 2.2.1a to 2.3.0b. But after updating (and copying DH's data folder and keeping server's name) I found that migration didn't happen, no lagging, no notification/message. When I checked the log, I found following information (⬇️) indicating that DH itself might think there's no data to migrate while the data itself is still there, with a mere name changing from
overworld to gm150ja4g3ueg@minecraft@@overworld as well as a 9MB new database in that folder. I tried to restore the backup and doing above all over again. But nothing has changed. 🫠
20 Replies
Oh, here's the log
you dont need to migrate data when going from 2.2.1 to 2.3.0
nothing changed except the location where the sqlite is stored
But I did notice there's no LODs rendering outside 10 chunks (server's render distance) and I need to go everywhere to get LODs again
While singleplayer worlds behaves normally
are there now two sqlite files?
Actually a lot of folders with hash-like names and a sqlite file
is there one that is a lot bigger than the others?
Yes! There's one with a size of 4.3GB
While others are MBs
Should I move the sqlite in that folder to the root of that dimension?
Oh? Are where any plans to add a migration for this?
I think, according to other support posts, this should be done automatically in most situations
Probably I will keep the backup and try to move that db
It's working!
Somehow automatic migration not working?
I think so
eyyy
Probably an edge case?
perhaps
Without reproduction steps, it'll stay as an edge case.
Yep... Should I provide you with that backup?
Or an mmc-pack export of my mc instance?
Or any other thing I can help?
Reply here if/when someone gets around to starting to try debugging this.
Okay, I'll do that
I think I need to mark this as solved, but I'm not sure about that, also I'm not sure on marking which message as solution
I wonder what the current migration logic is, in this database, here are Distant_Horizons_server_data/server_name/overworld/[a lot of uuid]/DistantHorizons.sqlite and only 1 has GB level size, the migration should pick the biggest one (or are those UUIDs have other meanings?)
Distant Generation doesn't work in multiplayer, meaning DH won't be able to generate LODs for chunks outside the vanilla render distance.
Instead, as you travel around the world, LODs will be generated for areas you've visited.
In the next update, DH 2.3, you will be able to add DH to your server granted it's running a compatible mod/plugin loader (Fabric, (Neo)Forge, Bukkit and their derivatives). This will allow the server to generate LODs and send them to the client, making distant generation possible on multiplayer.
If you wish to try 2.3 early, read everything in this thread: https://discord.com/channels/881614130614767666/1285883332768563284
Keep in mind that this build is still experimental, we do not encourage using it on large servers until further testing.