1.4
Compatibility
Required content
Changes
- Added Partner variants for every Legendary Pokémon.
- Just like Partner Magikarp and Partner Abra, Partner Cosmog and Partner Cosmoem also now learn attacking moves so that they can actually do something in battle.
- Mega-capable Partner Pokémon now have the "Dynamax Blocked" flag to prevent them from being capable of Dynamaxing (even though it isn't in the game yet) so that you don't end up getting into a situation where you have a Dynamaxed Mega Partner Pokémon.
- This also applies to Pokémon that have Mega-like transformations (excluding Battle Bond) so they also can't use Dynamax when they use said transformations.
- Partner Mew now has a slightly increased walking speed than it did before.
Side note: If you're using a mod that allows you to ride your Pokémon, like CobblemonRider, you may have noticed that you can't ride Partner Pokémon, meanwhile you could with the non-Partner variants. Don't worry, I've taken that into account, so I've added in an separate download with an edited config that also supplies the Partner variants, allowing you to ride the Partner variants of your Pokémon!
But still, I would highly suggest you still support the original mod instead of this datapack. I only added Partner variants to it, and made that available for everyone to use in conjunction with this datapack.
- To insert this, you need to do the same thing you did to install this datapack into your world, except you can just insert the config into your world's folder. Don't put the config file in the datapack folder, otherwise it won't work!
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Rider config.zip | Unknown | 6.71 KiB |
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:KSUvCcDq:FkkO0mw5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KSUvCcDq:FkkO0mw5"
}
