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

# Welcome to Waro Studios

Guides for installing, configuring and running Waro Studios FiveM scripts.

## What we make

Waro Studios makes cozy, immersive FiveM scripts with handcrafted interfaces. They work with **Qbox, QBCore and ESX**, and your framework is detected automatically.

Every script runs on [**waro\_lib**](/core/waro-lib.md), our free engine. It talks to your framework, inventory and banking, and saves player settings.

Browse the scripts in the sidebar under **Scripts**.

## New here?

Follow these pages in order:

1. [Requirements](/getting-started/requirements.md): what your server needs first.
2. [Installation](/getting-started/installation.md): download, drag in, and start in the right order.
3. [Escrow & config](/getting-started/escrow-and-config.md): how to change settings safely.
4. [Troubleshooting](/getting-started/troubleshooting.md): if something doesn't work.

{% hint style="success" %}
You don't need to import any SQL. Every script creates its own database tables the first time it starts.
{% endhint %}

## Where to buy

All Waro Studios scripts are sold on [warostudios.com](https://warostudios.com). After you buy, the script appears in your [Cfx.re portal](https://portal.cfx.re) (Keymaster), ready to download.

## Getting help

Join our **Discord** and open a ticket. See [Support](/help/support.md) for what to include so we can help you quickly.


---

# 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/readme.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.
