Tags
Creators
Details
1.7.5
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update adds compatibility with Cobblemon 1.8.0 and 1.8.1, improves Pokémon storage safety, and ensures existing CobblePCEnhanced features continue to work with the latest supported Cobblemon versions.
Added
- Added compatibility with Cobblemon 1.8.0 and 1.8.1
- Added storage safety checks when reducing the number of PC boxes
- Added information about boxes that must be emptied before reducing storage capacity
Changed
- Updated CPE to support changes introduced in newer Cobblemon versions
- Updated dependencies and accepted Cobblemon versions
- Preserved compatibility with previously supported Cobblemon versions
Improved
- Improved Pokémon storage safety when reducing PC capacity
- Improved detection of boxes containing Pokémon before storage reduction
- Improved Pokémon preservation during transfers, automatic sorting, and world reloads
- Improved compatibility with Cobblemon 1.8.0 and 1.8.1 while keeping existing PC features functional
Notes
- Tested successfully with Cobblemon 1.8.0 and 1.8.1, including PC navigation, Pokémon transfers, upgrades, automatic sorting, search, box renaming, and custom wallpapers
- Remote PC access and Pokémon transfers were validated for non-OP players
- Pokémon storage and customizations were verified after closing and reloading the world
- Alpha and Radiant integrations depend on the compatibility of their respective optional mods
- Full Radiant integration compatibility with Cobblemon 1.8.0 and 1.8.1 has not yet been validated
- Supported Cobblemon versions:
1.6.1to1.8.1 - Minecraft
1.21.1— Fabric
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:oqnWAgL4:AA5NYI95"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oqnWAgL4:AA5NYI95"
}

