All versions
0.4.1.1
Release
0.4.1 - NeoForgelast month 83
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Client and server
Required content
Unavailable version
Changes
v0.4.1.1 - First NeoForge Release
Cobblemon Mount Mastery is now on NeoForge! Same mod, same features you already know from Fabric, now on your NeoForge server too.
What Mount Mastery Does
- Riding trains your Pokémon. The more you fly, run, or swim on a Pokémon, the more its actual riding stats improve, real gains, not just a number going up.
- Stamina grows too, so mounts can keep going longer before needing a rest.
- Riding a well-trained Pokémon also builds its Friendship, on top of the usual ways to bond with it.
- The Riding Pager shows you exactly where a Pokémon stands, right-click it to see its stats, or hold the Pager while riding for a live readout.
- Upgrade Berries and Stamina Berries let you speed things along by hand, feed one to give an instant boost.
- Daily Quests, Achievements, and a Distance Relay give you extra goals and rewards for riding.
- Full in-game settings, tune the pace of training server-wide, or set up different rules per Pokémon species, all from a menu, no config file editing needed.
Requirements
- NeoForge for Minecraft 1.21.1
- Cobblemon 1.8.0 or newer (the NeoForge build of Cobblemon)
Good to Know
- Training is turned off automatically in Creative and Spectator mode, so testing or building won't accidentally rack up progress.
- Upgrade Berries only ever raise training (Flying/Running/Swimming). Once a Pokémon's training is fully maxed, an Upgrade Berry has nothing left to do for it, Stamina only comes from the Stamina Berry or from riding a Pokémon whose Friendship is already maxed out.
Optional dependencies
Any compatible version
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:gNiqCzya"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:THkyAcSA:gNiqCzya"
}

