What is the best way to pregenerate LODs, Chunks etc for distant horizon using on a server?
Me and 2 of my friends are trying to find out the best way to play without any lag by pregenerating LODs, chunks and anything necessary before our game sessions.
We are hosting it on Minehut with the "PRO" plan.
I installed chunky and used that at start, but i saw on other post that that is not reccomanded.
Any suggestions on what changes to do to get maximum performance?
The only player of this server are me and 2 other friends and we are just playing a normal vanilla.
7 Replies
/chunky
Using Chunky to pregenerate for DH is not recommended for several reasons. The first one is the swiss cheese that might show up when using chunky while DH is installed. The second reason is that it's pointless, as DH has a build in pregenerator that is better integrated than chunky:
- It saves space by only storing LODs, not normal chunks
- It is faster to use DH's pregenerator to generate the LODs than first using chunky to generate the normal chunks, and then using DH to convert the normal chunks to LODs
- It is part of DH, and therefore always/only called when DH needs it
- Chunky calculates it's radius in blocks, confusing the user if they are not aware of this
Distant Horizons' built-in LOD pregenerator is enabled by default, and can be sped up or slowed down by changing the
Cpu Load in DH's settings, or disabled by turning off Distant Generation.
If you want to pregenerate both LODs and normal chunks, set the Distance Generator Mode to Internal Server under Advanced, World Generator. This will of course take up quite a lot more storage space. Make sure you have C2ME installed if you want to use Internal Server, as the generation speed will be crap if you don't.
Note, this also applied to other similar pregeneration mods.
If the server is modded use the DH pregen command
Before that make sure to change the distant generation mode to save vanilla chunks
/generators
- FEATURES: Complete generation of all LODs with mostly correct structures and trees. Does not save vanilla chunks, and is much faster than INTERNAL_SERVER unless C2ME is installed.
- INTERNAL_SERVER: Generates and saves both DH LODs and vanilla chunks, has 100% correct LODs, because it also saves vanilla chunks it takes the most amount of drive space. Generation speed will suck unless C2ME is installed.
- PRE-EXISTING: generates LODs for all existing vanilla chunks.
If the server is a plugin server, use Chunky
If you get holes after using Chunky, either go into every single chunk with a hole and place/destroy a couple of blocks in the chunk with high CPU load preset and wait some time in each
Or delete all your LODs and start again
/lodstored
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/
Server Mod
- Overworld: SERVER_FOLDER/world/data/DistantHorizons.sqlite
- Nether: SERVER_FOLDER/world/DIM-1/data/DistantHorizons.sqlite
- End: SERVER_FOLDER/world/DIM1/data/DistantHorizons.sqlite
- Custom Dimensions: SERVER_FOLDER/world/DIMENSION_FOLDER/data/DistantHorizons.sqlite
Server Plugin
All dimensions in one file: SERVER_FOLDER/plugins/DHSupport/data.sqliteAlso make sure to increase the server DH CPU load preset if you want faster generation
And install C2ME if you use Internal Server generation mode