Leaving and rejoining server restarts the lod sending process from the beginning.

[Barkells]

Leaving and rejoining server restarts the lod sending process from the beginning. When you leave a server and rejoin the lods which have already been sent to the client get sent again. Is this by design?

[travismlee]

Not the maintainer, but I've noticed that too. I've been slowly working on a solution for it (essentially having server & client compare hashes of sections to make sure they're sync'd rather than just retransmit the whole thing). I was going to PR it to this repo when I was done, but I guess it'd be good to start a discussion on it to see if @PooSmacker has thoughts.

[travismlee]

@PooSmacker Saw the 1.2.0 release, few bugs I found;

1. Server & client only sync on login, and they only sync within a radius - if the player were to move to a different location that they already have voxy LODs for then the issue still persists (server does not request a new manifest based on the player moving around).

2. If you use a mod like Chunky to generate chunks outside of player render distance, then the hashes can get corrupted for the client - causing holes in the world that persist beyond reconnecting, requiring them to delete their clients .voxy folder to re-pull everything. See screenshot.

[PooSmacker]

@travismlee can u try this https://github.com/PooSmacker/VoxyServer/releases/download/test/VoxyServer-1.2.0.jar and lmk if it fixes ur issues

[travismlee]

@travismlee can u try this https://github.com/PooSmacker/VoxyServer/releases/download/test/VoxyServer-1.2.0.jar and lmk if it fixes ur issues

1. Appears fixed
   (measured through network usage, before it was 3Mb -> teleport -> 300Mb. Now it's 3Mb -> teleport -> 6Mb)

2. Is significantly less common, still present, 6 total holes that I could see.
   Persists through reconnect, had to delete client .voxy folder to get it to load.
   (server view distance = 10, chunky radius = 24)

[PooSmacker]

yeah those holes happened before the update, tbh im not too sure of the cause, ill continue to investigate but for now ill release this as a hotfix. thanks for lmk