Tags
Creators
Details
1.7.3
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update adds Radiant box support and improves compatibility with both Cobblemon 1.6.1 and Cobblemon 1.7.3.
Fixed
- Fixed the Upgrade button overlapping Cobblemon 1.7.3 native PC UI elements
- Fixed Radiant Pokémon not having a dedicated special box category
- Fixed Radiant Pokémon being sorted into non-Radiant categories
- Fixed UI alignment issues caused by the updated Cobblemon 1.7.3 PC interface
Added
- Added dedicated Radiant boxes
- Added Radiant support to the PC box mapping system
- Added Radiant support to automatic Pokémon sorting
- Added Radiant support to
/cpe sort now - Added Cobblemon version detection to better adapt CPE behavior depending on the installed Cobblemon version
Changed
- Changed the box layout to include Radiant boxes after Shiny boxes and before Free boxes
- Changed automatic sort priority to support Radiant Pokémon correctly
- Changed the Upgrade button placement for Cobblemon 1.7.3 to avoid overlapping the native Cobblemon PC search and rename UI
- Changed the Upgrade button icon to a cleaner and more readable compact arrow icon
Improved
- Improved compatibility with Cobblemon 1.7.3 while keeping support for Cobblemon 1.6.1
- Improved PC UI integration with the newer Cobblemon PC interface
- Improved box mapping, naming, and search behavior with the new Radiant box category
- Improved wallpaper and Auto Type behavior around special box categories
- Improved persistence checks for names, wallpapers, box layout, and sorting behavior
Notes
- CobblePCEnhanced 1.7.3 has been tested with Cobblemon 1.6.1 and Cobblemon 1.7.3
- Radiant sorting requires Pokémon to have the
radiantaspect - A small wallpaper polish is planned for a future hotfix: Auto Type should preserve manual wallpapers on Alpha, Shiny, Radiant, and Free boxes
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:U25IwyZp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oqnWAgL4:U25IwyZp"
}

