All versions
1.6.0
Release
Cobblemon Dungeon 1.6.04 months ago 21
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
v1.6.0
Added
- Added a new Dungeon Flow screen in the Area Editor.
- Added visual dungeon flow editing for area order.
- Added automatic gate creation based on the Dungeon Flow order.
- Added directional flow arrows to make area connections easier to understand.
- Added Gate Bounds / trigger area guidance in validation messages.
- Added a default draft flow: explore_1 -> boss_area.
- Added a dedicated Cobblemon Dungeon creative tab.
- Added a Dungeon Manager item that opens the dungeon management menu.
- Added Dungeon Flow Arrow items for visual flow display.
- Added Dungeon Flow validation:
- The first area must be EXPLORE.
- The last area must be BOSS.
Changed
- Area Editor is now split into Area List and Dungeon Flow.
- Area List now focuses only on area creation and area editing.
- Gate creation is now handled automatically from Dungeon Flow instead of being managed manually from the Area List.
- Dungeon Flow now uses a 5-area snake layout with connector rows, making row-to-row connections easier to read.
- Dungeon Flow no longer opens area editing from flow slots. It is now used only for flow configuration.
- New dungeon drafts now start with the minimum natural structure: EXPLORE area -> BOSS area.
- explore_1 is treated as the fixed initial area when present.
- Manager and editor UI text has been improved and partially localized into Japanese.
Fixed
- Improved the confusing “Missing trigger area” validation warning by referring to Gate Bounds / trigger area more clearly.
- Fixed invalid Japanese language resource formatting.
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:V03bLRKB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lqogdq3N:V03bLRKB"
}

