> For the complete documentation index, see [llms.txt](https://striga.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://striga.gitbook.io/docs/striga-inventory/qbox-and-esx.md).

# Qbox & ESX

The ox\_inventory mode for Qbox and ESX. Ready on the inventory side, waits for a striga-core update.

{% hint style="danger" %}
**Not ready for a live server yet.** The inventory side is done, but loading and saving player inventories on Qbox and ESX comes with a **striga-core** update. Until then players start with an empty inventory and nothing is saved. Use it on a test server only.
{% endhint %}

On Qbox and ESX, Striga Inventory takes the name `ox_inventory`. qbx\_core, es\_extended and scripts made for ox\_inventory keep calling `exports.ox_inventory` with no edits.

## Mode

`Config.Compat` in `editable/config.lua`:

| Value              | What it does                                                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `'auto'` (default) | Picks `'ox'` when the convar `inventory:framework` is set, qbx\_core or es\_extended is installed, or striga-core runs on Qbox / ESX. Otherwise `'qb'` |
| `'qb'`             | QBCore: answers `exports['qb-inventory']`                                                                                                              |
| `'ox'`             | Qbox / ESX: answers `exports.ox_inventory`                                                                                                             |

Only one of the two runs.

## Setup

{% tabs %}
{% tab title="Qbox" %}

1. In `striga-inventory/fxmanifest.lua`: comment out `provide 'qb-inventory'`, turn on `provide 'ox_inventory'`, and set `version '2.45.0'` (qbx\_core checks the ox\_inventory version).
2. Move the `ox_inventory` folder out of `resources`.
3. In `server.cfg`: `setr inventory:framework "qbx"`, and start Striga Inventory **before** qbx\_core.
4. Items live in `striga-inventory/data/items.lua` and `data/weapons.lua` (ox format). Copy your old ox item entries in.
   {% endtab %}

{% tab title="ESX" %}

1. The same `fxmanifest.lua` change (`provide 'ox_inventory'` + `version '2.45.0'`).
2. Move the `ox_inventory` folder out of `resources`.
3. Start Striga Inventory **before** es\_extended. ESX switches to ox mode by itself.
4. Items live in `data/items.lua` and `data/weapons.lua`. The ESX `items` table is not read.
   {% endtab %}
   {% endtabs %}

Old ox\_inventory data: convert it with `strigaconvert ox`. See [Converting from another inventory](/docs/striga-inventory/converting-from-another-inventory.md).

## What works

* The ox server exports used by qbx\_core, es\_extended and most scripts: `AddItem`, `RemoveItem`, `SetItem`, `GetItem`, `GetItemCount`, `GetSlot*`, `Search`, `CanCarryItem`, `RegisterStash`, `RegisterShop`, `forceOpenInventory`, `Items`, hooks and more.
* The common ox client exports: `Search`, `GetItemCount`, `openInventory`, `closeInventory`, `useItem`, `getCurrentWeapon`...
* `money` is the cash item.
* ox ammo items (`ammo-9`, `ammo-rifle`...) work with the [weapon pack](/docs/striga-inventory/weapons.md).

Not supported: containers inside items, ox crafting benches, `SwapSlots`, `InspectInventory`, `ConvertItems`.

{% content-ref url="/pages/yy0mE6nWWVGSu4FcUSAz" %}
[Exports & Events](/docs/striga-inventory/exports-and-events.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-inventory/qbox-and-esx.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.