Tags
Creators
Details
Licensed MIT
Published 8 months ago
Updated 3 weeks ago
All versions
0.0.18
Release
Cobblemon Economy 0.0.183 weeks ago 592
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
Added
- Full trainer previews: battle quests now show the supplied trainer skins in quest cards and the detail preview.
- Prerequisite visibility: locked quests now show the missing prerequisite quests in the quest-board tooltip.
- Separated JSON configuration: shop definitions now have a documented
authoritative home in
shops.json, whileconfig.jsoncontains global economy settings. Quest definitions, quest NPCs, milestones, and quest-board bindings remain in their own files. - Persistence compatibility layer: economy and quest SQLite databases now use versioned, transactional migrations with
.bakbackups and safe refusal of unknown future schemas. - Safe configuration writes: JSON files are written atomically, backed up before replacement, and malformed files are quarantined before defaults are regenerated.
- Added persistence architecture diagrams, an operator migration/recovery guide,
and a tested release compatibility matrix for JARs
0.0.13through0.0.18.
Fixed
- Quest-board quests with unmet prerequisites are no longer displayed as available; the missing requirements are clearly identified.
- Cobblemon 1.7/1.8 Pokédex compatibility: capture and discovery rewards
now recognize both Cobblemon 1.7's
CAUGHTstatus and Cobblemon 1.8+'sOWNEDstatus without linking to a removed enum constant. - Cobblemon 1.7/1.8 model preview compatibility: quest-board Pokémon
previews select the appropriate
ModelWidgetconstructor at runtime after Cobblemon 1.8 added the block-light parameter.
Changed
- The development dependency target is the Fabric Cobblemon 1.8.1 artifact, Fabric Loader 0.17.2, and Fabric API 0.116.6+1.21.1; the published JAR still accepts Cobblemon 1.7.1 and newer when paired with that version's compatible Fabric Loader/API.
- The release version is now
0.0.18.
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:zfVCrbFk:3xp4vMCk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zfVCrbFk:3xp4vMCk"
}

