How does client-side work with the new multiplayer changes?
I have been using DH in a LAN server that I host. Due to space limitations I'm the only one using it, as the other players do not currently have the free space for the LOD database and the file for this particular world is rather large.
From what I've read I assume that the server actively sends the LODs to the clients and then they save it locally. I'm just hoping I interpreted it wrong or that there is an option for active sending of LOD without local saving (without knowing for sure how it all works I can not understand whether that would be prohibitively expensive or not).
12 Replies
You are correct. LODs will be stored on both. But the server will have all LODs while client will only have the ones they need.
They can always delete the LOD DBs once in a while
By "ones they need", does this mean that a client will only have the LODs within their render distance? which means that more LODs (that the server already has) will only be added to the client if they actually travel within their DH render distance?
Additionally, does loading LODs in the server mean also generating real terrain, therefore further increasing the size of the world?
/generator
- 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.
Yes, but if the player travel through the world all the LoDs that are no longer in their DH RD are being kept
To you first question: Also yes. The client will download the LODs within their render distance, and nothing else. When they move, only the new LODs within range are downloaded from the server. The client keeps all the LODs it has seen, and when revisiting an area where they've downloaded LODs before - a comparison is made to see if there are any updates on the server for those LODs, or if they can just keep using the same ones.
And if an LOD is updated on the server while players are in range, they will automatically receive the update and replace the older LOD they downloaded previously
This is all assuming that you haven't disabled login sync or real time updates of course
gotcha 👌 And just to confirm, it looks like the server plugin matches the description of INTERNAL_SERVER, since it looks like real chunks are being saved, changing my server's total data from ~1.5GB to ~2.3GB on world size alone just by standing still with only one player. Is there a way to only process creating LODs but not real vanilla chunks? I know the question might seem a little strange, but I figure to ask anyway to see if it's possible not to bloat the server
Not possible
You would have to trim your world after LOD generation to recover the used space
I always recommend using the border feature of the plugin to limit how far out the world and LODs can be generated
I see, so pretty much once the initial generation finishes, it basically becomes a "diff", where only modified chunks that players are in are given updated LODs, so long as you're well inside your initial generation.
And I'm guessing that even after trimming the world, as soon as a player moves several chunks in one direction, only those super distant vanilla chunks are generated since no LODs exist there yet, causing another bloat, if no border exists?
Yes, it must have the underlying chunks to generate LODs, but after that it will only touch a chunk again if the chunk changes
And obviously if you have deleted the chunk and no player actually travels there to regenerate it, then it cannot change
makes a lot of sense 👌 thanks for the info!