Server side configuration
Which variables should I adjust in config
.toml for clients to not be able to generate LOD for chunks farther away than 32 chunks?10 Replies
GitLab
Server Owners · Wiki · Distant-Horizons-Team / Distant Horizons ...
This is a mod that adds a Level Of Detail (LOD) system to Minecraft. This implementation renders simplified chunks outside of the normal render distance allowing for an...
You can adjust the setting on the server with the
/dh config command.I don't understand whether these settings are in blocks or in chunks. 4096 seems too big of a default value for chunks, so I assume it's in blocks? But then for some reason when I join server it says it will be generating chunks for 11 hours, so it seems too much. I've read the FAQ in wiki, but I'm still confused.
They are in chunks.
And yes, default is 4096 because generation is continuous. There is physically no pause.
Why is default 4096 chunks then? It's huge.
Servers benefit not having to process additional loads, allowing faster generation.
Alright, it's more clear now.
One more bit which is unclear. Is "DH is loading chunks" message client side or server side? Can I speed up the process? It says abormally large amount of time, lik 9-11 hours remaining.
And
/dh pregen status says that nothing is runningThe loading is server side, but the message is client side. Loading can be sped up with /dh config common.threadpreset and using auto-fill to complete the command.
I believe that is only for running the pregen command. Which is there if you want to pregen without anyone online
Can I actually check which/how many chunks are currently in progress to get LODs generated then?
Enable the wireframe in the debug tab and ofc enable whatever info yoy want the wireframe to show.(e.g. worldgen/import que) just know that while you are connected to the server, the chunks you see in the wireframe as qued are the ones to be imported from the server, after they were generated ofc.