Troubleshooting
Start here
Section titled “Start here”Open /hud → Support as an admin. It shows, in one place:
- Which framework was detected
- Which of your scripts each integration bound to, by resource name
- What has failed since start-up
Most problems answer themselves here. An integration pointing at a resource that is not
running is named explicitly — which is usually a typo in config/client.lua.
The report
Section titled “The report”The panel builds a report to paste into a support channel. It is rate-limited to once every 30 seconds.
It contains what is needed to diagnose without a back-and-forth: versions, what was detected, what each integration bound to, and the recent failures from both client and server.
Common causes
Section titled “Common causes”A widget shows nothing
Section titled “A widget shows nothing”The HUD has no source for that value. On a standalone server the framework-fed widgets — job, wallet, hunger, thirst — stay dark until you feed them. See Exports.
The fuel gauge reads wrong
Section titled “The fuel gauge reads wrong”The fuel line in config/client.lua points at a script that is not running, or at the
wrong one. Support names what it found. If you renamed the fuel resource, update name in
its catalogue entry — see Integrations.
My seatbelt script and the HUD disagree
Section titled “My seatbelt script and the HUD disagree”Both are running. Turn the HUD’s seatbelt off in /hud → Admin, then push your state with
exports.hud:SetSeatbelt. While the HUD’s own feature is on it is the source of truth, and
the export returns false.
The menu will not open
Section titled “The menu will not open”The HUD refuses to open until it is ready — the player has joined, every server setting has answered, and the ped has spawned. This is deliberate: it stops the menu showing default values that would then be saved over the real ones.
If it never becomes ready, the cause is in Support: a setting that never answered.
Exports do nothing after renaming the folder
Section titled “Exports do nothing after renaming the folder”The resource must be named hud. Every export is addressed exports.hud:..., including
the ones inside config/client.lua. Rename it back.
Reporting a bug
Section titled “Reporting a bug”Send the report from the Support panel, plus what you did and what you expected. The report already answers the questions that would otherwise take three messages to establish.