UltimateFireworks Staff Reference
Public-safe technical notes for staff who configure or support UltimateFireworks on 1MoreBlock.
Verify destructive, economy-changing, permission-changing, and player-data commands against the installed build and an approved support case before running them.
Commands
Section titled “Commands”| Command | Permission | Purpose |
|---|---|---|
/ultimatefireworks | ultimatefireworks.admin | Common full command label; use installed help for exact syntax. |
/uf | ultimatefireworks.admin | Common alias in some builds; verify before documenting operational use. |
/ultimatefireworks reload | ultimatefireworks.admin | Common reload pattern; confirm installed help. |
Permissions
Section titled “Permissions”| Permission | Purpose | Suggested access |
|---|---|---|
ultimatefireworks.admin | Common administrative node; verify installed build. | Server administrators |
ultimatefireworks.* | Potential effect/command namespace. | Never grant without inspecting installed nodes |
Placeholders
Section titled “Placeholders”No plugin-owned placeholders were verified. PlaceholderAPI may still expose values through a separate expansion or an integrating plugin.
Configuration and integrations
Section titled “Configuration and integrations”- Custom items and recipes require metadata compatibility.
- WorldGuard and event-area rules still control where effects are allowed.
- The paid upstream page is the best available authoritative reference; installed
/helpoutput is required for exact command/perms.
Examples
Section titled “Examples”/ultimatefireworks/uf/ultimatefireworks reloadTroubleshooting
Section titled “Troubleshooting”- Capture item metadata, effect name, world, location, and trigger method.
- Check permission/world/effect configuration and whether another plugin consumed the item.
- For performance reports, record effect count and timing rather than repeatedly reproducing.