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

# FAQ

Answers to the questions every Cuxial script shares: licensing, editable files, start order and interfaces.

General questions that apply to every script. For a specific script, open its Troubleshooting page.

## Licensing

<details>

<summary>How are the scripts licensed?</summary>

Cuxial scripts are delivered through the Cfx.re asset escrow system. The purchase is linked to the Cfx.re account that made it, and the script only runs on a server whose license key belongs to that same account.

You do not enter any key in the script. The check is done by FiveM when the resource starts.

</details>

<details>

<summary>Which files can I edit?</summary>

The files left open by the escrow system:

| File                | What it holds                                               |
| ------------------- | ----------------------------------------------------------- |
| `shared/config.lua` | The script's options.                                       |
| `data/*.lua`        | Editable data, in scripts that have this folder.            |
| `locales/*.json`    | Interface and notification texts.                           |
| `install/`          | SQL and item definitions, in scripts that have this folder. |

The rest of the code is protected and cannot be read or modified.

Cuxial Bridge is the exception: it is free and open source, and you download it from [GitHub](https://github.com/Cuxialv2/cuxial_bridge/releases/latest).

</details>

<details>

<summary>The console says "You lack the required entitlement"</summary>

**Cause.** The server's license key does not belong to the Cfx.re account that owns the script, or the purchase has not reached that account yet.

**Fix.** Check that `sv_licenseKey` in your server configuration was generated by the account that bought the script, then restart the server. If the purchase was made minutes ago, wait a little and restart again.

</details>

<details>

<summary>Can I move the script to another server?</summary>

Yes, as long as the other server uses a license key from the same Cfx.re account.

</details>

## Installation

<details>

<summary>The server says "Could not find dependency"</summary>

**Cause.** The resource named in the message is not installed, has a different folder name, or does not start before the script.

**Fix.** Install it, keep its original folder name and add its `ensure` line above the script. The full list is in [Requirements](/scripts/getting-started/requirements.md).

If the dependency named is `/onesync`, the missing piece is OneSync: enable it in txAdmin or with `set onesync on`.

</details>

<details>

<summary>In what order do I start everything?</summary>

`oxmysql` and `ox_lib`, then your framework, inventory and target, then `cuxial_bridge`, then the Cuxial scripts.

{% code title="server.cfg" %}

```cfg
ensure oxmysql
ensure ox_lib
ensure qbx_core
ensure ox_inventory
ensure ox_target

ensure cuxial_bridge

ensure cuxial_chat
```

{% endcode %}

Replace the framework, inventory and target lines with the ones your server uses. The order matters: Cuxial Bridge detects them when each script loads and cannot see what starts later.

</details>

<details>

<summary>Can I rename a script's folder?</summary>

Do not rename `cuxial_bridge`: every script loads it by that exact name. Keep the original folder name of the scripts too, since other resources refer to them by name.

</details>

<details>

<summary>Does it work with my framework?</summary>

Cuxial Bridge supports QBox, QBCore and ESX, with `ox_inventory` or `qb-inventory`, and `sleepless_interact`, `ox_target` or `qb-target`.

Some scripts require a specific framework. The script-by-script table is in [Requirements](/scripts/getting-started/requirements.md#framework-compatibility).

How the detection works is in [Cuxial Bridge](/scripts/getting-started/cuxial-bridge.md).

</details>

## Interface

<details>

<summary>The interface does not appear</summary>

Go through these in order:

1. **The script is not running.** Look for errors when it starts in the server console. A missing dependency or a wrong start order stops it before the interface loads.
2. **The interface files are missing.** The interface ships already built inside the script's `web` folder. If that folder was deleted or the upload was incomplete, copy the script again from the original download.
3. **There is an error in the F8 console.** Open it right after the interface should have appeared and read the last lines.
4. **Only one player is affected, and the cursor shows but the interface does not.** Their Windows clock is probably wrong. See [Common errors](/help/common-errors.md#the-cursor-appears-but-the-interface-does-not).

</details>

<details>

<summary>How do I change the language?</summary>

The scripts use the language set for `ox_lib`:

{% code title="server.cfg" %}

```cfg
setr ox:locale "en"
```

{% endcode %}

A file with that name must exist in the script's `locales` folder. The scripts ship with `en.json` and `es.json`.

</details>

<details>

<summary>How do I change a text?</summary>

Edit the text in `locales/<language>.json` and restart the script. Change only the text on the right of each line, never the key on the left.

The file must remain valid JSON. A missing comma or quote leaves the script without texts.

</details>

## Updates

<details>

<summary>Will I lose my configuration when I update?</summary>

Not if you follow [Updating a script](/scripts/getting-started/updating.md). Your options, data and texts live in files that are yours; the guide explains how to carry them to the new version.

</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://docs.cuxial.com/help/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.