Dependencies

2 min readUpdated 2 weeks ago

Required

  • ml_bridge: framework abstraction: inventory operations, item metadata, usable items, vehicle targets, notifications, permissions, logging
  • ox_lib: callbacks, points, context menus, skill checks.
  • ox_inventory: the reference inventory. Jerry cans and power cells store their fuel as item metadata, so any inventory ml_bridge supports with metadata works, not only this one.
  • oxmysql: stores per-plate fuel conversions and tank upgrades

Framework

server.cfg
1ensure qb-core
2ensure oxmysql
3ensure ox_lib
4ensure ox_inventory   # or your inventory
5ensure ml_bridge
6ensure ml_fuel
server.cfg
1ensure qbx_core
2ensure oxmysql
3ensure ox_lib
4ensure ox_inventory   # or your inventory
5ensure ml_bridge
6ensure ml_fuel
server.cfg
1ensure es_extended
2ensure oxmysql
3ensure ox_lib
4ensure ox_inventory   # or your inventory
5ensure ml_bridge
6ensure ml_fuel
server.cfg
1ensure oxmysql
2ensure ox_lib
3ensure ox_inventory   # or your inventory
4ensure ml_bridge
5ensure ml_fuel
Auto Detection

ml_bridge detects your framework, inventory and target resource on its own.

Optional

Minigames

  • mgc: extra minigame pool for scavenge and siphon actions. The provider file self-skips when the resource is not started
  • ps-ui: same as above
Fallback

ox_lib skill checks are always registered, so scavenge minigames work with no extra resource installed.

Dispatch

A failed scavenge or siphon minigame can alert police jobs through Bridge.AlertDispatch. It uses whatever dispatch system ml_bridge detects on your server. Configured per feature via minigame.onFail.alertDispatch.

Base Building

  • Outpost (ml_base_building): generators are refuelled from ML Fuel jerry cans through the hold-to-pour panel