All versions
1.7
Release
Quests Cobb 1.74 days ago 20
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
1.7
Added
- Automatic Daily Rewards Pruning:
- Implemented automatic cleanup of claimed daily quest entries older than 7 days (
pruneExpiredDailyClaims) during load and day rollover. - Prevents unbounded disk and RAM growth in
quests_data.jsonover months of server uptime.
- Implemented automatic cleanup of claimed daily quest entries older than 7 days (
- TTL Eviction for Thrown Pokéballs:
- Implemented timestamped
HitRecordentries and a 3-minute TTL eviction mechanism forPOKEBALL_HIT_COUNTS. - Completely eliminates memory leaks when Pokéballs hit Pokémon that despawn, flee, or are not captured.
- Implemented timestamped
Fixed
- Exhaustive Evolution Stone Detection:
- Fixed
EVOLVE_WITH_STONEto recognize all official evolution stones (Moon, Sun, Leaf, Ice, Dusk, Dawn, Shiny, Oval Stones, and Linking Cords) instead of only Water, Fire, and Thunder stones.
- Fixed
- Full Size Spectrum Detection for Jumbo & Teeny:
- Extended size detection in
CATCH_JUMBOandCATCH_TEENYto recognize all size variants (colossal,gigantic,microscopic,pygmy,size:huge,scale:*). - Added safeguard ensuring a single Pokémon capture cannot trigger duplicate increments.
- Extended size detection in
- Jobs Reward Claiming:
- Implemented missing server reward handlers for
reward_jobs_level_andreward_jobs_xp_inClaimRewardHandler. Players can now successfully claim their rewards when reaching level 10 or XP thresholds in their professions. - Enhanced
JobsCobbBestEffortwith reflective method caching, resilient Knot classloading fallbacks, and alias support.
- Implemented missing server reward handlers for
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:AE9CEHCV:TYzlYYl8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AE9CEHCV:TYzlYYl8"
}

