
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.
Links
Tags
Creators
Details
3.2.0+1.21.10-neoforge
Compatibility
Changes
Added
- Universal LOD generation on the Bukkit/Paper/Folia plugin. The plugin line previously
shipped with LOD generation hardcoded off; it now generates LOD data by default, matching
the Fabric/Forge/NeoForge behavior, using the same pregen-time hook the mod side already
used. No configuration needed --
lod-enabled: falsestill turns it off for admins who want pregen without LOD.
Fixed
- Housekeeping-hook stall under a large chunk-unload backlog (issue #11). The shared
per-tick housekeeping mixin (every Fabric/Forge/NeoForge cell) called
chunkMap.invokeTick(() -> true), discarding vanilla's real per-tick time budget (haveTime, already passed in and unused) and letting the unload loop run with no time limit every tick. A backlog of 13k+ chunks pinned the server thread for over 50 minutes CPU time on one reported world. Fixed by passing the realhaveTimethrough -- shared plumbing, so every cell picks up the fix automatically. Load-tested 62.5 minutes continuous on the exact reported configuration (144,433 chunks processed, zero stalls) and boot-verified across the rest of the matrix. - Plugin:
IncompatibleClassChangeErrorextracting LOD biome data on some Paper builds. Bukkit'sBiometype changed from a class to an interface across Paper API generations within the same Minecraft version line; a plugin jar compiled against one shape could throw at runtime against a server built against the other. Fixed by resolving the biome through the stableorg.bukkit.Keyedinterface instead of the concreteBiometype, and by making LOD extraction failures fail loud (logged) instead of silently doing nothing, so a bug in this class can't hide again. - C2ME compatibility guard was only wired into one Fabric cell. A ticket-race workaround for running alongside the C2ME concurrency mod (added for Fabric 1.21.11 in 3.1.5) is now applied on every Fabric/Forge/NeoForge cell. No behavior change where C2ME is absent -- Forge and NeoForge never set the detection flag that arms it.
Changed
- Version numbering reconciled fleet-wide. Every cell (Fabric, Forge, NeoForge, and the
plugin, across every supported Minecraft version) now reports
3.2.0. Previously the plugin tracked3.1, most mod cells tracked3.1.1, and two cells (Fabric 26 and Fabric 1.21.11) had drifted ahead to3.1.4/3.1.5on earlier fixes that never got a version bump recorded here.
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:7nRRs69U"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BeAEBIb:7nRRs69U"
}
