All versions
2.0.0
Beta
Cobblemon Dungeon 2.0.04 months ago 21
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
2.0.0
This release focuses on Cobblemon Boss encounters, Pokemon clear rewards, and dungeon editor localization.
Added
- Added Cobblemon Boss trainers that appear as a configured Pokemon and battle with that fixed single Pokemon.
- Added configurable Cobblemon Boss HP phases (1-10). A lethal hit restores the boss to full HP in the same battle, clears persistent status, and preserves stat stage changes.
- Added configurable Cobblemon Boss stat boost stages (
None,+1to+6) applied at battle start. - Added weighted Pokemon clear rewards that are delivered to the player's party or PC.
- Added Pokemon reward previews to the dungeon reward information menu.
- Added BOSS and MINIBOSS area settings for switching between NPC Trainer and Cobblemon Boss encounters.
- Added an in-game party picker for registering one current-party Pokemon as an area's fixed boss.
- Added
/dungeon debug instantbosstest [id]for generating the instant test dungeon with a fixed Cobblemon Boss.
Changed
- Cobblemon Boss encounters now battle the displayed Pokemon entity directly instead of having it act as a trainer.
- Applied RCT Battle AI to direct Cobblemon Boss battles and prevented boss capture.
- Dungeon join UI defaults now fall back to localized runtime text instead of generating Japanese-only default text.
Fixed
- Added missing English and Japanese localization entries for dungeon editor screens, including area settings, dungeon flow, gate overview, gate creation, join conditions, boss Pokemon selection, reward previews, and dungeon management.
- Replaced remaining Japanese-only editor UI text with localization keys so both
en_usandja_jpare available.
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:Lqogdq3N:H8ggEMGQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lqogdq3N:H8ggEMGQ"
}

