Links
Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated last month
All versions
1.3.0
Release
Cobblemon: Coop+ 1.3.02 months ago 337
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Additions
- Added a fully customizable Handicap menu with independent battle restrictions.
- Added clearer error messages when player does not met requirements for a battle
- Added waiting screens while another player accepts an invitation or selects their team
- Added chat message showing rewards earned after defeating a trainer while co-op mode
- Added a improved session cleanup when players disconnect, cancel, or leave a battle
- Added a WHOLE UI Rework for ALL Menu (Hope you enjoy it)
- Changed the reward split, so items drop next to each player instead of getting into inventory
Fixes
- Fixed a issue with split mode losing or duplicating Pokémon when a trainer has fewer than six
- Fixed a issue with split mode behavior for both 3-each and 6-each battles
- Fixed a issue with co-op invitations sending the same message twice
- Fixed a issue with specific trainers displaying the incorrect “no trainer data” error
- Fixed a issue with conditional trainer loot tables not being evaluated correctly
- Fixed a issue that made rewards being lost when a player's inventory is full
- Fixed a issue with several unclear or generic battle eligibility errors
- Fixed a issue with the compatibility with both older and newer supported RCTMod versions (This should make Completely compatible with Cobbleverse 1.3.x up to 1.4.x)
- Fixed a issue that made both players can fight in different dimensions
- Fixed a issue that made coop player to not able to interact anymore with trainer once fight ended
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:cbOecy62:F61C4I35"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cbOecy62:F61C4I35"
}

