Tags
Creators
Details
All versions
0.16.11-beta
Beta
Version 0.16.11-beta11 months ago 944
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Changelog
Note that the latest 0.16 version only supports Cobblemon 1.6. Version 0.17 is coming soon.
[0.16.11-beta] - 2025-11-22
Added:
- #348 Data pack property
initialLevelCapandrelativeLevelCapfor series: Overwrites the global config value for a series if set - #347 Data pack property
relativeLevelCapfor trainer mobs: Overwrites the global config value and series property for a trainer if set
Changed:
- #346 Commands
trainer get required/reward_level_capnow require a player selector argument - #345 Renamed server config
additiveLevelCapRequirement->relativeLevelCap(the option will reset to its default value0) - #344 Replaced some log errors with warnings
- #343 Trainers (that have the appropriate loot table) may now only drop an
Ancient Origin Ballafter their first defeat and this is only possible for trainers with pokemon at or above level50(the item was originally considered to be removed) - #342 Trainers will no longer refuse battles against players with a lower level cap than the trainer level (they will still refuse for other reasons, e.g. carrying pokemon above the level cap or missing defeats against other trainers)
Fixed:
- #341 Adjusted displayed level caps in various locations (e.g. trainer card) to better reflect the actual progression of a player
- #340 Inconsistencies if trainers depend on others from different series (these dependencies are now ignored and a warning is printed to the log)
- #339 Omitting (optional)
titleordescriptionin series metadata causing a crash - #338 Visual bug in legend of generated progression graphs for series (plantuml)
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:lRwTUnD7:gDi9xzH1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lRwTUnD7:gDi9xzH1"
}

