Tags
Creators
Details
All versions
4.0.0-SNAPSHOT+1-bukkit
Beta
CreeperConfettiPro 4.0.0-SNAPSHOT+1-bukkitlast month 4
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.4
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Added
- Command system refactored to subcommand mode (no longer a single root command listing all functions):
| Command | Description |
|---|---|
| `/cc help [page | subcommand]` |
| `/cc effect <list | add |
/cc chance [0-100] |
View / set global confetti trigger chance (new) |
| `/cc language <info | list |
/cc reload |
Reload configuration and firework styles |
- Aliases supported:
effect→style/styles/firework;language→lang; root command →cc/confetti. - Hierarchical tab completion.
- Permissions split into fine-grained nodes:
creeperconfetti.command.{reload,effect,chance,language}(parent permission grants all child permissions by default viachildren). - Multiple firework styles + random triggering: Configuration changed from a single
confetti_effecttofirework_styles(mapping structure). Each style may contain one or more firework effects. When a creeper explodes, one style is randomly selected to play.- Colors support three formats: color names (
RED/LIME…), hex (#FF0000/#f00), RGB object ({RED: 255, GREEN: 0, BLUE: 0}). - 4 built-in default styles:
classic/starburst/rainbow/creeper. - In-game
/cc effect add <name>saves all firework effects from your main hand as a new style.
- Colors support three formats: color names (
- Backward compatibility: Old configs with only
confetti_effectwill be automatically migrated into a style nameddefault. Empty config falls back to built-in default styles. - Language manager improvements: Supports recursive reading of nested keys. Untranslated keys automatically fall back to English; raw keys will no longer be displayed.
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:zOtyOPVB:q5t8qRNO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zOtyOPVB:q5t8qRNO"
}

