Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated last month
All versions
2.0.0+1.21.1
Release
Cobblemon Firework Capsules 2.0.0+1.21.18 months ago 241
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Firework Capsules has had a massive overhaul going into the 2.0 update!
Stickers are now ENTIRELY data-driven
- Stickers are now all under the
fireworkcapsules:stickerid. - Sticker mechanics are now defined under the
fireworkcapsules:sticker_explosiondata component. - New stickers can be created using ONLY a resource pack (with optional datapack functionality).
- Stickers now run on Cobblemon's snowstorm particle engine, allowing for much more dynamic particle effects.
- Stickers can now also play sounds when the Pokemon is sent out.
- Revamped all existing stickers, with some getting complete reworks.
Collect stickers with the new Sticker Book
- The sticker book is a new item which can store stickers, all the way up to the integer limit!
- Hovering over the sticker book will preview the first three rows of stickers inside the book.
Extra features
- Implemented a new
sticker/explosiondata registry to dynamically add stickers to the Creative Tab (and XEI tabs). - Added a way to extract stickers and firework stars from a ball capsule by putting the ball capsule and paper in a crafting grid.
- Added a recipe to convert the old stickers to the new stickers. The old sticker ids will be removed in a future update.
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:zBOfzARU:p6Vgrodr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zBOfzARU:p6Vgrodr"
}

