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

# Troubleshooting & FAQ

Fixes for the most common Striga Tokyo HUD problems.

{% hint style="info" %}
First check the server console and F8 for red errors. Send them with your question, it makes a fix much faster.
{% endhint %}

<details>

<summary>No HUD at all</summary>

* Log in with a character first, the HUD waits for the login.
* Check striga-core runs and printed its `ready` line. Look for a red striga-core error in the server console.
* Check F8 and the server console for errors, and that `web/dist` made it to the server (some FTP clients skip it).

</details>

<details>

<summary>The HUD thinks it is standalone on QBCore / Qbox / ESX</summary>

Set `framework` in `striga-core/config.json` by hand. Start your framework before striga-core, and striga-core before the HUD.

</details>

<details>

<summary>Stress goes up twice as fast</summary>

qb-hud (or qbx\_hud / esx\_hud) still runs. Remove it.

</details>

<details>

<summary>The minimap frame does not line up</summary>

Type `/hud debug` and open F8. Then change `Config.Minimap.Frame.Offset` (or `Offsets` if the map itself is off) in small steps like `0.002`, restart, check again. For the circle shape use `Frame.Circle`.

</details>

<details>

<summary>The rounded map shows square corners</summary>

After a change in `stream/`, players must reconnect. A resource restart is not always enough.

</details>

<details>

<summary>Share codes say disabled</summary>

oxmysql is not running, or `Config.Storage.Share` is `false`.

</details>

<details>

<summary>Fuel always shows full</summary>

Your fuel script is not in the list. Add its resource name to `fuel.resources` in `striga-core/config.json`, restart striga-core and the HUD.

</details>

<details>

<summary>The seatbelt key does nothing</summary>

With qb-smallresources or qbx\_seatbelt, use their key, the HUD only shows the state. The built in seatbelt only exists without them (or with `Own = true`).

</details>

<details>

<summary>The seatbelt chime keeps going while buckled</summary>

Your seatbelt script does not fire `seatbelt:client:ToggleSeatbelt`. Make it fire that event, or set `Seatbelt.Warning.Enabled = false`.

</details>

<details>

<summary>I changed the menu key but nothing changed</summary>

FiveM remembers keys per player. Players who already joined keep their key until they change it themselves. New players get the new default.

</details>

<details>

<summary>A Striga script has no block in the /hud menu</summary>

The script must run and use striga-core 0.1.0 or newer. Scripts without player settings have no block.

</details>

<details>

<summary>Texts show in English after I set another language</summary>

The locale file is missing or has a JSON error. Check the server console, then run the file through any JSON validator.

</details>

<details>

<summary>Blur stays on screen</summary>

Set `Config.MenuBlur = false`. If it is the stress blur, lower `Config.Stress.Effects` or turn `Blur` off.

</details>

{% content-ref url="/pages/WUiiSHagdFSrfVMaiwiA" %}
[Introduction](/docs/striga-tokyo-hud/introduction.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-tokyo-hud/troubleshooting-and-faq.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.