
Cobblemon Info for REI / JEI / EMI
Cobblemon Info for REI turns REI, JEI, or EMI into a full in-game Cobblemon reference. Click a Pokemon and inspect its spawns, evolutions, drops, moves, stats, forms, fossils, obtainment methods, riding data, and more without leaving the game.
Tags
Creators
Details
2.31.2+fabric
Compatibility
Required content
Changes
TM and egg moves and evolutions for things that only exist on a server, plus a batch of form fixes.
Added
- TM and egg moves for forms and for Pokémon the server added, on Cobblemon 1.8 and newer. Forms on a server used to show their base species' lists, and added Pokémon showed none.
- Evolutions for Pokémon the server added, on Cobblemon 1.8.2 and newer. The requirements read the way Cobblemon words them.
- The overview page says tutor moves are unknown when you're on a server. Cobblemon never sends them, so an empty list doesn't mean the Pokémon learns none.
/cobbledex statstells you whether TM/egg moves and the evolution info came from the server.
Fixed
- Forms that are two things at once overwrote each other. Alolan Mega Marowak replaced Alolan Marowak, and the same thing happened with the Hisuian Typhlosion and Zoroark Megas, Galarian Darmanitan and its Zen mode, and the three Paldean Tauros breeds. Each has its own entry now.
- Unown's ! and ? forms were treated as one form.
- Type: Null couldn't be found. The colon in its name was read as a mod prefix, so its spawns and Resurrection Machine recipe never attached to it.
- Zygarde's 10% and 50% forms showed "Format error: cobblemon.ui..." where the name should be. Any form with a % in its name did that.
- Cherrim's Sunshine form had no entry because its stats match the base form. A form with an aspect of its own gets an entry now.
- Costume forms with a number on the end (costume2, costume3) were listed as real forms.
- When hosting a world yourself, spawns that pick their variant through a feature, like Vivillon's wing patterns, lost the variant. A plain on/off variant showed as "True" instead of its name.
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:qekxLrOP:CZjl3KnO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qekxLrOP:CZjl3KnO"
}
