Tags
Creators
Details
N-2.2.5-Beta.4-Hotfix.1
Compatibility
Changes
NOTE: I did NOT test Fabric & NeoForge on servers, only on Clients. Gathering Chunks for Minecraft 26.1 & 1.21.11 is coming soon. There are a lot of API changes, which means I'll take a while to fully port the mod to those versions leading up to the 2.2.5 Release.
Available on Fabric and NeoForge
Bug Fixes
-
Player Spawn Persistence: Fixed an issue where reconnecting players would always revert back to the initial spawn chunk after a server restart. Spawn states are now properly persisted.
-
Dimension Generation: Added saving for custom dimension generation configurations, ensuring original source dimensions are remembered across server reloads.
-
Chunk Eraser Textures: Resolved the broken pink-and-black missing textures for the Chunk Eraser block-item in inventory views on both Common and Fabric.
-
Mushroom Chunk Spawner Recipe: Fixed the broken recipe that made the Mushroom chunk
Changes & Improvements
Internal Cleanup Removed old, legacy Pale Garden spawner assets.
Known Issues
The following issues are known and being tracked for the stable release:
- Performance: The mod may cause slowdowns on low-end CPUs.
- World Scanner: Manual scan mode can occasionally stall or fail to complete. Restarting the scan usually resolves it.
- Dimension Sync (Nether/Overworld): Rare desync events or failed chunk transfers between dimensions are still possible.
- Ocean Chunk Spawner: May not behave as intended in all cases, occasionally spawning land chunks instead of ocean chunks.
If you feel any recently added feature does not fit the direction of the mod or feels out of place, feedback is genuinely appreciated. The goal is to keep Gathering Chunks focused and high quality.
Found a bug or crash? Please report it here with as much detail as possible, including logs.
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:h2cEfp4R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UgEJpudA:h2cEfp4R"
}

