Dependencies

3 min readUpdated Today

Dependencies

ML Inventory is an addon for ox_inventory. It installs inside your own ox_inventory folder and adds the grid, the clothing slots and the equipment systems on top of it. ML Clothing ships in the same package and runs as its own resource next to it.

Required

Resource | Why

ox_lib | Callbacks, keybinds, locale loading and progress helpers used by both resources.

oxmysql | Database driver. The tables your inventory uses today keep being used as they are.

ox_inventory | Your own copy. The download contains no ox_inventory file: you install into the folder you already run, or into a fresh copy from the official ox_inventory repository, which is free.

ml_bridge | Framework abstraction used by ML Clothing. Player identity, item and permission calls go through it, so the same build runs on ESX, QBCore and QBox. Get it from the Cfx.re portal.

Load order matters

ml_bridge and ml_inventory must start before ml_clothing. The ML Clothing manifest also registers a DLC_ITYP_REQUEST for the armor plate prop, so the resource must sit in your server data folder for that asset to stream.

Server config load order

server.cfg

1ensure oxmysql
2ensure ox_lib
3ensure ml_bridge
4ensure ml_inventory
5ensure ml_clothing

The ml_inventory line is your ox_inventory folder after the install. It is the only line that changes name: what used to read ensure ox_inventory now reads ensure ml_inventory.

Framework setup

ml_bridge detects your framework at runtime. The blocks below only differ in which core starts before the shared dependencies.

server.cfg

1ensure qb-core
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_inventory
6ensure ml_clothing

server.cfg

1ensure qbx_core
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_inventory
6ensure ml_clothing

server.cfg

1ensure es_extended
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_inventory
6ensure ml_clothing

server.cfg

1ensure oxmysql
2ensure ox_lib
3ensure ml_bridge
4ensure ml_inventory
5ensure ml_clothing

Auto detection

ml_bridge resolves the framework at runtime. There is no framework option to set inside ml_clothing. Player identity, inventory operations, item metadata and permission checks all go through Bridge.*, so the same build works on every supported core.

Appearance scripts

No appearance script is a dependency. ML Clothing works with whatever is running: it detects illenium-appearance, bl_appearance, 4bit_appearance, codem-appearance (also under its crm-appearance name), fivem-appearance and qb-clothing at startup and saves worn clothing back through the detected one. With none present it runs in native mode and keeps outfits in item metadata. The clothing and plate systems work either way.

The other direction, turning an outfit saved in the appearance menu into inventory items, is wired with one export or event call inside the appearance script:

lua

1exports.ml_clothing:syncFromNUI(appearanceData)
2-- or
3TriggerEvent('ml_clothing:client:syncFromNUI', appearanceData)

See Clothing Integration for the exact lines to add in illenium-appearance and bl_appearance, and for the adapter files in open/adapters/ that cover any other appearance script.