0.3.1
Compatibility
Changes
Urbanforma: Fireworks 0.3.1
Version 0.3.1 brings together the firework content developed over recent updates into a full release.
This update adds 15 new fireworks to the Other series and rebuilds the original 15. They are no longer simple color variations of spherical bursts: each now has its own visual structure, including straight bursts, long rays, concentric rings, ring cores, willow trails, spirals, pulses, delayed breaks, orbital effects, and color-shifting bead trails.
Large, medium, giant, and Other fireworks have been reorganized into a unified catalog. The current version includes 180 craftable fireworks, all with recipes, item models, English and Chinese names, and Creative Mode entries.
The giant series now includes multi-layer radial bursts, thick radial effects, extended willow displays, and cascading secondary bursts. The medium series currently includes the Medium Dense Sphere Firework and Medium Dense Radial Firework, with more effect families planned for future updates.
Every firework rocket now has a new item texture. The textures keep the familiar vanilla rocket silhouette while using gradients based on each firework's primary colors.
The Creative Mode layout has also been updated. Midsize Fireworks is now an independent category placed before Large Fireworks, and medium entries no longer appear in the large-firework sections. This update also fixes several naming, sorting, recipe, model, and resource mapping issues.
The built-in HD Fireworks resource pack is disabled by default, so lower-end players can use the mod without enabling it. Players who want enhanced particle visuals can enable it manually from the Resource Pack screen.
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:AVL70hWL:cQtnbTcL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AVL70hWL:cQtnbTcL"
}

