Aurora HUD

The HUD your players
configure themselves.

Players set their own widgets, colours and positions from a menu in game. Works with Qbox, QBCore, ESX and standalone servers.

  • Qbox
  • QBCore
  • ESX
  • Standalone

What it does differently

Configured in game

Colours, positions, widgets, seatbelt, stress, currency and language all live in /hud. The config/ folder answers one question only: which of your scripts the HUD should talk to.

Layouts by dragging

Edit mode drops the HUD into a layer where every widget can be moved and resized directly, with snap guides between them. No coordinates to type.

Share codes

A player exports a layout as a code and another imports it, even on a different server. Positions, colours and opacity travel; nothing else does.

Server settings are marked

Admin tabs are red throughout the menu. The red is not an error state — it means the change leaves your machine and applies to every player.

Turn any feature off

Run your own seatbelt, indicators or cruise control and feed the icons through the exports. While a HUD feature is on, it is the source of truth.

Nothing fails quietly

Every adapter runs inside a guard. If one errors — a missing export, a renamed resource — the HUD carries on and reports what failed in /hud → Support.

The store opens soon

Aurora HUD will be sold through Tebex, with Cfx.re asset escrow. The documentation is already open, so you can see exactly what you are getting first.