Wiki
Critical Health FX Wiki
Low-health visuals, heartbeat audio, blackout tuning, frost pulses, tier extras, and the public admin workflow for CriticalHealthFX.
Getting Started
Install the plugin cleanly, validate the startup state, and learn the admin command surface before deeper tuning.
Core Tuning
Set the activation threshold, shape the vignette, and tune the audio and overlay layers that define the low-health loop.
GUI and Editing
Use the in-game editor safely, understand what each page owns, and decide when YAML is still the better tool.
Runtime and Troubleshooting
Use presets deliberately, force test mode safely, and troubleshoot the common reasons the effect feels missing or wrong.
This page covers the public admin surface for CriticalHealthFX: the root command, the subcommands that matter day to day, and the cleanest way to work with the plugin on a live server.
Base command
CriticalHealthFX registers:
/chfxAliases:
/criticalhealthfx/criticalfx
Core permission
The formal permission node shipped in plugin.yml is:
criticalhealthfx.admin
That permission gates the command surface and the GUI.
Public subcommands
/chfx gui
Open the in-game editor.
/chfx reload
Reload config.yml and re-apply the active runtime settings.
/chfx status
Show the effective runtime summary in chat, including:
- enabled state
- threshold HP
- warning blocks
- heartbeat state
- blackout state
- frost state
- tier potion and particle toggles
- debug flags
- detected Minecraft version
/chfx test <on|off>
Force the effect loop on your own player account for testing. This is the fastest way to preview the full presentation stack without repeatedly damaging yourself.
/chfx preset <mcwar|subtle|hardcore|off>
Apply one of the built-in presets.
/chfx help
Print the command summary.
Root command behavior
If a player with permission runs /chfx with no arguments, the current build opens the GUI instead of printing help first. Console and non-player senders should use explicit subcommands such as status, reload, or preset.
Recommended admin workflow
For normal day-to-day work, this flow keeps things clean:
- Use
/chfx guifor most tuning. - Use
/chfx test onon your own account while adjusting. - Use
/chfx statuswhen you want the effective runtime view, not just what you think the YAML says. - Use
/chfx reloadafter manual edits inconfig.yml. - Use
/chfx test offwhen you are done so you do not forget a forced state on your admin account.
GUI chat prompts
Some values are better typed than clicked, especially:
- sound keys
- biome keys
- potion type tokens
- particle type tokens
- dust colors
When the GUI closes for a prompt, type the new value directly in chat.
Type:
cancelto abort and return to the GUI.
Staff role split
Server owner or lead admin
criticalhealthfx.admin
Builder or content tuner
If they are editing the plugin live, they also need:
criticalhealthfx.admin
CriticalHealthFX does not currently ship a narrower public permission split for "view only" or "basic use."
Best practice
Keep one clean testing account
Have one account that uses /chfx test on and one normal player account nearby. That makes it much easier to tell whether the problem is the config, the permission setup, or simple player state.
Use status before you blame a tier
Many "the tier is wrong" reports are actually:
- the plugin is disabled
- the threshold is set lower than expected
- the player is in a disallowed gamemode
- blackout or frost is turned off globally
Treat presets as full profile changes
/chfx preset does not only change one value. It rewrites several global settings and the tier list together. Use it intentionally.