All versions
0.3.3
Beta
Cobblemon: Ride On! v0.3.3 for Fabric 1.21.1last year 1.17M
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- Fixed crashes that occurred with mods such as the Aether, where Whirlwinds invoke the "getPassengerRidingPosition" method of a Ride Pokemon. This was an instance of a non-passenger entity fetching a passenger attachment point, which was an unexpected occurrence that caused out-of-bounds index errors. This oversight has been addressed, meaning you can safely steer your Pokemon into billowing cyclones without worry of your server imploding.
- Fixed issues related to debug keybinds that were interfering with other keybinds even when "client.useDebugKeys" was disabled. Keybindings have been more closely aligned to how they are implemented in Cobblemon, which should reduce the likelihood of these issues moving forward.
- Restored ability for mounts to gradually turn with the player, like before v0.3.0. This issue arose after a switch to lerp functions based on the Mth class in Minecraft, which provides better stability and support for averaging between two rotations. But I goofed and set the lerp to use 100% of the player's rotation instead of the 50/50 that was used before. Sorry about that!
- Marked CobblemonRider and Cobblemon 1.7+ as incompatible with this mod for Fabric and NeoForge. Trying to run either mod/version alongside this one will now result in a crash.
- Some people are probably going to be mad with me for this change, but this was made with two intentions. One, this will stop people from trying to run this mod alongside CobblemonRider; these mods are not compatible and only interfere with one another when used at the same time, so this is meant as a hard stop to discourage any further attempts to mix the two mods. Second, this will head off any attempts to run this mod with Cobblemon 1.7 after it releases; the upcoming version will change a lot of files, in addition to adding its own riding system, so it's just cleaner and safer to make sure this mod is marked as 100% incompatible with the newer version so that people will remember to remove this mod once 1.7 is out.
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:Ts9Wi7Kt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vXREhDPP:Ts9Wi7Kt"
}


