Skip to main content

​
Third-party integrations

Everything is configured in config/integrations.lua. Most options default to "auto" — the resource detects what’s running and adapts.
TypeSupported
Fuelox_fuel, LegacyFuel, ps-fuel, lj-fuel, cdn-fuel, okokGasStation, hyon_gas_station, nd_fuel, myFuel, ti_fuel, Renewed-Fuel, rcore_fuel
Vehicle keysqb-vehiclekeys, qs-vehiclekeys, wasabi_carlock, MrNewbVehicleKeys, mk_vehiclekeys, cd_garage, okokGarage, t1ger_keys, Renewed, tgiann-hotwire, jaksam’s vehicles_keys
Notificationsox_lib, okokNotify, ps-ui, framework default
Banking / societyqb-banking, qb-management, esx_addonaccount, Renewed-Banking, okokBanking, fd_banking
Gangsqb-gangs, rcore_gangs, framework default
TextUIox_lib, qb-DrawText, okokTextUI, ps-ui

​
Interaction style

Distance prompts are the default. Prefer targeting? Enable Integrations.target (ox_target or qb-target — a ped spawns at each garage) or Integrations.radial (ox_lib radial menu).

​
Something not on the list?

The adapters live in bridge/ — fully editable, never escrowed. Wire your fuel, keys or gang system in there without touching the core.

​
Exports for phone apps & external scripts

Server-side exports (see Features.phone to toggle): 
-- All vehicles belonging to a player, with garage, state and condition
local vehicles = exports.nex_garages:GetPlayerVehicles(src)

-- One vehicle by plate (owner or shared access only)
local vehicle = exports.nex_garages:GetVehicle(src, plate)

-- Set a waypoint + blip to a left-out vehicle for the player
exports.nex_garages:TrackVehicle(src, plate)
GetPlayerVehicles / GetVehicle return, per vehicle: 
{
  plate = "ABC123",
  name = "My Sultan",        -- nickname, or model if none set
  model = "sultan",
  garage = "Legion Square",
  state = "here",            -- "here" | "out" | "elsewhere" | "impounded"
  fuel = 80, engine = 95, body = 90,   -- percentages
  impounded = false,
  financed = false,
  mileage = 1234.5,
  owned = true,              -- false when the caller only has shared access
}

​
Hooks

config/hooks-client.lua ships with events that fire on store, impound, take-out and transfer, plus verification callbacks — return false from a verification to veto the action (e.g. custom job checks, key handouts, logging). config/hooks-server.lua is an empty stub reserved for your own server-side integrations.