
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.2+1.21.10-neoforge
Compatibility
Changes
Fixed
-
Pregeneration silently generated nothing when C2ME was installed (Fabric, all versions). Reported as mod_support #13 on Minecraft 1.21.1 Fabric: Chunksmith reported thousands of chunks generated, in effectively zero seconds, and no terrain was written. Every Fabric build from 3.2.0 onward was affected on every Minecraft version, not only 1.21.1.
Root cause: 3.2.0 propagated the C2ME ticket-race guard fleet-wide, which correctly skips the forced
runDistanceManagerUpdates()call when C2ME is present. But that call is also what builds theChunkHolderfor the chunk ticket Chunksmith had just added, and the follow-upgetChunkFutureMainThread(x, z, FULL, create)was still being passedcreate = false. With no holder and no permission to create one, it returned an immediately-completed FAILEDChunkResult("unloaded chunk"). A failedChunkResultis not an exception, so the completion callback saw a null throwable, released the ticket, and counted the chunk as finished. The result was a pregen that reported complete success at impossible speed while doing no work.Fix: when either C2ME or Moonrise is present,
getChunkFutureMainThreadis now allowed to create the holder itself (create = true). The forced distance-manager call stays skipped under C2ME, so the 3.1.5 ticket-race crash fix is preserved. Moonrise already used this exact mechanism for the same underlying reason.Verified by disk state rather than by Chunksmith's own progress counter: a fixed 4225-chunk selection now writes 4225 chunks at
minecraft:fullinto the region files with C2ME installed, matching the no-C2ME control exactly. Before the fix the same selection wrote 49.
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:J8zDMRDx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BeAEBIb:J8zDMRDx"
}
