Tags
Creators
Details
1.1.1+cobblemon1.7.3
Compatibility
Required content
Changes
For Cobblemon 1.7.x. If you are on Cobblemon 1.8.x, download the +cobblemon1.8 file instead.
Fixes the legendary protection in the release review, on the premium build.
Excluding legendaries in the release rule did nothing, so a legendary could appear in a release list with that protection switched on. Shiny, held item and nickname protections were never affected, since those live on the Pokemon itself rather than on its species.
The cause is that Cobblemon keeps legendary, mythical and ultra beast status in species labels, and a client is not sent those labels, so asking Cobblemon directly always came back negative. The mod now reads them from the species files, the same source already used for evolutions and learnsets, and loads that when you join a world.
Nothing else changed. On the free build this release is optional.
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:LgXCSq0w:DXUa8KWe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LgXCSq0w:DXUa8KWe"
}

