> 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/hud-v7/f.a.q.md).

# F.A.Q

<details>

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

Make sure `IZZY.Framework` matches your server (`newqb`, `oldqb`, `esx`, `oldesx`). The player must be fully logged in. If cash comes from a custom inventory item, check your framework bridge and money sync events. Restart the resource or re-login if values stay stuck.

</details>

<details>

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

The command name is set in `IZZY.HudSettingsCommand` (default: `hud`). Make sure `ox_lib` and your framework are running. If the resource did not start properly, the command may not register. Alternative: `exports['izzy-hudv7']:OpenSettingPanel()`

</details>

<details>

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

QB: Hunger/thirst metadata or `hud:client:UpdateNeeds` must be triggered by your framework or status script.\
ESX: `esx_status` must be running and sending tick updates. If `esx_status` is stopped, the bars will stay static.

</details>

<details>

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

Check `IZZY.DefaultMap` (`rectangle` or `circle`) and map visibility settings in the HUD menu. Stream assets (`squaremap`, `circlemap`) must be loaded — install the Tebex asset pack if missing. Set `IZZY.DisplayMapOnWalk = true` if you want the map visible on foot.

</details>

<details>

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

`IZZY.Seatbelt.enable` must be `true`. If you use `qb-smallresources` or `esx_cruisecontrol` seatbelt, set `IZZY.Seatbelt.enable = false` to avoid conflicts. Default key: B (`hud_seatbelt`). Motorcycles and some vehicle classes are excluded.

</details>

<details>

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

`IZZY.Stress.useStress` must be `true` and `IZZY.Stress.show_in_hud = true` for the bar to show. Whitelisted jobs (`leo`, `ambulance`) do not gain stress. Manual control:

```lua
TriggerEvent('izzy-hud:client:gainStress', 3)
TriggerEvent('izzy-hud:client:relieveStress', 2)
```

</details>

<details>

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

Wait until the HUD is ready: `exports['izzy-hudv7']:hudIsReady()`. `ox_lib` must be installed and running. Only one progress bar can run at a time. Cancel with X or `/hud_cancel_progress`.

</details>

<details>

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

Notifications will not show if the HUD is not loaded yet.

Server:

```lua
IZZY.Notification('Message', 'success', 5000, source)
```

Client:

```lua
exports['izzy-hudv7']:notify({ message = 'Message', type = 'success', duration = 5000 })
```

</details>

<details>

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

`IZZY.Music` must be `true` for the music panel. Use `/music` (`IZZY.OpenMusicPanelCommand`) or `/hud` for settings. Check F8 → NUI devtools for JS errors. Make sure `ox_lib` is running.

</details>

<details>

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

Fuel is 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, GTA native fuel is used and may show incorrect values.

</details>

<details>

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

`ox_lib` is required. Set `IZZY.Framework` correctly. Framework must start before the HUD. Disable other HUD scripts to avoid conflicts. Player must be logged in before the HUD activates.

Recommended start order:

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

</details>

<details>

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

The Tebex asset pack is required for the escrow package. Install it from your Tebex purchase. Unofficial copies often trigger this error.

</details>

<details>

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

Use the folder name:

Events use the `izzy-hud:` prefix, not `izzy-hudv7:`.

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

</details>

<details>

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

Edit locale files in `locales/` and set `IZZY.Locale = 'en'` or `'tr'` in `config.lua`. Players can also change language from the HUD settings menu.

</details>

<details>

<summary>How do I temporarily hide the HUD?</summary>

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

</details>

<details>

<summary>Helicopter speedometer is not showing — why?</summary>

Use `exports['izzy-hudv7']:ToggleHelicopterSpeedometer()` if it was toggled off. Make sure you are in a helicopter and the HUD is fully loaded.

</details>

<details>

<summary>Which framework value should I use?</summary>

Wrong value = cash, job, and name will not sync correctly.

| Your setup       | Config value |
| ---------------- | ------------ |
| QB-Core (latest) | `newqb`      |
| QB-Core (old)    | `oldqb`      |
| ESX (latest)     | `esx`        |
| ESX (old)        | `oldesx`     |

</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/hud-v7/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.
