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

# F.A.Q

<details>

<summary>The HUD does not show at all — what should I do?</summary>

Disable other HUD scripts first (`qb-hud`, `esx_hud`, etc.). In `server.cfg`, make sure `ensure izzy-hudv8` runs after your framework. Verify the `dist/` folder is complete and check the F8 console for NUI errors.

</details>

<details>

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

In `shared/config.lua`, `IZZY.Keybinds.hudMenuCommand.enable` must be `true`. If you changed the command name, use the new one (e.g. `/hudmenu`). Restart the resource after making changes.

</details>

<details>

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

Check that `IZZY.Framework` matches your server (`newqb`, `qbox`, `esx`). Make sure the player is fully loaded. If cash comes from an inventory item, `IZZY.TopInformation.cash.useItem` and `itemName` must be set correctly.

</details>

<details>

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

On QB, `hunger` and `thirst` metadata must be updating. On ESX, `esx_status` or your needs script must be running. In `IZZY.StatusVisibility`, `hunger` and `thirst` must not be disabled. The HUD only displays data — your needs script must feed it.

</details>

<details>

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

`IZZY.Minimap.enable` must be `true`. For on-foot minimap, set `onlyInVehicle = false`. Check that the `stream/` folder is present and `dependency '/assetpacks'` is satisfied. Disable any other minimap script that may conflict.

</details>

<details>

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

Ensure `IZZY.Seatbelt.enable = true` and the key (`seatbeltKeyMapping`, default `B`) is correct. Another seatbelt script may be conflicting — disable one of them.

</details>

<details>

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

`IZZY.Stress.useStress` must be `true` and `IZZY.Mysql` must match your MySQL resource (`oxmysql`, etc.). Whitelisted jobs may not gain stress. To test: `exports['izzy-hudv8']:SetStress(50)`.

</details>

<details>

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

Do not call exports before the HUD loads — check `hudIsReady()` first. `exports['izzy-hudv8']` must match your actual resource folder name. If an old `progressbar` resource is active, it will conflict — disable it.

</details>

<details>

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

If the HUD is not ready, notify may fail silently. Client: `exports['izzy-hudv8']:notify({ message = 'Test', type = 'success' })`. Server: `TriggerClientEvent('izzy-hud:client:notify', source, 'Message', 'inform', 5000)`.

</details>

<details>

<summary>Music menu or car control will not open — why?</summary>

Both are vehicle-only by default. Check that `/music` and `/carcontrol` (or `F10`) have `enable = true` in `config.lua`.

</details>

<details>

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

The HUD auto-detects scripts like `ox_fuel`, `LegacyFuel`, `cdn-fuel`, and `izzy-fuel`. If your fuel script is not supported, add it to the `IZZY.GetFuel` function.

</details>

<details>

<summary>Settings are not saving — why?</summary>

Settings are saved to client KVP. A different Cfx account or cleared cache can reset them. Save from the HUD menu, then test with `restart izzy-hudv8`.

</details>

<details>

<summary>HUD loads late after multichar — is that normal?</summary>

v8 has a QB spawn fallback, but `ensure` order still matters: framework → multichar → izzy-hudv8.

</details>

<details>

<summary>Version check shows a red warning — is that a problem?</summary>

If an update is available, download the latest build from Keymaster. If the server cannot be reached, it is usually due to internet/firewall and does not affect gameplay.

<https://portal.cfx.re/assets/granted-assets>

</details>

<details>

<summary>I get an <code>assetpacks</code> dependency error — what should I do?</summary>

Required for minimap textures. Make sure the Keymaster package includes the full `stream/` folder.

</details>

<details>

<summary>Server feels laggy — is the HUD slowing it down?</summary>

Default tuning is already optimized. You can increase intervals in `IZZY.Tuning`. Use `resmon` to check which script is actually causing the load.

</details>

If the problem persists, make sure you have downloaded the latest version of the script from Keymaster and that no other HUD script is active on your server.

If you still cannot find a solution, you can open a ticket on our Discord server. Our team can help with setup, configuration, and script conflicts.

{% hint style="info" %}
[Resources Download](https://portal.cfx.re/assets/granted-assets)
{% endhint %}

{% hint style="info" %}
[Join our Discord server](https://discord.gg/izzyshop)
{% endhint %}


---

# 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-v8/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.