All versions
1.5.0
Beta
Cobblemon Detail Viewer 1.5.08 months ago 297
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Changes
- Added a new split-panel HUD, while still allowing users to fall back to Jade if they don’t like the new style.
- The Custom HUD and PC HUD can both be toggled on in the settings so users can visually see their changes as they configure options.
- Added a priority-based ordering system for fields. If two fields share the same priority then it falls back to sorting alphabetically.
- Users can now control how many fields are shown on the left panel before splitting the remainder to the right panel.
- Added a setting that allows users to customize the color of the divider bars.
- Users can now toggle field labels on/off independently for the Custom HUD and PC HUD.
- Added two new settings that allow users to individually control the size of the PC icon and Poké Ball.
- Users can now customize the number of sprites displayed for Health and Armor.
- Users can now view the level of all Pokémon.
- Users can now view the type(s) of all Pokémon, and switch between text, icons, or both.
- Users can now view the Tera type of only their own Pokémon, and switch between text, icons, or both.
- Added gender characters that display next to the Pokémon name, but can be switched back to the text value as well.
- Users can now view all marks of their Pokémon, and the active mark of wild Pokémon or Pokémon owned by another player. (Unconfirmed: I do not think that wild Pokémon will spawn with an active mark, so this may not appear.)
- Fixed the Owner field and made it follow the same standards as other fields.
- Updated the license.
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:qHpht0Ug:DyKM1BEg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qHpht0Ug:DyKM1BEg"
}

