How it fits together

Where settings live

Aurora HUD is configured in game, not in files. There are three places a setting can come from, and they do not overlap:

Where	Who changes it	Applies to
/hud menu, player tabs	Any player	That player only
/hud menu, admin tabs	Holders of the command ace	The whole server
config/ folder	Server owner	The whole server

The config/ folder answers one question only: which of your other scripts should the HUD talk to. Fuel, inventory, notifications, voice, phone. Everything else — colours, positions, which widgets exist, seatbelt, stress, crosshair, currency, language — is in the menu.

Tip

If you find yourself editing a file to change how the HUD looks or behaves, you are in the wrong place. Look in /hud first.

The folder

hud/
├── config/     the only files you edit
├── client/     client code (bridge → core → modules)
├── server/     server code and persistence
├── stream/     minimap textures
└── web/        the interface

Only config/ is meant to be opened. The rest is the resource.

Nothing in config/ can break the HUD

Every adapter in config/ runs inside a guard. If one errors — a missing export, a renamed resource, a typo — the failure is recorded and the HUD carries on using its own behaviour for that feature.

You see what failed in /hud → Support, by name. See Troubleshooting.

After editing a config file

restart hud

Config files are read at start-up. Nothing in config/ is hot-reloaded.