1.3.5
Compatibility
Required content
Changes
Updated mod version metadata to 1.3.5. Fixed xpPerTier being ignored. Fixed config normalization forcing every tier back to 150 BPXP. Fixed reload behavior that could overwrite or reshape edited config files after loading. /bp reload should now correctly reload edited settings.json, quests.json, and the active rewards/season file. Fzzy Config changes now preserve the active rewards season instead of accidentally falling back to default rewards.json. Added specializedQuestRotationMinutes to settings.json and Fzzy Config. Existing worlds with old quest rotation values migrate safely without deleting custom quest edits. Added BPXP boost bossbar support. Added bpxpBoostBossBarEnabled, default true. Bossbar shows the active multiplier and remaining time. Bossbar timer drains as the boost event counts down. Manual /bp boost events now set total boost duration correctly for the bossbar. Random BPXP boost events also support the bossbar. Added persistent boost total-time storage so active boost timers survive saves more cleanly. Premium purchase now supports configurable item or item tag currency. Added premiumUnlockItemOrTag, default minecraft:diamond. Added premiumUnlockItemCost, default 32. Existing DIAMONDS configs are migrated into item mode automatically. CobbleDollars support is preserved through premiumUnlockCurrency = COBBLE_DOLLARS. Premium unlock button text now updates based on the selected payment method. Added /bp config set support for the new settings. Added the normal-stat fallback scanner that was already defined but not running. This gives capture/evolution/defeat XP tracking a backup path after resets/reloads or on packs where one Cobblemon event hook does not fire. Reset no longer leaves the system relying only on event hooks with no fallback scanner.
Optional dependencies
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:Zly5Pzt2:H3RDZ6v4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Zly5Pzt2:H3RDZ6v4"
}

