Tags
Creators
Details
All versions
v0.16.0+neoforge+mc26.2
Release
v0.16.0 - NeoForge (MC 26.2)last month 39
Compatibility
Minecraft: Java Edition
26.2
Platform
NeoForge
Supported environments
Client and server
Changes
Configuration
- Commented YAML settings — Client and server settings are grouped by feature, with comments explaining units and resource costs.
- Reload settings — Use
/lsslod reloadon servers or/lss reloadon clients; settings that need a restart or reconnect are reported. - Automatic JSON migration — Existing settings migrate to YAML on startup, preserving values and accepting the old loader's comments and loose JSON syntax.
- One-way migration — Downgrading to v0.15.x reads the retained JSON and ignores YAML edits; copy changes back into JSON before downgrading.
- New-install distances — Fresh configurations use 512 chunks in the Overworld and End and 64 in the Nether; migrated distances stay unchanged.
- Removed commands —
/lsslod setand preset commands are removed; edit the YAML, then run/lsslod reload.
Client Settings
- Updated Chinese translations — Adds Simplified and Traditional Chinese translations for the new settings labels, tooltips, and feedback.
Bug Fixes
- SQLite compatibility — Fixes NeoForge SQLite startup conflicts without requiring an additional library mod.
- Backfill fixes (Fabric/NeoForge) — Enabling during startup waits for the store; failed manual starts no longer report “already running”.
Support and Compatibility
- Platforms — Fabric, Paper/Purpur/Folia, and NeoForge for Minecraft 26.2; Folia is experimental, and NeoForge is best-effort without distant-player rendering.
- Compatibility — Preserves the network protocol and LSS/VSS configuration adoption.
- Known limitations — Existing Xaero first-spawn gaps, region-boundary shading seams, and shader/LOD-depth limitations remain.
Full Changelog: https://github.com/VoX/lod-server-support/compare/v0.15.1...v0.16.0
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:lKiXKLvv:NCAN9aDJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lKiXKLvv:NCAN9aDJ"
}

