Scripts That Run on a Qbox Build

Everything filed here names Qbox among the frameworks it supports. Qbox ships with more already wired in than the frameworks it descends from, so much of what you would add elsewhere is a configuration question here instead. Check the listing before buying something your core already does.

Scripts That Run on a Qbox Build - Qbox Scripts

Scripts in this category

120 products
FiveM Weapon Attachment UI - Gun Customization New
  • ESX
  • QBCore
  • Qbox

Weapon Attachment UI

Visual FiveM weapon attachment UI with inventory persistence, addon weapon support, job/item gates, and 0.01ms active cost. Standalone or integrated with ox, ESX & QBCore inventory.

$4.99
FiveM Scuba Diving Script | Advanced Underwater RP Sale
  • ESX
  • QBCore
  • Qbox

Advanced Scuba Diving V3

Advanced Scuba Diving V3 builds a full underwater economy: boat rental, oxygen-tracked dive tanks, shipwreck loot, skill-based crate minigames, and a quest system with XP leaderboard. ESX, QBCore, Qbox — one purchase.

$9.00 $10.00
FiveM Slaughterhouse Job Script – ESX, QBCore & Qbox Sale
  • ESX
  • QBCore
  • Qbox

Realistic Slaughtering Job /w Animations

FiveM slaughterhouse job with a full catch-to-grind processing chain, XP-gated success rates, dynamic market pricing, and dual delivery options for ESX, QBCore and Qbox servers.

$15.00 $30.00
Free FiveM Dodgeball Script | 1v1 to 5v5 Minigame
  • ESX
  • QBCore
  • Qbox

FREE FiveM Dodgeball Game

Free standalone FiveM dodgeball script with 1v1 to 5v5 match formats and a Vespucci Beach court included. No framework dependency — compatible with ESX, QBCore, Qbox, and Gamzky Scripts.

FREE
FiveM Police Vehicle Trunk - Interactive Storage Popular
  • ESX
  • QBCore
  • Qbox

Police Vehicle Trunk

Give FiveM officers a proper equipment trunk — visual prop layout, per-vehicle item config, clothing slots, job-gated access, and 0.03ms active usage. ESX, QBCore & Qbox.

$10.00
FiveM Gun Menu Script – CS2-Style Weapon Shop
  • ESX
  • QBCore
  • Qbox

GFX GunMenu for FiveM

CS2-style FiveM gun menu with configurable colors, stock, and pricing. Delivers weapons to inventory or hand. Minimal setup. ESX, QBCore, Qbox and standalone compatible.

$10.00
FiveM Outfit Items Script – Job Uniform Shop QBCore
  • ESX
  • QBCore
  • Qbox

Outfit Items

FiveM outfit items script with job and grade-based access, live character previews, and wearable inventory items that apply full uniforms instantly. QBCore, ox_inventory, ox_target ready.

$6.00
FiveM Electrician Job Script – 0.00ms, ESX & QBCore
  • ESX
  • QBCore
  • Qbox

FiveM Electrician Job

FiveM electrician job with a 4×4 circuit-board puzzle, randomized fusebox dispatch, auto-detecting ESX and QBCore support, and a verified 0.00ms active resmon — white-collar civilian work at £5.99.

$5.99
FiveM Pay and Spray | Multi-Location Vehicle Shop
  • ESX
  • QBCore
  • Qbox

Pay And Spray

Per-location Pay and Spray script for FiveM with individual pricing, job locking, livery preview, chameleon paint, and vehicle repairs. Runs on ESX, QBCore, and Qbox with broad inventory, banking, and fuel compatibility.

$6.00
FiveM Vehicle Respray RGB Script — JG Mechanic Sale
  • ESX
  • QBCore
  • Qbox

JG Mechanic Script

JG Mechanic gives FiveM servers a full RGB and chameleon respray system, OneSync-synced visuals, engine swaps, dyno testing, and mileage-based servicing at 0.0-0.1ms resmon on ESX, QBCore, and Qbox.

$24.90 $30.00

Qbox arrives with more in the box

Multicharacter, the join queue, and multijob and multigang handling live inside
qbx_core. ox_lib, ox_inventory and ox_target cover a lot of what separate
resources provide on other stacks. The practical effect is that a Qbox build needs
fewer add-ons than a bare framework install, and the first thing worth checking on
any listing is whether it duplicates something you already have.

Check these before you install

  • Does qbx_core already do it? The most common wasted purchase on a Qbox
  • server is a resource replacing a built-in.
  • The ox dependencies. Most Qbox-targeted resources expect ox_lib, and item
  • work expects ox_inventory. These are assumptions, not options.
  • Targeting. ox_target is the usual hook. A resource written for a different
  • targeting system needs adapting.
  • QBCore-era code. Some resources support Qbox through a compatibility layer
  • rather than natively. That is not automatically worse, but it is worth knowing.

Compatibility labels are a filter, not a verdict

A resource listed here supports Qbox. Whether it suits your server is a separate
judgement made from the requirements, the preview media and the feature list on
its own page.

Related shelves

The same catalogue filtered by the other frameworks sits under
QBCore and ESX. For a server
assembled up front, see the readymade builds, and for
the map layer, the MLO interiors.

Frequently asked questions

Do Qbox resources need the ox stack?

Usually. ox_lib is a near-universal dependency, item handling expects ox_inventory, and interaction scripts generally hook ox_target. Each listing names what it requires.

Will a QBCore resource run on Qbox?

Some do, because Qbox retains a degree of compatibility, and some are explicitly built for both. Others rely on qb-core internals that are not present. The framework labels on each listing are the place to check rather than assuming.

Why are there fewer resources here for things like multicharacter?

Because qbx_core already handles them. Multicharacter, the join queue and multijob are built in, so there is less to add.

Does Qbox support mean the resource was written for Qbox?

Not always. Some are native, others reach Qbox through a compatibility layer around QBCore code. The listing's requirements and version notes are the place that distinction shows up.

Can I mix Qbox and ESX resources?

A server runs one framework. Resources that list both are built to detect which is running; they do not let you run the two side by side.