> For the complete documentation index, see [llms.txt](https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/multichar.md).

# Multicharacter

**ghiaccio\_multichar v1.0.2** is a multicharacter, identity (ID card with photo), 3D spawn selector and pause menu for **ESX Legacy, QBCore and Qbox**, in a single resource with four modules. Every character is shown in a single scene and picked by clicking on them; it comes with automatic backups, staff commands and Tebex integration.

|                |                                                                                           |
| -------------- | ----------------------------------------------------------------------------------------- |
| **Price**      | 25 € / $29.99 (EUR includes VAT for Italy, USD base price)                                |
| **Store**      | [Buy on the official site](https://www.ghiaccioev.eu/scripts/ghiaccio-multichar)          |
| **Frameworks** | ESX Legacy, QBCore, Qbox (auto-detected)                                                  |
| **Requires**   | `oxmysql`. A recent FiveM server (artifact with `lua54`). Optional: an appearance script. |
| **Delivery**   | Cfx.re Asset Escrow ([portal.cfx.re](https://portal.cfx.re) > Granted Assets)             |
| **Languages**  | Italian, English (`Config.Locale`; more files in `locales/` are picked up automatically)  |

## Features

* **Single-scene selection**: every character of the account stands together in one scene (up to 10) and is picked by clicking on them. Hover highlights and shows a name tag, click selects, double click or Enter plays, arrows cycle. A free slot is a glowing placeholder: click it to create a character.
* **Identity** with ID card and photo, configurable fields and limits, unique names checked by the server.
* **3D spawn selector** with an aerial camera, points with job / gang / ACE filters, first spawn and last position.
* **Pause menu** with the character card and live server info, quick actions with shortcuts, keyboard and gamepad support.
* **`/relog`**: back to the selection with a server-side countdown, no way for a client to skip it.
* **Customizable loadscreen** with a local web editor (`editor.bat` / `editor.sh`).
* **Slots** from `Config.Slots`, ACE rules, `/gmc slots` or a Tebex grant; slots can be timed.
* **Automatic backups** before delete and wipe (14 days by default) and an audit log (console, database, optional Discord webhook).
* **Staff commands** `/gmc`: info, slots, lock, delete, wipe, backup restore, scene list, selftest, reload, import.
* **Import** of existing characters from `esx_multicharacter`, `qb-multicharacter` and Qbox. Existing characters show up with no migration.
* **Appearance adapters**: illenium-appearance, fivem-appearance, rcore\_clothing, qb-clothing, esx\_skin (+ skinchanger) or your own.
* Players **cannot delete** their own characters: only staff can, with a backup.

{% hint style="warning" %}
Multicharacter replaces your current multicharacter, spawn selector and loadscreen. Read [Installation](https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/multichar/installation.md) fully before touching a live server, and take a database backup.
{% endhint %}

Next step: [Installation](https://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/multichar/installation.md).


---

# 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://ghiaccioscripts.gitbook.io/ghiaccioscripts-docs/multichar.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.
