Tags
Creators
Details
Licensed MPL-2.0
Published 3 years ago
Updated 5 months ago
All versions
1.4.0
Release
Cobblemon Placeholders 1.4.05 months ago 1,809
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Any compatible version
Changes
- Removed the
pokedex_shinies_caughtandpokedex_shinies_seenplaceholders as they are not working as intended. They may return in the future if a workaround is found/made.- You may be able to use the placeholder that fetches a player statistics and use the Cobblemon statistic that tracks shiny catches. This is not a perfect replacement, but it may work for your use case.
- Added
party_scale_modifierplaceholder that will fetch the value of a given Party Pokemon's scale modifier value (<cobblemon_party_scale_modifier:[slot]>/%cobblemon:party_scale_modifier [slot]%) - Added 2 new Pokemon Property related placeholders:
<cobblemon_party_property_has:[slot]:[property]>/%cobblemon:party_property_has [slot]:[property]%- Checks a player's Party Pokemon in the specified slot for the given property and returns true or false depending. Ex:<cobblemon_party_property_has:1:unbreedable=true><cobblemon_party_property_get:[slot]:[property]>/%cobblemon:party_property_get [slot]:[property]%- Gets the value of the given property for the player's Party Pokemon in the specified slot. Ex:<cobblemon_party_property_get:1:unbreedable>
- Added an alias
party_tradeableforparty_tradableplaceholder - Fixed the
species_abilitiesplaceholder returning bad results for slots 1 and 2 sometimes. These slots were not being filtered for non-hidden abilitites, so they would sometimes return the hidden ability.
Need help? Join the Discord: https://discord.gg/cgBww275Fg
Optional dependencies
Any compatible version
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:Y62OLgNG:yGqB77nU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Y62OLgNG:yGqB77nU"
}

