Troubleshooting
How Roll Call reports which of your scripts Aurora HUD found, and which one stopped answering.
Start here
Section titled “Start here”Aurora HUD reads the resources around it by name and keeps a record of which ones answered.
That is Roll Call, and you read it in /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
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 the whole of Roll Call into a report to paste into a support channel, with a short cooldown between copies. It contains versions, what was detected, what each integration bound to, and the recent failures from 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 something feeds 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. A renamed fuel resource needs its name updated 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 the state with
exports.aurora_hud:SetSeatbelt. While the HUD’s feature is on, the export returns false.
The menu will not open
Section titled “The menu will not open”The HUD does not open until it is ready: the player has joined, every server setting has answered, and the ped has spawned. This prevents the menu showing defaults that would then be saved over the real values.
A setting that never answers is not fatal: the HUD stops waiting, opens anyway, and records what was missing in Support. Two conditions are fatal, both reported in the server console:
| Condition | Result |
|---|---|
| No usable language file (see Translations) | HUD never drawn, /hud never opens |
| Renamed resource folder | HUD never drawn, /hud never opens |
Exports do nothing after renaming the folder
Section titled “Exports do nothing after renaming the folder”The resource must be named aurora_hud. Every export is addressed
exports.aurora_hud:..., including those inside config/client.lua.
Reporting a bug
Section titled “Reporting a bug”Open a ticket in the Aurora Discord and paste the report from the Support panel, plus what was done and what was expected.