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

# Troubleshooting

Fixes for the most common problems when installing a Waro Studios script.

Start here if a script doesn't start or doesn't behave as expected. Most problems are one of the issues below.

{% hint style="info" %}
**Where to look for errors**

* **Server console** (or txAdmin live console): messages from the server side, shown when the server starts or the script restarts.
* **F8 console** in game: messages from the client side, shown while you play.

Red text is an error. Yellow text from a Waro script is a setup tip.
{% endhint %}

## The script doesn't start: missing dependency

**What you see** in the server console:

```
Could not find dependency ox_lib for resource waro_casino.
```

**Why:** a resource the script needs isn't installed, isn't started, or its folder has the wrong name.

**Fix:**

1. Check the **Requirements** table on the script's page.
2. Make sure each required folder is in `resources` with the exact name (`waro_lib`, not `waro_lib-main`).
3. Make sure each one has an `ensure` line in `server.cfg`.

## Wrong start order

**What you see:** a script errors on start or can't find your framework.

**Fix:** use this order in `server.cfg`, then restart the whole server:

```cfg
ensure ox_lib
ensure oxmysql
ensure waro_lib
# framework here (qbx_core / qb-core / es_extended) and its resources
# Waro scripts last
```

{% hint style="warning" %}
If you use a folder like `[waro]` with `ensure [waro]`, the scripts inside start in alphabetical order. Put `ensure waro_lib` on its own line **above** your framework.
{% endhint %}

## "You lack the required entitlement" or the script won't load

**Why:** the escrowed script is linked to the Cfx.re account that bought it, and your server key belongs to a different account.

**Fix:** create your server key (`sv_licenseKey`) on the **same** Cfx.re account you used on Tebex. If you need the script moved to another account, open a [support ticket](/help/support.md).

## Items don't work or show as unknown

**Why:** many scripts give or use items (tools, food, spray cans and so on). Your inventory must know about those items first.

**Fix:**

1. Open the script's page and find the **items** snippet under **Installation**.
2. Paste it into the right file for your inventory:
   * **ox\_inventory:** `ox_inventory/data/items.lua`, inside `return { ... }`.
   * **qb-inventory / ps-inventory / lj-inventory:** `qb-core/shared/items.lua`, inside `QBShared.Items = { ... }`.
   * **ESX:** run the SQL line the script provides, if it has one.
3. Restart your inventory resource (or the server).

{% hint style="warning" %}
Don't add the same item name twice. Two scripts can use the same item name. If an item already exists, keep only one copy.
{% endhint %}

## Admin commands say "no permission"

**Why:** admin and test commands are protected by FiveM permissions (ACE). Your account must have them.

**Fix:** add the ACE lines from the script's page to `server.cfg`. For example:

```cfg
add_ace group.admin waro_casino.staff allow
```

And make sure your account is in `group.admin`:

```cfg
add_principal identifier.fivem:1234567 group.admin
```

## Text is in the wrong language

Waro scripts show text from their own config, not from a language file. To change the wording, edit the text in that script's `config.lua` (many scripts group it in a `locale` section) and restart the script.

Your framework and ox\_lib have their own language settings. Those only change text that comes from them.

## Database errors

**What you see:** errors mentioning `oxmysql`, `MySQL` or a table name.

**Fix:**

1. Make sure `oxmysql` starts **before** `waro_lib`.
2. Check your `mysql_connection_string` in `server.cfg` is correct.
3. Make sure the database user is allowed to create tables. Waro scripts create their tables on first start.

## I changed the config and nothing happened

Restart the script after every change (`restart waro_casino` in the console). If the script now won't start, look for a line number in the error: there's probably a missing comma or quote. See [Escrow & config](/getting-started/escrow-and-config.md#editing-safely).

## Still stuck?

Open a ticket on our Discord. See [Support](/help/support.md) for what to include.


---

# 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.warostudios.com/getting-started/troubleshooting.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.