> For the complete documentation index, see [llms.txt](https://izzyshop-1.gitbook.io/izzyshop-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://izzyshop-1.gitbook.io/izzyshop-docs/hud-resources/classic-hud/f.a.q.md).

# F.A.Q

<details>

<summary>Cash, job, or name is not updating — why?</summary>

Make sure the framework is detected correctly (`qb-core` or `es_extended` must start before the HUD). The player must be fully logged in. On QB, `QBCore:Client:OnPlayerLoaded` must fire; on ESX, `esx:playerLoaded` must fire. If the issue persists, restart the resource or refresh data with `TriggerServerEvent('izzy-classichud:server:getPlayerInfo')`.

</details>

<details>

<summary>The /hud command does not work — why?</summary>

The command name is set via `Config.Commands.hudSettings` (default: `hud`). Make sure `ox_lib` and your framework are running. The command is registered in the escrow `client.lua` file; if the resource did not start properly, the command will not be registered. Alternative: `exports['izzy-classichud']:OpenSettingPanel()`

</details>

<details>

<summary>Hunger / thirst bars are not moving — why?</summary>

QB: The `hud:client:UpdateNeeds` event must be triggered — qb-core or qb-hud usually handles this.\
ESX: The `esx_status` resource must be running; `esx_status:onTick` sends hunger/thirst values. If `esx_status` is stopped, the bars will stay static.

</details>

<details>

<summary>Minimap is missing or broken — what should I do?</summary>

Check `Config.DefaultHudSettings.minimap.display`: `always`, `inVehicle` (default), or `never`. If stream assets (`minimapmask`) are not loaded, the minimap may break — install the Tebex asset pack. The HUD auto-refreshes on resolution changes; if the issue continues, restart the resource.

</details>

<details>

<summary>Seatbelt is not working — what should I check?</summary>

`Config.Seatbelt.enabled` must be `true`. Default key: B. Seatbelt is disabled on motorcycles, bicycles, and boats. Alternatives: `TriggerEvent('seatbelt:client:ToggleSeatbelt')` or `exports['izzy-classichud']:SetSeatBeltState()`

</details>

<details>

<summary>Stress system is not working — why?</summary>

It is disabled by default. Enable it with `Config.Features.stress.enabled = true` and `Config.Features.stress.showInHud = true`. Make sure QB/ESX stress events are working (`hud:client:UpdateStress`, `esx_status`).

</details>

<details>

<summary>Progress bar or exports are not working — why?</summary>

Exports may be called before the HUD is ready. Check with `exports['izzy-classichud']:hudIsReady()` first. `ox_lib` must be installed and running. Only one progress bar can run at a time; new calls are ignored while one is active.

</details>

<details>

<summary>Notifications are not showing — what should I do?</summary>

Client:

`exports['izzy-classichud']:notify({ message = 'Message', type = 'success' })`

Server:

`Config.Notification('Message', 'info', 5000, source)`

Notifications will not show if the HUD is not loaded yet — wait until `hudIsReady()` returns `true`.

</details>

<details>

<summary>Music menu or settings panel is not opening — why?</summary>

NUI may not have loaded properly. Check F8 → NUI devtools for JS errors. Use the `/hud` command or `exports['izzy-classichud']:OpenSettingPanel()`. Make sure `ox_lib` and your framework are running.

</details>

<details>

<summary>Fuel gauge shows 0 or wrong value — why?</summary>

Fuel scripts are auto-detected: ox\_fuel, cdn-fuel, LegacyFuel, rcore\_fuel, okokGasStation, lc\_fuel, BigDaddy-Fuel. Make sure your fuel resource is started. If none is found, the GTA native fuel value is used — which usually gives incorrect results.

</details>

<details>

<summary>HUD is not showing at all — why?</summary>

`ox_lib` is required — it must be installed and ensured. QB or ESX must start before the HUD. Another HUD script may be conflicting — disable other HUD resources. The HUD will not activate until the player is logged in.

```lua
ensure qb-core       # or es_extended
ensure ox_lib
ensure izzy-classichud
```

</details>

<details>

<summary>I'm getting a dependency '/assetpacks' error — what should I do</summary>

The asset pack is required for the Tebex escrow package. If you purchased the script from Tebex, install the asset pack on your server. Unofficial copies often trigger this error.

</details>

<details>

<summary>Which resource name should I use in exports?</summary>

Use the folder name — not the `name` value in `fxmanifest`:

```lua
exports['izzy-classichud']:showHUD()
exports['izzy-classichud']:notify({ message = 'Test', type = 'info' })
```

</details>

<details>

<summary>How do I enable Turkish / change language?</summary>

In `config.lua`:

Supported languages: `en`, `tr`, `de`, `ar`. Players can also change language from the `/hud` settings menu.

```lua
Config.Locale = 'tr'
```

</details>

<details>

<summary>I want to temporarily hide the HUD — how?</summary>

Commonly used in cutscene and admin menu scripts.

```lua
exports['izzy-classichud']:hideHUD()
-- cutscene, menu, inventory, etc.
exports['izzy-classichud']:showHUD()
```

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://izzyshop-1.gitbook.io/izzyshop-docs/hud-resources/classic-hud/f.a.q.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.