# Dependencies

> Required and optional dependencies for ML PropsCarry

Category: ITEM CARRY · Source: https://miciomods.it/docs/ml-propscarry-dependencies · Last updated: 2026-08-18

## Required

- [ml_bridge](https://portal.cfx.re): Framework abstraction, inventory operations, item definitions, permissions
- [ox_lib](https://github.com/overextended/ox_lib): Callbacks, model loading, weapon asset loading
- [oxmysql](https://github.com/overextended/oxmysql): Stores the live admin item catalog (`ml_propscarry_items`)

## Framework

**QBCore**

**server.cfg**

```cfg
ensure oxmysql
ensure qb-core
ensure ox_lib
ensure ml_bridge
ensure ml_propscarry
```

**Qbox**

**server.cfg**

```cfg
ensure oxmysql
ensure qbx_core
ensure ox_lib
ensure ml_bridge
ensure ml_propscarry
```

**ESX**

**server.cfg**

```cfg
ensure oxmysql
ensure es_extended
ensure ox_lib
ensure ml_bridge
ensure ml_propscarry
```

**Standalone**

**server.cfg**

```cfg
ensure oxmysql
ensure ox_lib
ensure ml_bridge
ensure ml_propscarry
```

> **INFO:** Auto Detection
>
> `ml_bridge` detects your framework automatically. No manual setup.

## Inventory

[ml_bridge](https://portal.cfx.re) reads your items from the inventory you already run, and detects it on its own. Supported: ox_inventory, qb-inventory, lj-inventory, ps-inventory, qs-inventory, codem-inventory, core_inventory, origen_inventory, tgiann-inventory, one_inventory, devix-inventory, jaksam_inventory and ak47_inventory. Nothing in ML PropsCarry changes from one to the next.

> **INFO:** Weapon attachments and tint
>
> The attachments, tint and skin shown on a carried weapon come from what your inventory keeps on that weapon. On an inventory that does not store weapon metadata, the weapon still shows on the body, just without the extras.

> **INFO:** Storage
>
> Per-player custom positions use FiveM KVP. The live admin item catalog (`/carryadmin`) persists to a single `oxmysql` table, `ml_propscarry_items`, created automatically on first start.