> 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-text-ui/troubleshooting-and-faq.md).

# Troubleshooting & FAQ

Fixes for the most common Striga Text UI questions.

<details>

<summary>Striga Text UI does not start</summary>

Check the server console. striga-core must run and be 0.1.0 or newer, and `ensure striga-core` must come **before** `ensure striga-text-ui`. A red error from striga-core means it is too old: update it. See [Updates & Versions](/docs/updates-and-versions.md).

</details>

<details>

<summary>Prompts still look like the old ones</summary>

* Check `striga-core/config.json` has `"textui": "auto"` or `"textui": "striga-text-ui"`.
* Check `ensure striga-text-ui` comes **after** `ensure striga-core` in `server.cfg`.
* For other scripts, check you did the step for your framework on [Integration](/docs/striga-text-ui/integration.md).

</details>

<details>

<summary>I see two prompts (ESX)</summary>

`esx_textui` is still running. Remove `ensure esx_textui` from `server.cfg` and restart the server.

</details>

<details>

<summary>A prompt shows on a different side than the script wanted</summary>

The player (or your config) picked a fixed position. With `auto`, the position the script asked for is used.

</details>

<details>

<summary>I pressed the key and the prompt went away</summary>

This is on purpose. Pressing the key plays a short animation and hides the prompt. It comes back when you are still at the same spot and no menu is open.

</details>

<details>

<summary>I see no prompts on the screen anymore</summary>

The player picked **3D** mode. In 3D mode nothing is drawn on the screen: prompts are pinned in the world. Switch back to Flat (2D) in `/textuisettings` or `/hud` → **Mode**. See [3D Prompts](/docs/striga-text-ui/3d-prompts.md).

</details>

<details>

<summary>A 3D prompt does not show</summary>

* Check `Config.World.Enabled = true`.
* Walk closer: it shows its key inside `distance` and the whole prompt inside `activeDistance`.
* It may be behind a wall. Put the point about 0.2 m in front of the surface, or set `occlusion = false` on that point.
* With `entity`, the point is hidden while the entity does not exist.

</details>

<details>

<summary>The 3D prompt shows but the key does nothing</summary>

Text UI only shows the prompt. Your script must read the key, for example `IsControlJustReleased(0, 38)` for `E`. See [Read the key in your script](/docs/striga-text-ui/3d-prompts.md#read-the-key-in-your-script).

</details>

<details>

<summary>How do I stop players from changing the look?</summary>

Set `Config.Ui.Settings = false` in `editable/config.lua`. Everyone then sees your config values and mode, and the `/hud` section is gone.

</details>

<details>

<summary>The color is not my HUD color</summary>

The player picked a color of their own. The order is: player color, then the Striga Tokyo HUD theme, then `Config.Ui.Accent`.

</details>

{% content-ref url="/pages/cJg4ereuFV8acLl6B5hc" %}
[Installation & Configuration](/docs/striga-text-ui/installation-and-configuration.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-text-ui/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.