Dependencies

Required

• ml_bridge: Framework and inventory abstraction, ownership lookups, notifications, logging
• ox_lib: Vehicle property serialization and the shared cache
• oxmysql: Database access

Framework

1ensure qb-core
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_vehicle_persistence

1ensure qbx_core
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_vehicle_persistence

1ensure es_extended
2ensure oxmysql
3ensure ox_lib
4ensure ml_bridge
5ensure ml_vehicle_persistence

1ensure oxmysql
2ensure ox_lib
3ensure ml_bridge
4ensure ml_vehicle_persistence

Optional

Garages

With the default Config.RespawnOnExternalDelete = false, any garage that deletes the vehicle entity on store is handled on its own. open/client.lua ships store-event listeners for several common garages.

Inventory

• Any inventory supported by ml_bridge: only needed for the GPS item, the scanner and the module. Definitions are in _INSTALL/items.lua. Both features can be disabled in the config, and persistence itself needs no inventory

Impound

• Any impound system: orphaned owned vehicles route through OpenServer.ImpoundVehicle, adaptable to your impound tables

Fuel

• Any fuel system supported by ml_bridge: fuel level is saved and restored with the vehicle

Admin Integrations

• ml_mechanic: Odometer and part condition in vehicle inspection; part repair and condition actions.
• ml_fuel: Fuel type, fuel level and tank upgrades in vehicle inspection. Fuel level actions require the vehicle entity to be spawned.
• ml_vehiclekeys: Key, lock and access actions in vehicle inspection.
• ml_base_building: Base link, raid gate and crew GPS options.

The Integrations page reports which optional resources are active. Provider files in open/integrations/ load automatically; the example provider must be configured and enabled before use.