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

# Installation

Download a script, add it to your server and start everything in the right order.

This guide works for every Waro Studios script. Each script's own page lists anything extra, such as items or permissions.

## 1. Buy and download

1. Buy the script on [warostudios.com](https://warostudios.com).
2. Log in to the [Cfx.re portal](https://portal.cfx.re) with the same Cfx.re account you used at checkout.
3. Open **Granted assets** (Keymaster). Your script is listed there, along with `waro_lib` (free).
4. Download both and unzip them.

{% hint style="warning" %}
Scripts are locked to the Cfx.re account that bought them. Your server's license key must belong to that same account, or the script will not start.
{% endhint %}

## 2. Drag into resources

Drag each folder into your server's `resources` folder. Keep the folder names exactly as they are (for example `waro_casino`, not `waro_casino-main`).

## 3. Add to server.cfg in the right order

Open `server.cfg` and add the `ensure` lines in this order:

1. `ox_lib`
2. `oxmysql`
3. `waro_lib`
4. Your framework and its resources
5. Your Waro scripts

```cfg
ensure ox_lib
ensure oxmysql
ensure waro_lib

# Your framework (Qbox example)
ensure qbx_core

# Waro Studios scripts
ensure waro_casino
```

## 4. Do the script's extra steps

Some scripts need a little more. Check the **Installation** section on the script's page for:

* **Items** to add to your inventory (for example to `ox_inventory/data/items.lua`).
* **Permission (ACE) lines** for staff commands.

## 5. Restart

Restart your server. You're done.

{% hint style="success" %}
**No SQL to import.** Every Waro script creates its own database tables the first time it starts.
{% endhint %}

Something not working? See [Troubleshooting](/getting-started/troubleshooting.md).


---

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