> 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/exports-and-events.md).

# Exports & Events

Open the character menu from your own scripts.

Striga Multicharacter has **no exports**. Framework, clothing and spawn calls all go through **striga-core**. Other scripts talk to the menu with the events below.

{% hint style="success" %}
**Quick start**

Send a player back to character select (server):\
`TriggerClientEvent('striga-multichar:client:open', source)`
{% endhint %}

***

## Events you can trigger

### striga-multichar:client:open

Client event. Opens the character select for that player.

```lua
-- server
TriggerClientEvent('striga-multichar:client:open', source)
```

{% hint style="warning" %}
Log the player out of the framework first. If the menu is already open, it does not open twice.
{% endhint %}

### qb-multicharacter:client:chooseChar

Client event. Kept for old housing and apartment scripts that fire it after a logout. It opens the character select, same as above. You do not need to change those scripts.

```lua
-- server
TriggerClientEvent('qb-multicharacter:client:chooseChar', source)
```

***

## Logout from other scripts

Any framework logout brings the player back to this menu by itself: the framework's own `/logout`, or a logout from another resource. striga-core turns them into one event, `striga-core:client:playerUnloaded`, and the menu listens to it.

To do it from your own script, log the player out with striga-core and open the menu (this is what `/logout` does):

```lua
-- server
local Core = exports['striga-core']:GetCore()
Core.logout(source)
TriggerClientEvent('striga-multichar:client:open', source)
```

***

## Settings hub and theme

Striga Multicharacter adds its player settings to the striga-core settings hub (icon `users`). Striga Tokyo HUD shows them in `/hud` after login. Changes made there show at the next character screen.

It also listens to `striga-core:client:theme`, so the menu color follows the suite theme unless the player picked a color.

See [Settings Hub & Theme](/docs/striga-core/settings-hub-and-theme.md) and [Events](/docs/striga-core/events.md) in the striga-core docs for `RegisterSettings`, `striga-core:client:settingsChanged` and `SetTheme` / `GetTheme`.

***

## Commands

| Command                                                          | Permission                           |
| ---------------------------------------------------------------- | ------------------------------------ |
| `/logout`                                                        | `command.logout` (not added on Qbox) |
| `/deletechar <citizenid>` then `/deletechar <citizenid> confirm` | `command.deletechar`                 |
| `/mcscene`                                                       | `command.mcscene`                    |

Command names can be changed in `Config.Commands`.

{% content-ref url="/pages/ZaoYoQ0QoVaxyzb8N7qa" %}
[Troubleshooting & FAQ](/docs/striga-multicharacter/troubleshooting-and-faq.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-multicharacter/exports-and-events.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.