
Chunksmith
Pre-generates chunks fast, and safely: an adaptive throttle paces generation against server tick-health so it can run with players online. Builds Distant Horizons / voxy LOD data as it goes and serves it to clients. Fabric, Forge, NeoForge and Paper/Folia.
Tags
Creators
Details
4.5.1+26.x-plugin
Compatibility
Changes
- The startup message about LOD storage now says about 5 KB per chunk (measured 2026-10-12 on 9,409 chunks), not 12 KB. Nothing about the store changed; the old figure overstated it.
- When LOD downloads over the fast path fail, the client now says why: the first failure's cause is printed after the "LOD: done" line and shown in the download status. Before, only the "failed" count went up, with no error anywhere (mod_support #48).
- Fixed: when LOD downloads over the fast path all failed, the client only switched to the slower in-band channel after trying EVERY region. With requests hanging to their 60-second timeout that took about an hour, so LOD never arrived. It now switches after the first four fail with nothing received, within about a minute (mod_support #48). A busy server (HTTP 429) does not count.
- Fixed: the client no longer starts an in-band transfer while leaving a server, and the "accepted a connection but served nothing" warning names the real port instead of 0.
- Fixed (server): a download whose receiver stops reading (a PC that lost power, a dropped Wi-Fi link) is now closed after 30 seconds without progress. Before, each one held one of the backchannel's four threads for up to a quarter of an hour, and four of them stopped downloads for every player.
- Fixed: on a Bukkit/Paper server (which has no in-band channel), a client that fell back to in-band waited for an answer that never came and stopped syncing for the rest of the session, so it never tried the fast path again either. The client now gives up an unanswered in-band request after 60 seconds and tries the backchannel again at the next sync, so LOD arrives as soon as the backchannel works.
- Fixed: when the client fell back to in-band, the next sync could start a second in-band transfer of the same regions while the first was still arriving. The two mixed their pieces and the client then failed to read the region ("incorrect header check"), so that LOD never showed.
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:4BeAEBIb:w06pjl0h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BeAEBIb:w06pjl0h"
}
