Links
Tags
Creators
Details
2.0.0
Compatibility
Changes
Reworked core chunk spawning system
The new system now coordinates chunk spawns to improve performance, ensuring only a single chunk is spawned at a time. Chunk spawning is now better spread across multiple ticks to improve performance, with the rate at which they are spawned controlled by a new chunk layer spawn rate configuration option - which specifies the number of y layers of a chunk to spawn each tick, up to 512. The default is 8, and it may be sensible to lower this if chunk spawning is causing performance issues.
This rework is a breaking change for existing worlds, but should be safe to update as long as the world is not in the process of spawning a chunk when the update is applied.
Features
- The World Mender will now spawn chunk by applying the type of chunk spawner provided to it - including unstable chunk spawners and biome themed chunk spawners.
- The rate at which the World Mender spawns chunk is now configurable, defaulting to as fast as possible. It will not spawn chunks while a chunk spawn is in progress.
- Added a new Generate Line World option. If enabled, the world will spawn all chunks along a line from spawn. Using this setting will disable settings that select a spawn point.
- The biome for unspawned chunks can now be set as part of sky dimension data packs.
- A covering block (e.g. snow) can now be set as part of sky dimension data packs.
- The number of initial chunks can now be configured up to 100.
- Tweaked recipe unlocks and advancement order.
Bug Fixes
- Fixed a crash when entities are spawned as part of a chunk spawn in the nether.
- Fixed unreliability in the spawning of villagers and other entities when spawning a chunk.
- Spawning chunks now replace snow in the original chunk.
Optional dependencies
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:ZVZyInUU:ZYNNRqsD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZVZyInUU:ZYNNRqsD"
}

