> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementlabs.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported resources

> The frameworks, inventories, databases and interface resources products work with, by exact folder name.

Products do not replace the resources you already run. When a product needs a player's character,
an inventory, a database or a notification on screen, it uses yours. This page lists every resource
it recognises, by its exact folder name, in the order they are tried.

There is nothing to configure. A product looks only for what it actually uses, and the first
resource in the list that is running wins. To connect a resource that is not listed, see
[Use your own framework or resources](https://docs.elementlabs.net/scripting/custom-provider.md): a resource declared that way wins
over this list.

## Framework

| Order | Resource | Framework |
| - | - | - |
| 1 | `es_extended` | ESX |
| 2 | `qb-core` | QBCore |
| 3 | `qbx_core` | Qbox |

**Without one:** a product that needs a framework stops, and says so. Some products work without one
and their overview page says so: they show the player's FiveM name instead of the character name, and
read job, gang and money as empty.

## Inventory

| Order | Resource |
| - | - |
| 1 | `ox_inventory` |
| 2 | `qb-inventory` |
| 3 | `qs-inventory` |
| 4 | `origen_inventory` |
| 5 | `core_inventory` |
| 6 | `tgiann-inventory` |

**Without one:** a product that moves items stops.

`qb-inventory` cannot tell other resources that an item moved between two inventories. A product that
needs to know reports it and stops; [the qb-inventory swap hook](https://docs.elementlabs.net/scripting/qb-inventory-swap-hook.md)
adds what it asks for. No other inventory here needs an edit.

## Database

| Order | Resource |
| - | - |
| 1 | `oxmysql` |
| 2 | `mysql-async` |

**Without one:** a product that saves data stops. A product that saves nothing does not need one.

## Notifications

| Order | Resource |
| - | - |
| 1 | `ox_lib` |
| 2 | `qb-core` |
| 3 | `es_extended` |

**Without one:** the product draws its own.

## Help text

The prompt in the corner of the screen, such as "Press E to open".

| Order | Resource |
| - | - |
| 1 | `ox_lib` |
| 2 | `esx_textui` |

**Without one:** the product draws its own.

## Progress bars

| Order | Resource |
| - | - |
| 1 | `ox_lib` |
| 2 | `progressbar` |

**Without one:** the product draws its own.

## Fuel

| Order | Resource |
| - | - |
| 1 | `LegacyFuel` |
| 2 | `ox_fuel` |
| 3 | `cdn-fuel` |
| 4 | `ps-fuel` |

**Without one:** the product reads the vehicle's own fuel level.

## Menus

| Order | Resource |
| - | - |
| 1 | `ox_lib` |
| 2 | `qb-menu` |

**Without one:** menus fail. See below.

## Text input

| Order | Resource |
| - | - |
| 1 | `ox_lib` |
| 2 | `qb-input` |

**Without one:** text input fails. See below.

## Targeting

| Order | Resource |
| - | - |
| 1 | `ox_target` |
| 2 | `qb-target` |

**Without one:** targeting fails. See below.

## When a product finds nothing

The product prints one line naming what it looked for, the first time it needs that capability. That
can be at start, or later, when a player first does something that needs it:

```text theme={null}
[ERROR] [FrameworkAdapter] No supported Framework adapter detected. Checked: [es_extended, qb-core, qbx_core]
```

What happens next depends on where the capability is used:

* **Framework, inventory, database** (on the server): the product stops. The console shows it start,
  then stop a moment later.
* **Menus, text input, targeting** (in the player's game): the line appears in that player's own
  console (`F8`), followed by:

  ```text theme={null}
  [ERROR] [MenuAdapter] 'Menu' is unavailable for the rest of this session; the server side of 'element_3d_pausemenu' stops the resource when it needs the same capability.
  ```

  The product keeps running, and whatever needed the capability does not work.

In both cases: install one of the listed resources, start it before the product (see
[Start order](https://docs.elementlabs.net/configure/start-order.md)), and restart.

## See which resource a product chose

Turn on `el:debug` (see [Server settings](https://docs.elementlabs.net/configure/server-settings.md)). Each choice is printed once,
when the product first uses that capability:

```text theme={null}
[DEBUG] [FrameworkAdapter] Using "esx" adapter.
[DEBUG] [DatabaseAdapter] Using "oxmysql" adapter.
[DEBUG] [NotifyAdapter] Using "standalone" adapter.
```

`standalone` means none of yours was found and the product's own version is in use.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.