Tags
Creators
Details
All versions
v0.22.0-beta.1+paper+mc1.21.1
Beta
v0.22.0-beta.1 - Paper/Purpur (MC 1.21.1)6 hours ago 0
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Paper
Purpur
Supported environments
Client-side
Server-side
Client and server
Changes
Changed
- Far players past the draw limit — "Extend Far Player Draw Range" is now on by default: with an LOD mod such as Voxy, far players beyond the game's normal draw limit are drawn. It does nothing while a shader pack is on, and you can turn it off on the mod's settings page.
- Sharing message after saving settings — While no server has received your "Share My Position" choice, the message after a save now says so plainly, and that a server uses its own default until it does.
New Features
- Says why nothing is loading —
/lss statusand the status screen now start with one line: working, or not working and why (the server doesn't have the mod, has it switched off, hasn't answered, or nothing you have installed can show the terrain). - Chat notice — The first few times you join a server where distant terrain can't work, one grey line in chat says why. Each kind of line is shown at most three times ever, and there is nothing to configure.
- Server diagnostics —
/lsslod diagnow lists errors the mod recovered from and how many sessions used each protocol version.
Support
- Beta — A test build for Minecraft 26.3 and 1.21.1. The full 0.22.0 release for all supported versions follows after a few days of testing.
- Platforms — Fabric, Paper/Purpur and NeoForge for Minecraft 1.21.1.
- Sponge — From this version the Sponge build is made for the newest Minecraft version only; 0.21.0 stays available for Sponge on 1.21.1.
Full Changelog: https://github.com/VoX/lod-server-support/compare/v0.21.0+mc1.21.1...v0.22.0-beta.1+mc1.21.1
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:8VZWp1yk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lKiXKLvv:8VZWp1yk"
}

