> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-hud/troubleshooting.md).

# Troubleshooting

**The HUD does not show up.** On QBCore and Qbox the HUD waits for `LocalPlayer.state.isLoggedIn`, on ESX for the player to be loaded. Check that the framework starts before `daddy-hud`, or set `Config.Framework = 'none'` to show it right after spawn. `/hud` > General > HUD Visibility must be on.

**Two HUDs on screen, or the minimap flickers.** Another HUD is still running. Stop it, or set `Config.Minimap.mode = 'off'` if another script should control the radar.

**Hunger and thirst stay at 100.** Without a framework nothing reports them. On ESX `esx_status` must run. Custom status scripts can call `exports['daddy-hud']:SetModuleValue('hunger', value)` or be connected in `client/bridge.lua`.

**The seatbelt icon never appears.** No seatbelt script was found. Use `qbx_smallresources`, a script that sends `seatbelt:client:ToggleSeatbelt`, or set `Config.Vehicle.Seatbelt = 'builtin'`.

**Fuel always shows full.** Your fuel script is not in the list. Set `Config.Vehicle.Fuel = 'native'` if it writes the GTA fuel level, or add its export in `client/vehicle.lua` (open source edition).

**The body map does not change when I get shot.** Check `Config.HealthSystem`. With `ml_healthsystem` the resource must run. With `external` only your scripts set the body map.

**Injuries stay after a revive.** Your ambulance script uses an event the HUD does not know. Call `exports['daddy-hud']:ClearInjuries()` from its revive code.

**The minimap frame does not line up with the radar.** The frame is placed for a 16:9 screen. Adjust the `SetMinimapComponentPosition` values in `client/minimap.lua` (open source edition) or set `Config.Minimap.mode = 'off'`.

**Test commands do not work.** They are only registered with `Config.Debug = true`.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-hud/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.