
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 operator tools that make CriticalHealthFX practical on a live server: presets, forced test mode, status output, and the first checks to run when something looks wrong.
Presets
CriticalHealthFX ships four preset lanes:
mcwarsubtlehardcoreoff
Apply them with:
/chfx preset <mcwar|subtle|hardcore|off>or through the Presets page in the GUI.
What each preset does
MCWAR
This is the public default release target:
critical_threshold_hp: 10.0- light red at 5 hearts
- strongest red at 1 heart
- blackout only at half a heart
- heartbeat enabled
- frost enabled
- tier potions and particles enabled globally
Subtle
This profile backs the intensity down:
- threshold lowered to
8.0 - blackout disabled
- softer tier curve
- tier potions and particles disabled globally
Hardcore
This profile pushes danger earlier and harder:
- threshold raised to
12.0 - faster scan cadence
- stronger warning distance
- blackout enabled earlier
- frost still enabled
- tier potions and particles disabled globally by default
Off
Disables the plugin globally.
Treat presets as full package swaps
Presets do not only flip one boolean. They rewrite several global settings together and replace the tier list. Do not use them casually in the middle of a detailed hand-tuned profile unless you actually want to replace that profile.
Test mode
The normal testing command is:
/chfx test onThat forces the effect loop on your own player account regardless of current health.
Turn it off with:
/chfx test offThis is the safest way to:
- tune the red curve
- compare presets
- verify the blackout threshold
- confirm the GUI changes are really taking effect
Status output
Use:
/chfx statusto read the active runtime summary instead of guessing from memory. The output includes the big switches that usually explain why a server owner thinks the plugin is broken.
Debug flags
The debug block currently includes:
debug:
actionbar: false
log_state_changes: falsedebug.actionbar
Shows extra state information while the effect is active.
debug.log_state_changes
Logs enter and exit state changes to console.
Leave both off in normal production unless you are actively diagnosing a problem.
First checks when the effect is missing
No red vignette
Check:
- the server is Paper, not just Spigot
enabled: true- the player is in an allowed gamemode
- the player is at or below
critical_threshold_hp - the tier curve is not overly soft
Red exists but feels too weak
Check:
warning_blocks- per-tier
warning_blocks - low-tier
diameter
Heartbeat is missing
Check:
heartbeat.enabled- the sound key is valid
- the volume is not too low
- the active tier is actually inside the threshold range
Blackout fires too early
Check:
overlays.blackout.min_hp- whether a preset was recently applied
- whether a separate darkness layer is also enabled and being confused with blackout
Frost is not appearing
Check:
overlays.frost.enabledoverlays.frost.min_hpoverlays.frost.biomes- whether the player is really in one of the configured cold biomes
Potion or particle extras are missing
Check:
tier_effects.potions_enabledtier_effects.particles_enabled- the active tier really contains those entries
- the particle type is valid for the current API
Good support request checklist
When a server owner reports a problem, ask for:
- server type and exact Paper build
- CriticalHealthFX version
- full console error if one exists
- the current
config.yml - exact reproduction steps
That is usually enough to tell whether the issue is:
- a runtime environment problem
- a threshold misunderstanding
- a biome-key problem
- a preset overwrite
- a config typo
Final rule of thumb
If the plugin feels wrong, do not start by changing ten tier values at once. Check the basics first:
- Is the plugin active for the player?
- Is the global threshold correct?
- Is the border tuning sane?
- Is the overlay threshold where you think it is?
- Is a preset hiding the change you expected?

