Tags
Creators
Details
N-2.2.5-Beta.5-Hotfix.1-Dev.3
Compatibility
Changes
Gathering Chunks - 2.2.5 Beta 5 - Development Snapshot 3
THIS IS AN ALPHA BUILD WHICH MEANS THAT IT IS NOT READY FOR PRODUCTION! This is the first version for Minecraft 1.21.11, so bugs are expected. Back up your worlds before testing!
New features
- Minecraft 1.21.11 support: Ported to 1.21.11.
- World-specific settings: every world now has its own settings file. You can configure them using the new GC Settings button when creating a world.
- New settings menu: access Debug and Performance options from the main menu.
- Better spawn themes: your starting theme now matches the biome you spawn in.
Fixes
- Ocean chunks fixed: ocean spawners now generate actual ocean chunks.
- No more repeated starting spawns: restarting a world no longer repeats the initial spawn.
- Chunk loading fixes: fixed several issues that could leave chunks loaded or stop spawning from finishing.
- Scanner coordinates fixed: the World Scanner and Cave Scanner now show the correct chunk coordinates.
- Server lag reduced: fixed a major ChestTracker issue that could freeze the server.
Performance
- Chunk copying is 25 to 30% faster
- Starting spawn search is around 75% faster
- Less background work: the progression helper and rain filling system are now more efficient.
Important notes
- World settings: most settings become locked after world creation. Some options remain editable, and certain changes only affect newly generated chunks.
- Server settings: multiplayer clients automatically receive the server's settings.
- Slow server warning: creating a world on a very slow machine may cause the server to time out while searching for the starting spawn. Disabling the server watchdog with
max-tick-time=-1inserver.propertiesis a possible workaround.
Known issues
This is an early alpha, so bugs and compatibility issues are expected. Please report anything unusual!
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:UgEJpudA:9RD1wvRB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UgEJpudA:9RD1wvRB"
}

