
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
3.17.2+26.1
Compatibility
Required content
Changes
Changed
-
The 26.3 build now targets
26.3-pre-2. Chunksmith pins its 26.3 jar to one exact Minecraft build rather than a range, becausepack_formathas moved on nearly every 26.3 build and a jar carries exactly one. 26.3-pre-2 shipped the same day this release was prepared, so the jar targets it rather than going out already a build behind.pack_formatis unchanged at 97 -- read from 26.3-pre-2's ownversion.json, not assumed.Nothing else differs between the two builds for this mod: the only Minecraft change on a surface Chunksmith attaches to was
ServerChunkCache.tickChunkslosing a parameter, and Chunksmith does not hook that method.
Fixed
-
The world no longer runs on underneath the "Preparing your world" screen. The progress screen drew a panel in the middle and left the live world rendering behind it at full brightness, so you could watch yourself standing there -- and, if the spawn was not flat ground, watch yourself fall. It reads as though the freeze is not working. It was: Minecraft's tick freeze deliberately exempts players, so everything else really was held while the player alone kept moving. The screen is a full backdrop now, and there is nothing to misread. (mod_support #20, reported by Maker261)
-
You are no longer the only thing still ticking while your world pre-generates. Because of that same exemption, the player kept running for the whole freeze -- which is 80 minutes or more at the default radius. Hunger drained, fall damage applied, and a spawn over water could drown you while you watched a progress bar. The player is now frozen along with everything else until the run finishes or you press Enter World Now, and is released with the rest of the world.
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:2TZ3Svm2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4BeAEBIb:2TZ3Svm2"
}
