LOD Server Support

Distributes LOD (Level of Detail) chunk data from servers to connected clients over a custom networking protocol. Built primarily as a multiplayer backend for Voxy clients request distant chunks in batches, the server reads them from disk or memory and streams the data back, enabling Voxy to render terrain far beyond the vanilla render distance on multiplayer servers. The result: players see fully rendered terrain out to hundreds of chunks on multiplayer servers, without needing to explore the world first.

Supports Fabric clients and Fabric, Paper, Purpur, Folia servers.

See https://github.com/VoX/lod-server-support for the most up to date documentation.

Demo Video: https://github.com/user-attachments/assets/721fb344-890e-4e03-ab36-539444427f7b

Installation

Install LOD Server Support (LSS) on both the server (Fabric mod or Paper plugin) and every client (LSS Fabric mod + Voxy). Without LSS on both the connecting client and on the server it will not function.

Fabric Client

1. Install Voxy and place lod-server-support-fabric.jar in the client's mods/ directory
2. Join a server running LSS — client config is generated at config/lss-client-config.json

Fabric Server

1. Place lod-server-support-fabric.jar in the server's mods/ directory
2. Install the Fabric mod and Voxy on all clients
3. Restart the server — config is generated at config/lss-server-config.json

Paper/Purpur/Folia Server

1. Place lod-server-support-paper.jar in the server's plugins/ directory
2. Install the Fabric mod and Voxy on all clients
3. Restart the server — config is generated at plugins/LodServerSupport/lss-server-config.json

Commands

Server (Fabric and Paper)

• /lsslod stats - Show per-player transfer statistics
• /lsslod diag - Show detailed diagnostics (config, bandwidth, queue depths)

Client (Fabric only)

• /lss clearcache - Clear the local column cache, forcing all chunks to be re-requested from the server
• /lss diag - Show client-side diagnostics (connection, throughput, scan progress, request budget)

Configuration

Server (Fabric and Paper)

Server config is generated on first run:

• Fabric: config/lss-server-config.json
• Paper: plugins/LodServerSupport/lss-server-config.json

Setting Default Description enabled true Enable LOD distribution lodDistanceChunks 256 Max LOD distance in chunks bytesPerSecondLimitPerPlayer 20971520 Per-player pre-compression bandwidth cap (20 MB/s) bytesPerSecondLimitGlobal 104857600 Total pre-compression bandwidth cap (100 MB/s) diskReaderThreads 5 Thread pool size for async disk reads sendQueueLimitPerPlayer 4000 Max queued column payloads per player (each carries a full chunk column of sections) syncOnLoadConcurrencyLimitPerPlayer 200 Max in-flight sync requests per player generationConcurrencyLimitPerPlayer 16 Max in-flight generation requests per player enableChunkGeneration true Generate missing chunks on demand for LOD data generationConcurrencyLimitGlobal 32 Max chunks generating server-wide at once generationTimeoutSeconds 60 Timeout for pending chunk generation perDimensionTimestampCacheSizeMB 32 Max timestamp cache size per dimension in MB (used for up-to-date checks on reconnect) dirtyBroadcastIntervalSeconds 10 Interval for pushing dirty column notifications to clients

Paper-specific: The config also includes an updateEvents list of Bukkit event class names used for dirty chunk detection. /lsslod commands require the lss.admin permission (or op).

Client

Client config is generated at config/lss-client-config.json on first run.

Setting Default Description receiveServerLods true Enable receiving LOD data from the server lodDistanceChunks 0 Max LOD request distance in chunks (0 = use server limit)

License

MIT