For the complete documentation index, see llms.txt. This page is also available as Markdown.

Client Side

Client Side list of exports/events


GetVehicleProperties

Capture a full props table for garage persistence (mods, paint, neon, health, …).

local props = exports['op-mechanic']:GetVehicleProperties(vehicle)
  • vehicle: number (entity)

  • returns: table | nil


SetVehicleProperties

Apply a props table. Default uses a reliable multi-pass apply.

exports['op-mechanic']:SetVehicleProperties(vehicle, props)
exports['op-mechanic']:SetVehicleProperties(vehicle, props, false) -- single pass
  • vehicle: number

  • props: table

  • reliable: boolean? (true default)

  • returns: boolean


OpenTuning / CloseTuning / IsTuningOpen


OpenTablet / CloseTablet

Useful for radial menus or custom item handlers. Prefer inventory export useMechanicTablet when using mechanic_tablet.


GetVehicleMileage

Live mileage for HUDs. Reads state bag.


EnsureVehicleMileage

If the state bag is missing, loads DB mileage.


Nitro Exports

Get nitro state and all required data to connect it to your hud.

Item exports (inventory)

Used from inventory item definitions:

Kit unlock items (Tebex / item shops)

When Config.Nitro.requireInstallItem / Config.AntiLag.requireInstallItem is true, players use the kit on the vehicle to unlock mounting in the tuning menu. The item does not fit the kit by itself - install still happens in tuning (pay / work order).

Full setup: Require nitro & anti-lag install item.

ox_inventory example

Framework usable registration is also handled automatically by the resource when requireInstallItem = true (ESX / QB / Qbox via Fr.RegisterUsableItem).

Last updated