> 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/common-errors.md).

# Common errors

Errors that can show up with any Cuxial script, with their cause and fix.

Errors that are not tied to one script. Each entry gives the symptom, why it happens and how to fix it.

## On the player's side

### The cursor appears but the interface does not

**Symptom.** A player opens a menu and gets the mouse cursor, but nothing is drawn on screen. Other players on the same server see it correctly.

**Cause.** The date or time of that player's Windows is far from the real one. With a badly wrong clock, interfaces can fail to display even though the script has opened them.

**Fix.** Synchronize the Windows clock, then restart FiveM.

{% stepper %}
{% step %}

## Open the date and time settings

Windows **Settings** → **Time & language** → **Date & time**.
{% endstep %}

{% step %}

## Turn on automatic time

Enable **Set time automatically** and **Set time zone automatically**.
{% endstep %}

{% step %}

## Synchronize

Press **Sync now**, close FiveM completely and join again.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
A quick way to tell this apart from a server problem: if it happens to one player only, it is their computer. If it happens to everyone, look at the server console.
{% endhint %}

## On server start

<details>

<summary>Could not find dependency ... for resource ...</summary>

**Cause.** A required resource is missing, has been renamed or starts after the script.

**Fix.** Install the resource named in the message and place its `ensure` above the script. See [Requirements](https://app.gitbook.com/s/aRpo4HjLxwhtq0SBsDxE/getting-started/requirements).

</details>

<details>

<summary>Could not find dependency /onesync</summary>

**Cause.** OneSync is off. Every Cuxial script requires it.

**Fix.** Enable OneSync in txAdmin, or add `set onesync on` to your server configuration, and restart the server.

</details>

<details>

<summary>You lack the required entitlement to use ...</summary>

**Cause.** The server's license key does not belong to the Cfx.re account that owns the script.

**Fix.** Use a license key generated by the account that bought it and restart the server. More in the [FAQ](/help/faq.md).

</details>

<details>

<summary>The script fails to load after uploading it by FTP</summary>

**Cause.** The upload was incomplete or files were altered in transit. Protected scripts need every file intact, including the `.fxap` file in the script's folder.

**Fix.** Delete the folder on the server and upload it again from the original download. Make sure hidden files and files without a known extension are included.

</details>

<details>

<summary>[cuxial_bridge] aviso: no se detectó framework, usando fallback "qbox"</summary>

**Cause.** No supported framework was running when the script loaded, so Cuxial Bridge assumed QBox.

**Fix.** Start your framework before `cuxial_bridge` and before the Cuxial scripts. If your framework's folder has a non-standard name, force it as explained in [Cuxial Bridge](https://app.gitbook.com/s/aRpo4HjLxwhtq0SBsDxE/getting-started/cuxial-bridge).

</details>

<details>

<summary>An error mentions @cuxial_bridge/init.lua or @ox_lib/init.lua</summary>

**Cause.** `cuxial_bridge` or `ox_lib` is missing, renamed or started after the script.

**Fix.** Keep the original folder names and start both before any Cuxial script.

</details>

<details>

<summary>A database error says a table does not exist</summary>

**Cause.** The script's SQL was not run, or it was run on a different database from the one `oxmysql` connects to.

**Fix.** Run the SQL files from the script's `install` folder on the database your server uses. The script's installation page lists them.

</details>

## After editing files

<details>

<summary>The script stops starting after editing the configuration</summary>

**Cause.** A syntax error in `shared/config.lua` or in a `data/*.lua` file: a missing comma, quote or closing brace.

**Fix.** The server console shows the file and line. Correct it, or restore the file from your backup, and restart the script.

</details>

<details>

<summary>Texts are missing or show as codes</summary>

**Cause.** The language file is not valid JSON after an edit, or the language set in `ox:locale` has no file in the script's `locales` folder.

**Fix.** Validate the JSON file and check that the language file exists. See "How do I change the language?" in the [FAQ](/help/faq.md).

</details>

<details>

<summary>My changes are not applied</summary>

**Cause.** The script was not restarted, or the edited folder is not the one the server loads.

**Fix.** Restart the script, or the whole server. If you keep an old copy of the script inside `resources`, remove it: the server may be loading that one.

</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/common-errors.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.