1.7.0
Compatibility
Changes
Changelog 1.7.0 Added Added dungeon battle level rules with NORMAL, FIXED, and RELATIVE modes. Added fixed-level join validation and temporary player party level scaling in fixed mode. Added relative trainer scaling based on the player's highest party level plus a configurable offset. Fixed mode now scales only the player's party; trainer party levels remain as configured. Added an option to disable Cobblemon battle experience during dungeon trainer battles. Added an in-game Battle Rules editor for level mode, relative offset, fixed level, and battle EXP. Added Shift-click dungeon deletion from the Dungeon Manager. Added targeted cleanup for a deleted dungeon's saved entry NPC. Added a Join NPC Cleaner item for removing leftover dungeon entry NPCs manually. Added per-EXPLORE-area heal NPC counts. Added an Area Settings editor screen for changing each explore area's heal NPC count. Added editor-side heal NPC count limits based on the area's available explore NPC candidates. Added separate explore NPC placement tools for fixed-facing and look-around spawn patterns. Changed Heal NPC assignment now uses each EXPLORE area's own healCount instead of one dungeon-wide value. /dungeon set healcount now distributes the requested count across EXPLORE areas for compatibility. Dungeon info displays now show the total of all area heal NPC counts. Updated the sample dungeon definition to use area-level heal NPC settings. Fixed Fixed malformed dungeon JSON resources. Fixed missing Japanese localization in dungeon management and adjustment screens. Fixed deleted dungeons reappearing after reload by writing deletion markers for editable dungeons. Fixed dungeon deletion leaving the related entry NPC behind.
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:8D5rUPSm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lqogdq3N:8D5rUPSm"
}

