All versions
1.2.2
Release
Cobbleboost 1.2.2last week 596
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Changes
CobbleBoost 1.2.2
🆕 Cobblemon 1.8.2 support
- Now works with Cobblemon 1.8.2. Cobblemon 1.7.x and earlier 1.8.x versions are still supported.
🧠 New: Memory Saver
- Unload Unused Pokémon Textures: frees the memory used by textures of Pokémon you haven't seen for a while (default: 5 minutes, adjustable from 1 to 60). They reload automatically when that Pokémon shows up again. This helps most on PCs with integrated graphics, where video memory is shared with system RAM.
- New
/cobbleboost memorycommand: immediately frees textures of Pokémon that aren't on screen and shows your current RAM usage and how many Pokémon textures are loaded. - Memory Saver is off by default. Turn it on in the new "Memory Saver" category of the config screen. While it's on, texture pre-caching is skipped, since pre-caching does the opposite.
🐛 Bug fixes
- Fixed being pulled back after a teleport while the packet throttle was holding back movement packets.
- Fixed Pokémon briefly showing the wrong pose after evolving or changing form, or after switching worlds or servers.
- Fixed a crash when opening the config from Mod Menu without Cloth Config installed. The config button is now hidden in that case.
- Fixed the config screen saving invalid LOD distances (medium distance greater than or equal to low distance). Values are now corrected on save.
⚠️ Notes
- Cobblemon 1.8.2 requires Fabric Loader 0.17.2+ and Fabric API 0.116.6+. Update those too if you update Cobblemon.
- With Memory Saver on, you may notice a tiny hitch the first time you see a Pokémon again after its texture was freed.
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:LlGoQx60"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UnZwG5gK:LlGoQx60"
}

