All versions
1.2.1
Release
Cobbleboost 1.2.12 weeks ago 515
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Changes
CobbleBoost 1.2.1
🆕 Cobblemon 1.8 support
- Now works with Cobblemon 1.8.x (including 1.8.1). Cobblemon 1.7.x is still supported.
🐛 Bug fixes
- Fixed distant Pokémon disappearing completely at the low detail level. The LOD system now only hides small details and never removes a Pokémon's main body.
- Fixed distant Pokémon taking other Pokémon's poses. A far-away Charizard could copy the pose, and even the head position, of a nearby Pikachu. Each Pokémon now keeps its own pose.
- Fixed LOD having no effect on distant Pokémon while animation throttling was on.
- Fixed LOD making parts visible that Cobblemon had hidden on purpose, for example alternate eyes or accessories.
- Fixed particle effects never ending when the spawn rate was set to 0%, which also kept them in memory.
- Fixed the hurt flash sometimes showing on the wrong Pokémon when animations were throttled.
- Fixed texture pre-caching never actually running. It now loads the right textures.
- Fixed the packet throttle never activating in-game. Queued packets are now always sent in their original order and are never dropped.
⚡ Improvements
- Smoother animation throttling: distant Pokémon no longer freeze completely. They animate less often the farther away they are, from every 2nd frame up to the "Max Throttle Interval" setting, which used to do nothing.
- Better particle limiter: it now reduces the number of particles an effect spawns instead of slowing the whole effect down, so moves still play for their full duration. "Max Particles Per Effect" now caps live particles (new default: 64).
- Texture pre-caching now covers addons and resource packs, skips shiny textures to save video memory, and loads gradually so the loading screen doesn't freeze.
- Faster LOD checks: bone decisions are cached instead of being recalculated every frame.
- Updated setting tooltips (English and Italian
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:UnZwG5gK:L8shWg16"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UnZwG5gK:L8shWg16"
}

