Dependencies

1 min readUpdated Today

Required

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

Framework

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

ml_bridge detects your framework automatically. No manual setup.

Optional

Garages

Any garage that deletes the vehicle entity on store is handled automatically. The open/client.lua file ships listeners for the common ones (qb-garages, qs-advancedgarages, jg-advancedgarages, cd_garage, loaf_garage, okokGarage, esx_advancedgarage). Add your garage's store event there if it is not listed.

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
No Garage Required

Persistence works without any garage script. Garage integration only controls when a vehicle leaves persistence.