Death Firework
Minecraft 26.2 datapack that launches a configurable firework when a player dies.
Requirements
- Minecraft Java Edition 26.2 (pack format 107)
- No mods or plugins required
Install
1. Download the datapack zip from a release, or build one locally (see Build). 2. Remove any older copy of this datapack from the world's datapacks folder. 3. Place the zip unextracted in <world>/datapacks/. 4. Run /reload, or restart the world. 5. Check with /datapack list enabled.
The zip must have pack.mcmeta and data/ at the root (not inside an extra folder). Release zips are built that way.
Playing
Open the personal colour menu:
/trigger df_menu
Available colours: red, blue, yellow, green, pink and purple. A player can only change their own colour.
Operators can open the global admin menu:
/function death_firework:admin/menu
Global options:
- lifetime: 20 / 40 / 60 / 80 ticks
- trail: on / off
- sparkle: on / off
Defaults: lifetime 60, trail off, sparkle on, colour red.
Test the current colour and global settings without dying:
/function death_firework:test/current
Or trigger the firework with /kill @s. Global scores: /function death_firework:admin/status.
Notes: the admin menu runs /function buttons, so it needs sufficient command permission. A firework explosion can damage entities close to the blast. Missing or invalid config values are restored automatically.
Releases
Push a version tag (for example 1.0.0 or v1.0.0). The BlueGit pipeline runs automatically on that tag (no manual job): it validates the pack, builds the zip, and attaches it to the release. Do not add a second leading v; the pipeline strips one if the tag already starts with v.
The zip is named:
death-firework-<minecraft-version>-v<tag>.zip
The Minecraft version is the single line in the minecraft-version file at the repository root (currently 26.2). Change that file when the pack targets a new game version. It is not included in the zip.
Build
From the repository root, without pushing a tag:
bash scripts/ci/validate.sh
bash scripts/ci/pack.sh 1.0.0
The zip is written to build/out/death-firework-26.2-v1.0.0.zip.
Source
| 1 | # Death Firework |
| 2 | |
| 3 | Minecraft **26.2** datapack that launches a configurable firework when a player dies. |
| 4 | |
| 5 | ## Requirements |
| 6 | |
| 7 | - Minecraft Java Edition **26.2** (pack format 107) |
| 8 | - No mods or plugins required |
| 9 | |
| 10 | ## Install |
| 11 | |
| 12 | 1. Download the datapack zip from a [release](https://git.timfalken.com/timfa/death-firework/-/releases), or build one locally (see [Build](#build)). |
| 13 | 2. Remove any older copy of this datapack from the world's `datapacks` folder. |
| 14 | 3. Place the zip **unextracted** in `<world>/datapacks/`. |
| 15 | 4. Run `/reload`, or restart the world. |
| 16 | 5. Check with `/datapack list enabled`. |
| 17 | |
| 18 | The zip must have `pack.mcmeta` and `data/` at the root (not inside an extra folder). Release zips are built that way. |
| 19 | |
| 20 | ## Playing |
| 21 | |
| 22 | Open the personal colour menu: |
| 23 | |
| 24 | ```text |
| 25 | /trigger df_menu |
| 26 | ``` |
| 27 | |
| 28 | Available colours: red, blue, yellow, green, pink and purple. A player can only change their own colour. |
| 29 | |
| 30 | Operators can open the global admin menu: |
| 31 | |
| 32 | ```text |
| 33 | /function death_firework:admin/menu |
| 34 | ``` |
| 35 | |
| 36 | Global options: |
| 37 | |
| 38 | - lifetime: 20 / 40 / 60 / 80 ticks |
| 39 | - trail: on / off |
| 40 | - sparkle: on / off |
| 41 | |
| 42 | Defaults: lifetime 60, trail off, sparkle on, colour red. |
| 43 | |
| 44 | Test the current colour and global settings without dying: |
| 45 | |
| 46 | ```text |
| 47 | /function death_firework:test/current |
| 48 | ``` |
| 49 | |
| 50 | Or trigger the firework with `/kill @s`. Global scores: `/function death_firework:admin/status`. |
| 51 | |
| 52 | Notes: the admin menu runs `/function` buttons, so it needs sufficient command permission. A firework explosion can damage entities close to the blast. Missing or invalid config values are restored automatically. |
| 53 | |
| 54 | ## Releases |
| 55 | |
| 56 | Push a version tag (for example `1.0.0` or `v1.0.0`). The BlueGit pipeline runs **automatically** on that tag (no manual job): it validates the pack, builds the zip, and attaches it to the release. Do not add a second leading `v`; the pipeline strips one if the tag already starts with `v`. |
| 57 | |
| 58 | The zip is named: |
| 59 | |
| 60 | ```text |
| 61 | death-firework-<minecraft-version>-v<tag>.zip |
| 62 | ``` |
| 63 | |
| 64 | The Minecraft version is the single line in the `minecraft-version` file at the repository root (currently `26.2`). Change that file when the pack targets a new game version. It is not included in the zip. |
| 65 | |
| 66 | ## Build |
| 67 | |
| 68 | From the repository root, without pushing a tag: |
| 69 | |
| 70 | ```bash |
| 71 | bash scripts/ci/validate.sh |
| 72 | bash scripts/ci/pack.sh 1.0.0 |
| 73 | ``` |
| 74 | |
| 75 | The zip is written to `build/out/death-firework-26.2-v1.0.0.zip`. |