All versions
1.0.4
Release
Cobblemon Cards 1.0.4last week 335
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Unavailable version
Changes
📝 Changelog: v1.0.4
🐛 Bug Fixes
- Right-Click Menu Crash (
IndexOutOfBoundsException): Fixed a server/client desync crash that occurred when right-clicking a Master Album in your hand while having a regular Binder equipped in your accessory slot. The menu logic now strictly differentiates between hotkey presses (which check the accessory slot first) and direct item interactions (which strictly open the clicked item). - Grainy Terrain / Mipmap Rendering Bug: Fixed a major visual issue where distant terrain (especially tree leaves) appeared shimmering or pixelated when the mod was installed. This was caused by irregular texture dimensions (like
40x30or22x31) forcing Minecraft's texture atlas to drop the mipmap level from 4 to 0. All affected textures have been padded with transparent space to reach multiple-of-16 dimensions (e.g.,48x32,32x32), restoring smooth distant rendering.
🎨 UI & Visual Polish
- GUI UV Mapping Adjustments: Updated the internal rendering code to perfectly offset the new transparent padding applied to the textures. Cards and Pokémon icons will continue to render exactly at their intended sizes without any visual shifting or misalignment.
- Shiny Sprite Cleanup: Removed the semi-transparent orange aura/glow artifacts from Shiny Pokémon icons (commonly found in HOME or newer generation sprites), giving them a much cleaner, authentic pixel-art look inside the binders.
- Icon Standardization: Cropped and centered oversized Pokémon icons to ensure all sprites fit perfectly inside the designated
40x30card slots without overflowing the UI.
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:9asBGJMf:O1OunsSQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9asBGJMf:O1OunsSQ"
}

