All versions
1.2.0
Release
Cobblemon True Pickup 1.2.02 weeks ago 88
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Unavailable version
Any compatible version
Any compatible version
Changes
v1.2.0
Added
- Honey Gather support — the ability-to-loot-table system is now fully generalized, so Honey Gather works out of the box alongside Pickup. Any future ability can be supported the same way, just by adding a matching loot table file — no code changes needed.
- Rarity-tiered loot pools —
generic,uncommon,rare,epic, andlegendarytiers per ability, each with its own selection weight and its own weighted item list. A roll picks a tier first, then an item within it.
Changed
- Loot tables reworked from per-species files to per-ability files.
Previously every Pickup-capable species got its own loot table under
config/truepickup/pickup_tables/. That's been replaced with one file per ability (pickup.json,honeygather.json) underconfig/truepickup/loot_tables/, each split into rarity tiers. Much easier to tune at a glance than juggling a dozen-plus species files. - Config key renamed:
debugLogging→debug.
Removed
- Per-species loot table files and their
enabledflag/template-generation system (superseded by the per-ability tiered tables above).
Notes
- If you customized any per-species tables under the old
pickup_tables/folder, those won't carry over automatically — the new system reads fromloot_tables/instead. Re-apply any custom weights to the newpickup.json/honeygather.jsontier format. - Loot tables remain config-folder based rather than datapack-based, by design — see the mod description for why.
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:ENWEtfIW:OYfpzAra"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ENWEtfIW:OYfpzAra"
}

