Tags
Creators
Details
v0.5.0+fabric+mc1.20.1
Compatibility
Required content
Changes
This release brings the full v0.5.0 feature set to servers still running Minecraft 1.20.1, published from the long-lived support/mc1.20.1 branch. Requires Java 17+.
Important — read before installing: Voxy has no public build for Minecraft 1.20.1, so the bundled Voxy bridge stays dormant on this version. This release is for servers whose players use a private/self-built Voxy port, or for mod developers integrating another LOD renderer through the LSSApi consumer interface.
New Features
- Paper and Purpur server support on MC 1.20.1 — The v0.5.x Paper plugin now runs on 1.20.1 servers (ships properly reobfuscated for 1.20.1's Spigot-mapped runtime).
- Smarter client syncing — All v0.5.0 sync-correctness fixes are included: lost or rejected chunks self-heal instead of leaving permanent holes, and the server pushes change notifications so distant terrain stays current after edits.
- More reliable chunk generation on Paper — Chunks generated for LOD serving are now pinned during the load, fixing a 1.20.1 race where a freshly generated chunk could unload before it was serialized and never reach the client.
Known Limitations
- No Folia support on this line — Folia only has frozen 2023 alpha builds for 1.20.1, and their chunk-loading behavior breaks LSS's generation path. The plugin deliberately declines to load on Folia 1.20.1 rather than run degraded. (Folia support remains available on the MC 1.21.11 and 26.1 releases.)
- Maximum column payload is capped at 1 MiB — a Minecraft 1.20.1 protocol limit; normal vanilla-scale chunks fit comfortably.
Upgrade Notes
- Coming from v0.2.x — Clients rebuild their local LOD cache once on first join (the cache format changed), so the first rejoin re-syncs from the server.
Full Changelog: https://github.com/VoX/lod-server-support/commits/v0.5.0+mc1.20.1
Optional dependencies
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:5r8bwswR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lKiXKLvv:5r8bwswR"
}

