-
Notifications
You must be signed in to change notification settings - Fork 1
Client LOD Settings
File: config/chunksmith-lod.properties, on the player's machine, written with
defaults and comments the first time you join a Chunksmith server.
This file only exists on a client. A dedicated server never touches it, and there is no server setting that corresponds to either of these -- they are yours, not the operator's.
Both apply in single-player and multiplayer, for different reasons. In single-player the client half is what hands your own renderer its data; in multiplayer it also governs the download from the server. See Commands for which commands are yours to use where.
Both settings are also reachable with /cslod set <name> <value>, which applies the
value to the running game and saves the file.
Default 300. Minimum 30.
How often the client asks the server "has your LOD store changed?", in seconds.
The check itself is tiny -- 22 bytes out, 34 bytes back, and it opens no file on either side. A full region index is only pulled when the answer is yes.
What this setting is for is the player who joins, walks to their base, and stays there. Chunksmith normally asks for new terrain when you have travelled half a region; a player who does not travel would otherwise never pick up terrain from a pregen that is still running behind them. This poll is what extends their horizon without a relog.
The 30-second floor is enforced in code, not in the file: a smaller number in the file is clamped on read, and the log says so. One poll is one directory listing plus one stat per in-range region, so at 30 seconds a hundred clients cost the server roughly three of those per second. Below that, the sync starts becoming the problem it exists to solve.
Default false.
Send every LOD region to your renderer again on the next join.
Chunksmith remembers which regions it has already handed to voxy or Distant Horizons, so joining a world does not re-send terrain the renderer already has. That record is normally correct. It is wrong in exactly one case: you emptied the renderer's own database. voxy's storage and Distant Horizons' sqlite belong to them, and nothing Chunksmith can read says "this was reset" -- so our record honestly describes data that is gone, and we skip it forever.
Set this true, join once, set it back. /cslod set reinject-on-join true does it without
leaving the game. Deleting the .injected files next to your LOD store has the same effect.
Anything that is not literally true is read as false, so a misspelling cannot quietly
turn a one-shot recovery switch into permanent behaviour.