
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.32.0+fabric
Compatibility
Required content
Changes
Servers can now install CobbleDex themselves, so players see the server's spawns, tutor moves and evolutions without having its datapacks.
Added
- Drop the same jar into a dedicated server's mods folder (Fabric or NeoForge) and it shares the data Cobblemon doesn't sync with players who have CobbleDex: spawn pools, species files, habitat pools. That brings spawns, tutor and legacy moves, evolutions, catch rates, egg groups and "Added by" names for Pokémon the server added.
- Players only download what they don't already have, around 0.4 MB on a big pack list, and the client keeps a copy so reconnecting is instant. Players without CobbleDex aren't sent anything, and servers without it work as before.
config/cobbledex-server.jsonon the server lets you turn it off, limit it to operators, or hide species and files./cobbledex statsshows whether the server sent data.
Changed
- On a server that has CobbleDex, Spawns and Evolutions no longer show the "local files only" warning, and the "tutor moves unknown" note is gone.
- The Fabric jar now loads on dedicated servers too. It does nothing there unless the sync is used.
Fixed
- REI's Pokémon list could be empty on a server. REI sometimes loaded before CobbleDex had its data and never tried again. CobbleDex now asks REI to reload once the data is ready.
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:2HsfZCoS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qekxLrOP:2HsfZCoS"
}
