Tags
Creators
Details
1.0
Compatibility
Required content
Changes
π Cobble Capsule 1.0.0 β Initial Release
This marks the first public release of Cobble Capsule, a fully integrated capsule progression system designed to fit naturally into the Cobblemon gameplay loop.
π§© Capsule System
- Added a full set of trainer-oriented capsule families (loot, resources, combat, healing, etc.).
- Each capsule line now includes multiple tiers to create a clear sense of progression.
- Seamless integration into the Cobblemon loot ecosystem for a native gameplay feel.
π οΈ Crafting & New Items
- Added a dedicated capsule workstation to centralize all capsule-related crafting.
- Introduced several capsule cores and mid-to-late-game crafting components.
- Crafting recipes now use a hybrid of Cobblemon and Minecraft items to reward exploration and combat.
π Visual Feedback & Effects
- Implemented tier-based opening particles when activating capsules.
- Added sound feedback on capsule activation using official Minecraft sound assets.
- Technical groundwork prepared for future custom capsule SFX.
π Compatibility & Integrations
- Native compatibility with Cobblemon as the core dependency.
- Support for optional mod integrations through bonus capsule entries
(e.g.
cobblemon_utility,mega_showdown). - Loot table structure designed for easy extension in upcoming updates.
βοΈ Balance & Technical Setup
- First pass of loot balance to keep rewards meaningful without breaking progression.
- Modular loot table architecture to allow external mods to append their own drops safely.
- Codebase prepared for upcoming balance patches and new capsule lines.
This version 1.0 lays the foundation of Cobble Capsule. Future updates will focus on fine-tuning the balance, adding custom sound design, and exploring new capsule categories.
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:AnJ1o5qa:ghnflcop"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AnJ1o5qa:ghnflcop"
}

