Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last year
All versions
0.2.3
Beta
Cobblemon: Ride On! v0.2.3 for Fabric 1.21.1last year 32.3K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
"Sorry to keep you waiting."
- Fixed bug where loading a Pokedex where a Pokemon with multiple forms is listed - but where none of the currently visible forms are in that dex (e.g. if you had normal Exeggutor but not Alolan and tried to access the Alola dex) - would cause a crash.
- Fixed bug where certain mods would not work well with Ride On! due to improperly-coded network mixins. This primarily affected Mega Showdown. (Thanks to Yakat_Kaul, the dev of Mega Showdown, for helping debug this one.)
- Fixed bug where evolving a Pokemon would not correctly update its move behaviours. This would cause Pokemon that obtained rideability or whose ride behaviours changed post-evolution to not work as intended.
- Reverted behaviour for mounting such that right-clicking while holding an item will no longer trigger a mount. This is intended to resolve issues where some items, particularly those which built atop the Item class in Minecraft (such as Mega Showdown items), would be overridden by the user mounting their Pokemon instead. While this change effectively means you cannot mount Pokemon anymore unless you have an empty hand, I've decided that this will be the better solution for now to ensure that other mods and their items work as intended. This change is a temporary compromise until the next major update, when planned changes will make this issue obsolete.
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:vXREhDPP:cHdWCZhW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vXREhDPP:cHdWCZhW"
}


