> For the complete documentation index, see [llms.txt](https://docs.valoragaming.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valoragaming.com/getting-started/dependencies.md).

# Dependencies

Valora is built on the modern **ox** stack. Install these once and they serve the whole suite. Each script's page lists exactly which of these it needs.

## Required (almost everywhere)

| Dependency  | What it does                                                                                               | Link                                                            |
| ----------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| **ox\_lib** | Core library — callbacks, notifications, context menus, cache, points. Required by every Valora resource.  | [overextended/ox\_lib](https://github.com/overextended/ox_lib)  |
| **oxmysql** | Database layer. Required by any script that persists data (registrations, garages, marketplace, blips, …). | [overextended/oxmysql](https://github.com/overextended/oxmysql) |

## Common

| Dependency        | Used by                                                       | Link                                                                       |
| ----------------- | ------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **ox\_target**    | Interaction targeting (e.g. `vlr_sitsys`, registration NPCs). | [overextended/ox\_target](https://github.com/overextended/ox_target)       |
| **ox\_inventory** | Item handling (e.g. `vlr_armour` vests/plates/kits).          | [overextended/ox\_inventory](https://github.com/overextended/ox_inventory) |

## Framework compatibility

Valora auto-detects your framework — you do **not** configure it. Each script carries a **bridge** with a real, separate code path per framework, resolved in this order:

1. **qbx\_core** (QBox)
2. **qb-core** (QBCore)
3. **es\_extended** (ESX)

Most of the suite runs on **all three**, and several scripts also run **standalone** (no framework) where that makes sense. Each script's own page states exactly what it needs.

{% hint style="info" %}
**"Built on ox\_lib" does not mean "QBox only."** `ox_lib`, `ox_target` and `ox_inventory` are **standalone, framework-agnostic** libraries — they work identically on ESX, QBCore and QBox. (QBox depends on `ox_lib`, not the other way around; `ox_inventory` selects your framework with a single `setr inventory:framework "esx|qb|qbx"` convar.) So a script that requires `ox_inventory` or `ox_target` is **not** locked to one framework.

QBox is a modern fork of QBCore and keeps a `qb-core` compatibility bridge, so QBCore and QBox behave almost identically for our scripts — and every Valora script also ships a **native QBox path**, not just the compatibility shim.
{% endhint %}

The one product that is **framework-specific** is **vlr-multicharacter** (QBox / QBCore only — never ESX), because a character selector wires directly into the framework's own character-creation flow and database schema. Its page says so plainly. Scripts that need no framework at all (e.g. `vlr_uipack`, `vlr_loading`) list Framework as *None / standalone*.

## Optional integrations

Some scripts light up extra features when a partner resource is present, but never require it:

| Integration                      | Enhances                                                              |
| -------------------------------- | --------------------------------------------------------------------- |
| **nc-banking** (NoxCore Banking) | Society / business bank accounts (registration centers, mechanic).    |
| **lb-tablet**                    | MDT records (vehicle registration data in police/mechanic tablets).   |
| **t1ger\_mechanic**              | Vehicle part-health used by the technical inspection in `vlr_vehreg`. |

{% hint style="warning" %}
Always start dependencies **before** the Valora resource in your `server.cfg`. A script that can't find `ox_lib` on start will refuse to run.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.valoragaming.com/getting-started/dependencies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.