All versions
1.1.4
Release
Cobblemon BattlePlus 1.1.44 months ago 21
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
1.1.4
- Added Battle Plus Manager creative-only item.
- Added Cobblemon Battle Plus creative tab.
- Added manager hub GUI from the Battle Plus Manager item.
- Added Trainer NPC manager GUI.
- Trainer NPC manager can create draft Trainer NPC presets from the player's current Cobblemon party.
- Trainer NPC manager displays each trainer's party in rows, with Pokemon shown one-by-one.
- Trainer NPC manager can spawn selected Trainer NPC presets from the GUI.
- Trainer NPC draft presets are saved under
config/cobblemonbattleplus/trainer_npc/presets. - Trainer NPC preset loading now supports both bundled datapack presets and config presets.
- Added Battle Factory pool manager GUI.
- Added Battle Tower pool manager GUI.
- Pool managers now use a two-step flow: select tier/pool first, then view and edit that pool.
- Pool managers display registered parties with Pokemon shown one-by-one.
- Pool managers can append the player's current 3-Pokemon party to config-backed pools.
- Pool managers can delete config-backed pool entries.
- Bundled pool entries are display-only and cannot be deleted from the manager.
- Battle Factory trainer pools now support config-backed direct
party_entries. - Battle Tower trainer pools now support config-backed direct
party_entries. - Added shared player party capture support for saving species, level, moves, ability, held item, nature, IVs, EVs, aspects, and tera type.
- Trainer NPCs now receive stationary protection when spawned.
- Battle Factory opponent NPCs now receive stationary protection.
- Battle Tower opponent NPCs now receive stationary protection.
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:KpbTa7sG:xxk49btA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KpbTa7sG:xxk49btA"
}

