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

# Troubleshooting & FAQ

Fixes for the most common Striga Chat problems.

<details>

<summary>I see two chat windows / every message twice</summary>

The default `chat` still runs. Remove `ensure chat` from `server.cfg`, set `set resources_useSystemChat false` and restart the server.

</details>

<details>

<summary>Plain text is not sent, the player gets "use a command"</summary>

`Config.UseChannels` is `false`, so the chat runs on commands only. Set it to `true` to get channel tabs and plain text. See [Channels & Commands](/docs/striga-chat/channels-and-commands.md).

</details>

<details>

<summary>/me or /ooc is the framework's one, not Striga Chat's</summary>

Another resource made the command first. Set `Override = true` on that command in `Config.Commands`. If you restarted your framework, restart `striga-chat` after it.

</details>

<details>

<summary>/me only reaches me</summary>

Nearby commands need **OneSync**. Turn it on in your server settings.

</details>

<details>

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

* Check `ensure striga-core` comes **before** `ensure striga-chat`.
* Check striga-core is 0.1.0 or newer. If it is too old, the server console shows a red error.

</details>

<details>

<summary>A script still calls exports.chat and nothing shows</summary>

Make sure the real `chat` resource is **not** started. Striga Chat provides `chat` and answers `exports.chat` calls, but only when it is the one running.

</details>

<details>

<summary>"do you have a lighter?" runs as a /do</summary>

Commands without a slash are on for every command (`Config.Slashless = 'all'`). Use a list without `do`, e.g. `{ 'me', 'try', 'roll' }`, or `{}` to turn it off.

</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 the chat panel and in `/hud`.

</details>

<details>

<summary>The chat does not follow the HUD color</summary>

The player picked an own chat color. Open the chat settings (or `/hud` > Chat) and set the color back to the HUD theme.

</details>

<details>

<summary>I see a red UPDATE line in the console</summary>

A newer Striga Chat is out. Download it from the link in that line. See [Updates & Versions](/docs/updates-and-versions.md).

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