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

# Troubleshooting & FAQ

Fixes for the most common Striga Notify questions.

<details>

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

* Check `striga-core/config.json` has `"notify": "striga-notify"`.
* Check `ensure striga-notify` comes **after** `ensure striga-core` in `server.cfg`.
* Check the server console for a red striga-core error. If striga-core is too old, update it.
* For other scripts, check you did the step for your framework on the [Integration](/docs/striga-notify/integration.md) page.

</details>

<details>

<summary>Striga Notify does not start</summary>

Striga Notify needs **striga-core 0.1.0 or newer**, started before it. Without striga-core it does not start. With an older striga-core, striga-core stops it and prints a red error in the server console.

</details>

<details>

<summary>I see every notification twice (ESX)</summary>

`esx_notify` is still running. Remove `ensure esx_notify` from `server.cfg` and restart the server. Keep the folder.

</details>

<details>

<summary>A notification shows in a different place than the script wanted</summary>

This is on purpose. All notifications show in one tidy list, at the position the player (or your config) picked.

</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, in `/notifysettings` and in `/hud`.

</details>

<details>

<summary>The color does not follow my HUD theme</summary>

The player picked an own color. In `/notifysettings` (or the **Notifications** block in `/hud`) switch the color back to the theme, or press **Reset**.

</details>

<details>

<summary>A player wants the default look back</summary>

Open `/notifysettings` and press **Reset**.

</details>

<details>

<summary>A server script sends many notifications and some are missing</summary>

The server `Notify` export sends at most **20 notifications per second** to the same player. More are dropped, so a loop can not flood a player.

</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 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-notify/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.