Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 5 months ago
All versions
1.1.0
Release
CobblemonChunkmenager 1.1.05 months ago 1,367
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
CobbleChunkManager v1.1.0 — Patch Notes
Ghost Pokémon Fix
- Fixed a major issue where Pokémon in cold chunks would become unresponsive and impossible to interact with (no battles, no catching). The mod now detects players in real-time and instantly re-enables Pokémon AI when you're
nearby — no more frozen Pokémon standing around ignoring you.
Safer Entity Migration
- Pokémon moved to other chunks by the budget system now properly appear and remain fully interactable at their new location. Previously, migrated Pokémon could sometimes become invisible or unclickable.
- The system no longer accidentally migrates or despawns your owned Pokémon or Pokémon that are currently in battle. If something goes wrong during a check, the mod now plays it safe and leaves the Pokémon alone.
Smarter Budget Enforcement
- Entity counts now update immediately after a migration or despawn, preventing the system from over-aggressively removing Pokémon from a chunk that was already handled.
- Spawn blocking is now fail-safe: if something goes wrong during a spawn check, the spawn is denied rather than allowed, keeping chunk populations under control.
Performance
- AI throttling now uses graduated tick intervals (configurable for HOT/WARM/COLD chunks) instead of a simple on/off switch, giving smoother performance scaling without sacrificing gameplay.
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:B5Oa5DCX:10eDaCP2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B5Oa5DCX:10eDaCP2"
}

