All versions
0.4.1
Release
Cobblemon Mount Mastery 0.4.1last month 341
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
Bug Fixes
- Training wasn't actually training. Flying, Running and Swimming were supposed to boost your Pokémon's stats the more you rode, but a bug meant that never happened, for anyone, ever. Fixed. You'll now see real stat bonuses and level-ups while riding.
- Riding Pager could go blank while mounted, showing none of your stats even though everything was fine. Fixed.
- Training could get stuck at 100% and never level up. Some Pokémon would hit a full bar and just stay there forever, no matter how much further you rode. Fixed.
- The Summary screen's progress bar didn't move, even though the level number next to it updated fine. Fixed, the bar fills up properly now.
- Turning training off could still let Stamina build up in secret, handing out a free level the moment it got turned back on. Fixed.
- Server-wide speed settings didn't speed up Friendship gains, leaving them behind if a server sped up training. Fixed.
- Cleaned up the config HUD, using a table structure to display the buttons and gain more screen space.
New Features
- Riding now builds real Friendship. Once you've trained a style past level 20, keep riding that Pokémon and its actual Friendship stat climbs too, which helps its Stamina grow faster.
- The Daily Quests window remembers where you left it. Hide it, move it, and it stays that way next time you play.
Balance Changes
- Training and Stamina both take about twice as long to fully max out now, so leveling up feels like more of an achievement.
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:THkyAcSA:2U3HZdjK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:THkyAcSA:2U3HZdjK"
}

