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

# Troubleshooting & FAQ

Fixes for common Striga Multicharacter problems.

<details>

<summary>Black screen, or nothing opens</summary>

Press F8 and look for red lines that start with `[striga-multichar]` or `[striga-core]`. `waiting for striga-core` means striga-core is not started or did not find your framework.

</details>

<details>

<summary>Two menus, or the old menu shows up</summary>

The default character menu of your framework is still running. See **Turn off your old character menu**.

</details>

<details>

<summary>ESX character does not load</summary>

`Config.Multichar` is not `true` in `es_extended/shared/config/main.lua`.

</details>

<details>

<summary>The preview ped has default clothes</summary>

The saved skin was made with a different clothing resource than the one running now.

</details>

<details>

<summary>The menu stopped after I restarted striga-core</summary>

FiveM stops this menu when striga-core stops. Run `ensure striga-multichar` again.

</details>

<details>

<summary>Players can not delete their characters</summary>

This is on purpose. Only admins can, with `/deletechar <citizenid>` and then `/deletechar <citizenid> confirm` within `Config.Commands.DeleteConfirmSeconds` (30 seconds).

</details>

<details>

<summary>A player has more (or fewer) slots than I set</summary>

Slots come from `Config.Slots.Default`, `ByLicense` and the ACE `striga.multichar.slots.<n>`, capped by `Config.Slots.Max`. Locked slots are never shown.

</details>

<details>

<summary>The /hud menu has no Multicharacter section</summary>

Striga Tokyo HUD must run, and striga-core must be 0.1.0 or newer. The section shows after login. The YouTube link is only in the menu's own Settings.

</details>

<details>

<summary>My server prints a red striga-core UPDATE line</summary>

A newer version is out. 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-multicharacter/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.