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

# Requirements

What your server needs before you install a Waro Studios script.

## Server

* A FiveM server on a **recent server artifact**. Keep your artifact up to date; old artifacts can fail to start current resources.
* **OneSync** turned on. It is on by default on current servers and always on with Qbox. Some scripts need it; their pages say so.
* A **MySQL or MariaDB** database, connected through `oxmysql`.

## Framework

Waro scripts work with these frameworks. Your framework is detected automatically, so there is nothing to set.

| Framework | Resource name |
| --------- | ------------- |
| Qbox      | `qbx_core`    |
| QBCore    | `qb-core`     |
| ESX       | `es_extended` |

{% hint style="info" %}
A few scripts have their own framework notes. Always check the **Requirements** section on each script's page.
{% endhint %}

## Shared resources

Every Waro script needs these three resources. Install them once and every script uses them.

| Resource   | What it is                                                                                                         | Where to get it              |
| ---------- | ------------------------------------------------------------------------------------------------------------------ | ---------------------------- |
| `ox_lib`   | A common library many FiveM scripts use.                                                                           | Overextended (free, GitHub)  |
| `oxmysql`  | Connects scripts to your database.                                                                                 | Overextended (free, GitHub)  |
| `waro_lib` | Our free engine: framework, inventory and banking bridge, and player settings. See [waro\_lib](/core/waro-lib.md). | Comes free with every script |

Menus, notifications and dialogs outside a script's own screens use ox\_lib.

{% hint style="warning" %}
Some scripts need extra resources such as `ox_inventory` or `pma-voice`. The **Requirements** table on each script's page is the final word.
{% endhint %}

## Optional resources

Some scripts work better with, or can use, other resources you may already run:

* **Inventory:** `ox_inventory`, `qb-inventory`, `ps-inventory` or `lj-inventory`, or the ESX default inventory. `waro_lib` detects which one you use.
* **Company accounts:** Renewed-Banking, qb-banking, qb-management or esx\_society. `waro_lib` detects which one you use.
* **Targeting:** some scripts use `ox_target` if it is running, and an **E** prompt if it isn't.

Next: [Installation](/getting-started/installation.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/requirements.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.