All versions
1.1.0
Release
Cobblemon: Team Preview 1.1.0 ~ neoforge2 weeks ago 276
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Changelog
1.1.0 (October 9th, 2026)
Additions
- Ported the team preview from the Fabric-only version to Fabric + NeoForge.
- Added the Singles Preview and Doubles Preview formats to Cobblemon's challenge screen.
- Added a Cobblemon styled confirm button; the selection is locked only after confirming.
- Pokémon are now picked in order: each pick shows its position and can be dropped again.
- Doubles Preview is bring 6, pick 4, with the first 2 picks as leads.
- Added Spanish translation.
Changes
- Updated to Cobblemon 1.8.2, Kotlin 2.2.20, Fabric Loader 0.17.2 and NeoForge 21.1.182.
- Switched to Mojang mappings and the cobblemon-contenders build setup.
- The preview only opens for the preview formats; normal battles start right away as in Cobblemon.
- Selection time is now 60 seconds; when it runs out the selection is completed with the team order instead of cancelling.
- Timers now run on the server tick instead of a background thread.
- Battles are started through Cobblemon's battle builder (respects level-adjusted formats and validations).
Fixes
- The rival only receives the data shown in the preview (no moves, IVs, EVs, nature, ability or held item).
- Previews are cancelled when a player disconnects or dies, and players are looked up by UUID when the battle starts.
- Teams without any usable Pokémon skip the preview so Cobblemon reports the error right away.
- Only the left mouse button selects a Pokémon.
- The selection survives resizing the window.
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:jjp3jo0b:59Gtr54M"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jjp3jo0b:59Gtr54M"
}

