> 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/help/support.md).

# Support

How to get help with a Waro Studios script.

## Before you open a ticket

Many problems are quick to fix yourself:

1. Check the script's **Requirements** and **Installation** sections.
2. Read [Troubleshooting](/getting-started/troubleshooting.md).
3. Make sure you're on the latest version (see [Updating](/getting-started/updating.md)).

## Opening a ticket

1. Join the **Waro Studios Discord**.
2. Go to the support channel and open a **ticket**.
3. Fill in the details below in your first message.

{% hint style="info" %}
We may ask for your **Tebex transaction ID** to confirm your purchase. It's in your Tebex receipt email.
{% endhint %}

## What to include

The more of this you send, the faster we can help:

| What                                    | Where to find it                                                        |
| --------------------------------------- | ----------------------------------------------------------------------- |
| **Script and version**                  | The `version` line in the script's `fxmanifest.lua`.                    |
| **Server artifact**                     | The build number shown at the top of your server console or in txAdmin. |
| **Framework**                           | Qbox, QBCore or ESX, and its version if you know it.                    |
| **Inventory**                           | For example ox\_inventory or qb-inventory.                              |
| **Server console errors**               | Copy the red text from the server console or txAdmin live console.      |
| **F8 errors**                           | Press **F8** in game and copy any red text, or send a screenshot.       |
| **Your config**                         | Attach your `config.lua` if you changed it.                             |
| **Start order**                         | The `ensure` lines from your `server.cfg`.                              |
| **What you expected and what happened** | Short steps we can follow to see the problem.                           |

{% hint style="warning" %}
Remove passwords, your license key (`sv_licenseKey`) and your database connection string before you send any file.
{% endhint %}

## Bug reports and ideas

Found a bug, or have an idea for a script? Tell us in a ticket on Discord. Early access feedback helps shape 1.0.


---

# 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/help/support.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.