Compatibility

Frameworks

Framework	Status	Notes
QBX Core (Qbox)	✅ Native	Default
QB-Core	✅ Native	Set Config.Framework = 'qb'
ESX (es_extended)	✅ Native	Set Config.Framework = 'esx'
Auto-detect	✅	Config.Framework = 'auto'

Optional integrations

Resource	Toggle	Effect
jg-mechanic	Config.Nitro.integration.useJGMechanic = true	ECU tablet shows live maintenance data (oil, brakes, tires) during scans
lc_fuel	Auto-detected if started	Aggressive tunes burn extra fuel (up to ~2.5x at extreme settings)

Inventory

Required: ox_inventory. The nitro kit and ECU tablet are both ox_inventory items. Not compatible with qb-inventory or qs-inventory out of the box.

Vehicle systems

Compatible with any vehicle persistence layer that uses stable plate keys (qbx_vehicles, qb-garage, esx_advancedgarage, etc.). Tunes persist via vehicle plate — if your garage system rotates plates, tunes won't survive a session.

Anti-cheat

The nitro applies a temporary power boost via ApplyForceToEntity and modifies max speed natively. Most anti-cheats accept this if the script is in their whitelist:

• FiveGuard — whitelist suty-drag in its resource policy
• Badger — usually no action needed
• Eulen-detect — whitelist suty-drag for vehicle speed/force checks

Other suty resources

Resource	Interaction
All other suty-	No conflicts

Known incompatibilities

• Some custom handling scripts that re-apply per-frame SetVehicleEnginePower will fight nitro's boost. Disable handling overrides on drag vehicles or use a vehicle-class exception.

Report issues on Discord.