Introduction

LX Studios builds premium FiveM resources that work on Qbox and QB-Core from a single purchase — no separate framework editions. ESX is not supported.

How LX products are built

Every LX product is made of up to three resources:

Resource	Role
The product (e.g. lx-busjob)	The gameplay script you bought
lx-lib	Framework bridge — detects Qbox / QB-Core and provides one shared API for money, items, jobs, and notifications
lx-navigation	Transit navigation engine — GPS guidance, turn instructions, and driver HUD (used by transport products)

lx-lib and lx-navigation are included with your purchase. You install them once; future LX products reuse them.

Requirements

• A FiveM server with OneSync enabled (server build 7290+)
• One supported framework: qbx_core or qb-core
• ox_lib — hard dependency of Advanced Bus Job; optional for lx-lib notifications
• oxmysql — Advanced Bus Job career stats / contracts
• Inventory recommended for the broader stack: ox_inventory or qb-inventory — optional to lx-lib and the current Advanced Bus Job loop (item APIs stub safely when none is detected)
• QB-Core only: Community Bridge when using the ox stack (ox_lib / ox_inventory). Not required on Qbox.

Optional fuel, vehicle-key, and target integrations are configured per product — none are hard dependencies. Framework cash payouts do not require a banking script. lx-navigation has no framework or ox_lib dependency.

Next steps

1. Install the resources
2. Understand escrow and updating
3. Configure your product — for Advanced Bus Job start at the overview