Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated last month
All versions
1.2.0
Release
CobblemonChunkmenager 1.2.0last month 355
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
CobbleChunkManager 1.2.0
Requirements
- Cobblemon 1.8.0 or newer (Minecraft 1.21.1, Fabric)
- Fabric Language Kotlin 1.13.6 or newer
New
- Works with CobbleOptimizer. If CobbleOptimizer is installed, C freezing to it, so the two mods no longer conflict. ChunkManageralso respects CobbleOptimizer's despawn protections (species blacklist, NPC Pokémon, spawn grace period). You can change the AI behaviour with the deferAiToCobbleOptimizer config option.
- Despawn protection. Shiny, Alpha, Legendary, Mythical and Ultra Beast Pokémon are never despawned by the chunk budget. Each one can be turned on or off in the config.
- New command /ccm unfreeze. It wakes up wild Pokémon that older versions left frozen in your world. Run it once after updating.
Fixes
- Pokémon no longer stay frozen after their chunk unloads, the server restarts, or the mod is removed.
- Pokémon near a player are no longer frozen, even when the play
- NPC Pokémon, persistent Pokémon, and Pokémon that are ridden or on a leash are no longer moved or frozen.
- NoAI set by map makers or other mods is no longer removed.
- Pokémon are no longer moved into lava, into fire, inside blocks, or into chunks where they can't move.
- Chunk budgets now work properly on large servers: chunk data rs are counted right away. Herds and bursts of spawns no longer goover the limit.
- Spawn chunks are now managed.
- Pokémon on a chunk border are no longer counted twice.
- Nearby chunks were sometimes skipped when looking for a place checked now.
- Dimensions no longer interfere with each other's data.
- Despawned Pokémon no longer leave invisible "ghost" Pokémon on
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:2uv6Vv55"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B5Oa5DCX:2uv6Vv55"
}

