Dependencies

2 min readUpdated 2 weeks ago

Required

  • ml_bridge: the framework and inventory abstraction layer. Every player, item, and usable-item call in ML Random Cloth goes through it, which is what makes the resource work across ESX, QBCore, Qbox, and Standalone.
  • ox_lib: provides the progress bar used when opening a pack, and shared runtime helpers. Loaded as @ox_lib/init.lua.
  • ml_clothing: the companion this resource packs for. The pack items give real clothing items (jacket, pants, bag) that ml_clothing defines and handles, including bag stash metadata. ml_random_cloth is an addon for ml_clothing, not a standalone system. Start ml_clothing first.

ox_inventory is where the 15 standard pack_* items are registered and is what calls the usePack export on item use.

Framework Setup

Set your framework's resource name in server.cfg ahead of the dependency chain. ML Random Cloth itself detects the framework through ml_bridge and needs no framework key in its own config.

server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure qb-core
4ensure ox_inventory
5ensure ml_bridge
6ensure ml_clothing
7ensure ml_random_cloth
server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure qbx_core
4ensure ox_inventory
5ensure ml_bridge
6ensure ml_clothing
7ensure ml_random_cloth
server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure es_extended
4ensure ox_inventory
5ensure ml_bridge
6ensure ml_clothing
7ensure ml_random_cloth
server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure ox_inventory
4ensure ml_bridge
5ensure ml_clothing
6ensure ml_random_cloth
Auto Detection

ML Random Cloth does not have a framework setting. ml_bridge detects the active framework at runtime and routes every Bridge.* call to it. With Config.Debug = true the detected framework is printed on start: ml_random_cloth initialized (Framework: ...).

Optional

There are no optional integrations. ML Random Cloth talks only to ml_bridge, ox_lib, ml_clothing, and ox_inventory. It uses no custom interface, no database, and no other resource.