Dependencies

1 min readUpdated 2 weeks ago

Required

  • ml_bridge: Framework abstraction, inventory operations, item definitions, permissions
  • ox_lib: Callbacks, model loading, weapon asset loading
  • oxmysql: Stores the live admin item catalog (ml_propscarry_items)

Framework

server.cfg
1ensure oxmysql
2ensure qb-core
3ensure ox_lib
4ensure ml_bridge
5ensure ml_propscarry
server.cfg
1ensure oxmysql
2ensure qbx_core
3ensure ox_lib
4ensure ml_bridge
5ensure ml_propscarry
server.cfg
1ensure oxmysql
2ensure es_extended
3ensure ox_lib
4ensure ml_bridge
5ensure ml_propscarry
server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure ml_bridge
4ensure ml_propscarry
Auto Detection

ml_bridge detects your framework automatically. No manual setup.

Optional

  • ml_weaponskins: shows the applied weapon skin on carried weapons. Detected when it is started

Inventory

ml_bridge reads your items from the inventory you already run and detects it on its own. Any inventory ml_bridge supports works the same way.

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 without the extras.

Storage

Per-player custom positions use the server's FiveM KVP. The live admin item catalog (/carryadmin) persists to a single oxmysql table, ml_propscarry_items, created automatically on first start.