How do I disable the DH Plugin from generating new chunks?
Pretty self explanatory title. I want all full features aside from this one, just to prevent massive storage demands.
71 Replies
The chunks must be generated for the plugin to know how the LOD should look. You can however trim the world after generating your desired render distance
You can also apply a world border to stop generation past a certain point
It can't simply generate the LOD based off of the chunks already generated in the orld? That is what I was wanting.
I forget to mention, this is a server.
No, the plugin doesn't know which chunks exist and which don't. It simply requests the server to provide the areas the clients want LODs for
And in order to do that it must generate chunks?
I genuinely dont know by the way, sorry if I sound rude.
The server must generate the chunks when they are requested, yes. But I just had an idea. Will come back to this later.
Latest nightly now (again) has the option to disable generation of new chunks
The new config entry is called
generate_new_chunks
Delete your old config and have a new one automatically generated, or add it in manuallyDid you JUST add that today @Jckf ?
Yes, I got home about 4 hours ago and started working on it =P
THANK YOU
This will seriously be a lifesaver for the storage of our server
It's a frequently requested feature as well, and we used to have it before - but the implementation was so poor that unabling it cause all servers to lag
I had a brainwave when you asked earlier though, and realized how it could be done well
I am no coder, but wouldnt you be able to request a list of all the existing chunks and just send data from those?
you fixed it obviously but I am just theorizing
The problem with doing it that way is that the amount of data you have to keep track of (ie. coordinates of all existing chunks) grows with the size of the world. So the bigger your world is; the more RAM the plugin would use.
I see
I Would ask how you did it but I probably wouldnt comprehend it
The old approach was to attempt a chunk load where the server was told to not generate anything, and if the load failed - then we knew the chunk didn't exist.
The new solution is basically also this, but instead of just doing it as a check - we do it when we actually want the chunk data during LOD generation. So if one of the requested chunks comes back empty when chunk generation is disabled, then we know that the chunk doesn't exist and we can skip LOD generation as well.
Wouldnt that old approach be asking to load billions of unloaded chunks?
Yes, the plugin does that. For every 1 LOD it has to build, 16 chunks have to be loaded/generated
Where exactly did you post this?
You can find the latest nightly builds here https://gitlab.com/distant-horizons-team/distant-horizons-server-plugin/-/wikis/Nightly-development-builds
GitLab
Nightly / development builds · Wiki · Distant-Horizons-Team / Dis...
Add support for Distant Horizons to your Bukkit server.
It says last edited 4 days ago though
The wiki article, sure
Ah, ok.
The links always point to the latest build
I see, thank you sir.
You said generate_new_chunks?
Searched it up in the config yml
And it doesnt appear to be there
If you already had a config.yml, then it will be missing. You can see the default config file here https://gitlab.com/distant-horizons-team/distant-horizons-server-plugin/-/blob/develop/src/main/resources/config.yml?ref_type=heads
GitLab
src/main/resources/config.yml · develop · Distant-Horizons-Team /...
Add support for Distant Horizons to your Bukkit server.
To edit the config, press the button next to the FOV slider to edit the config.
The config file found in .minecraft/config/DistantHorizons.toml
It appears to keep generating
DHS still says generation in progress
Default set to : true
and
generate_new_cunks set to : false
Generation just means it's generating LODs
ooohhh
And it might not even be new ones, but updates to old ones
Ok ok, thanks
@Jckf I may have done something wrong but I don't believe it worked. There were still a bunch of new chunks that generated (Which I am able to tell thanks to Bluemap)
It does appear to have just generated this morning though, which is odd.
Looking at the console, it says "Received DH config for JohnsJohn42".
So I am guessing someones config over-rode the No-go for pre-generation in the server config.
What do you mean? Unless you have defined a world border, the plugin will generate LODs as requested
I am just saying that chunks generated
when the world gen thingy is set to false
Let me check the border part
The border_radius is set to 5000 but parts of the generation reach -7100 and +7100
Yeah border is enforced on player requests, not the pregen command, so you can pregen beyond the border
but doesn't the "Generate_new_chunks" prevent that?
If you don't have those chunks already, then yes. Can you post your config?
yes one moment
You have not disabled chunk generation
Really?
Lines that start with
# are "commented out"
Ie. they don't matterdarn*
Do I get rid of the Hash? Or do i disable it some other way.
The idea is that you can remove the hash to "enable" that line of config, yes :)
Ok that makes sense man, thank you.
I will likely experience another issue soon if I were to guess but we will see.
New to minecraft plugins so quite inexperienced I am
Can you just send me your config lol
I'm guessing you're just editing the files in Notepad or something similar? It would probably help a lot if you got an editor with proper syntax highlighting. Here's a screenshot of how the default config looks when I open it: You can very clearly see which lines are "in effect" and which are commented out.
yes
The generate_new_chunks should be working and false, I cant see the color but the hash isnt there.
👍
It still generates chunks sadlyt
I am unable to reproduce that on my end. When I disable chunk generation, it only generates LODs for areas when chunks already exist - and no new chunks appear in my world
It completes a pregen task with 1024 chunk view distance in about 60 seconds when chunk generation is disabled, because it isn't actually doing any work
And my world folder is 3.8 MBs afterwards
The LOD database is 32.8 kB
A single LOD was generated, presumably for the spawn area - where the server always generates chunks
Can you send me the config that you used?
It's just the default config with that one hash sign removed
I'd rather see yours again so that we can check if you did something wrong
or if there's something else funky going on here
I am having the same issue
same exact configuration, generate_new_chunks is set to false and not commented out
I am still unable to reproduce any unwanted behavior here. This is the total view distance I get with DH on a fresh server with generation disabled. You can see on the right hand side that most LOD requests have "failed" (rejected because the chunks don't exist)
@Batman what is your server setup? since we both have the same issue, maybe we can find some pattern
When I get home I’ll send my config
few days late but here is the config
I could be doing something wrong but idk
still generates new chunks
Which server software and MC version? I'll have to try and reproduce this
Paper 1.21.4
That's what I use locally for testing as well
Can you explain how you are determining that the plugin is causing world gen?
I have the Bluemap plugin, its basically dynmap but just with some upgrades.
I can see that new terrain is being generated very clearly over time on bluemapo
it randomly generates some nights on its own accord
It also does state that it is generating in console.
DH and DHS will constantly be generating forever as long as there is activity in the world, like water flowing, plants growing, and mobs griefing
Seeing the console message that some LODs were generated does not automatically mean that chunks were generated
Additionally; DHS will never generate anything new "on its own accord". Every new LOD it creates is a response to either a player LOD request, or an admin pregen command.
so there is no way realistically to prevent the plugin from not generating any new chunks?
nothing has actually generated for a while
so mayb it resolved itself?
I have not seen any proof in this thread that the plugin is causing chunk generation
Well I’m not trying to waste your time even if it may seem like it. I don’t have chunky and I had the config set to no chunk generation the moment I got it setup this time.
And our server looks like this
Is most definitely generates chunks
But like I said, it hasn’t in a week or so so maybe it resolved itself.
@Batman today I checked out the latest nightly build and there is an option for that now but ask @Jckf if it works
I think he knows ;) It was made because of his request IIRC
https://discord.com/channels/881614130614767666/1355554854537527547/1355729951734759434
Oh mb did not see it
Jckf, I am not sure why it generated all those chunks that first day I put it on, but nothing has happened since and the feature has worked in that sense. So, thank you!
What's the expected behavior if a player is say, right at the border between pregen chunks and chunks that the player is generating for the first time due to travelling? Will LODs be generated on completely new chunks that the player is directly on? and will those be persisted?
I thinks soo because it will request them
As an update I think
No no I’m pretty sure that it will import them
Look in f3 if you see any activity if you are on newly generated chunks