
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.3+1.21.8-neoforge
Compatibility
Changes
Added
- Pregeneration now verifies its own work. A chunk counted as "generated" was only ever a
claim: the counter is incremented when the load future completes, and a future can complete
having done nothing at all -- which is exactly how 3.2.2's C2ME bug went unnoticed for two
releases while every counter and log line reported success. At the end of a run Chunksmith now
takes a spread of up to 32 chunks it says it generated and asks the world whether they are
actually on disk. If any are missing it says so loudly, with the count and example coordinates,
instead of reporting a clean finish. Costs at most 32 status reads, once, per run.
- Deliberately quiet when it cannot get an answer (busy or shutting-down server): only a definite "not on disk" is ever reported. A check that cries wolf gets ignored.
- The end-of-run drain now happens for every task rather than only LOD-enabled ones, so a task no longer declares itself finished while its own dispatches are still outstanding. Previously a non-LOD run could under-report by up to the dispatch limit.
Changed
- MC 26.3 rebuilt onto
26.3-snapshot-7(was snapshot-6), Fabric API0.156.2+26.3,pack_format95 (was 94). Every 26.3 snapshot so far has bumped the resource pack format by exactly one, so each build is snapshot-exclusive by design --3.2.2+26.3remains available and listed for snapshot-6.
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:lz9m9sD0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BeAEBIb:lz9m9sD0"
}
