- ESX
- QBCore
- Qbox
BLVCK HUD V2
BLVCK HUD V2 delivers three switchable HUD styles, server-synced nitro visible to all nearby players, cinematic mode, and an optional stress system for ESX, QBCore, and Qbox servers.
$5.00
Scripts That Run on a QBCore Build
Everything filed here names QBCore among the frameworks it supports. That is a starting point, not a guarantee: a resource can target qb-core and still expect a particular inventory, targeting system or database layout. Open the listing and read the requirements before you buy.
Scripts in this category
119 products
Sale
- ESX
- QBCore
- Qbox
Illenium Appearance Reskin (NoPixel Inspired)
NoPixel-inspired illenium-appearance reskin for FiveM. Replaces qb-clothing and esx_skin with rank-based wardrobes, tattoos, plastic surgery, and ox_lib UI. ESX, QBCore & Qbox.
$25.00
- ESX
- QBCore
- Qbox
Advanced Ankle Monitor Script
Let officers place real tracking devices on offenders — with a proper leg prop, configurable update intervals, lockpick removal, and 0.00ms idle. ESX, QBCore, and Qbox ready.
$10.00
- ESX
- QBCore
- Qbox
Advanced Multijob & Boss Menu
Samuel’s Advanced Multijob & Boss Menu supports unlimited concurrent jobs, polyzone duty enforcement, per-job leaderboards, 12 inventory integrations, and a full boss management suite for QBCore and QBox servers.
$20.00
Sale
- ESX
- QBCore
- Qbox
FREE MDT for Police
A fully free police MDT for FiveM with warrants, criminal records, vehicle database, auto nearest-player lookup, and five-language support. ESX, QBCore & Qbox. Rated 4.89/5.
FREE
New
Sale
- QBCore
- Qbox
QBCore Framework V4
QB Core V4 FiveM server on build 1.2.6 — crypto mining, gun dealer, black market, Cayo Island, PMA-voice, Discord webhooks, and a full civilian and criminal economy out of the box.
$100.00
Popular
Sale
- ESX
- QBCore
- Qbox
All in one Restaurant Script
Single QBCore resource covering 14 FiveM restaurant locations — Burgershot, Bean Machine, Cat Cafe, and eleven more — with unified menus, staff storage, customer kiosks, surveillance cameras, and consumable effects.
$15.00
$20.00
- ESX
- QBCore
- Qbox
FREE Keypad Minigame
Free, unencrypted FiveM keypad minigame with configurable PIN length, attempt limits, and per-attempt feedback. Works standalone or with ESX, QBCore, and Qbox. Zero cost, full source.
FREE
Sale
- ESX
- QBCore
- Qbox
ProdigyRP 2.0 Inspired Target | ox_target Redesign
ProdigyRP 2.0-inspired ox_target UI redesign for FiveM. Smooth eye animations, sprite icons, configurable colors and transparency. Drag-and-drop install, all frameworks supported.
$15.00
$30.00
- ESX
- QBCore
- Qbox
Mining Job V3
Free open source FiveM mining job for ESX, QBCore and Qbox — four-stage chain from raw rock to smelted ore to crafted jewelry, with tool durability, quests, coal delivery missions, and a live XP leaderboard.
FREE
- QBCore
- Qbox
Citation Script for Police Job
Turn police fines into real RP. This FiveM citation script creates physical inventory items documenting suspect details, charges, and fine amounts — with MDT integration and society account routing.
$15.00
What "QBCore compatible" tells you, and what it does not
A listing that names QBCore is telling you the resource speaks the framework's
player, job and money exports. It is not telling you which inventory it draws
into, which targeting resource it hooks, or which version of qb-core it was
built against. Those are separate answers and they live in the listing's own
requirements section.
Check these before you install
- The
qb-coreversion. A resource written against an older core can call - exports that were renamed or removed. The listing states what it was tested on.
- Inventory. Anything that gives, takes or displays an item has an inventory
- assumption baked in. Confirm it matches yours.
- Targeting. Interaction scripts hook a targeting resource. Swapping that out
- later is rarely a config change.
- Database. Scripts that persist state ship their own schema. Check whether it
- expects
oxmysqlor another wrapper. - Conflicting events. Two resources registering the same event name will fight.
- The listing usually names the events it owns.
Forks are their own question
A fork that renamed exports is a different target, however close it looks. If you
run one, treat QBCore support as a strong hint and verify against the fork's own
documentation rather than assuming a clean drop-in.
Where these sit in a build
Framework compatibility is a filter, not a shelf. Most resources here also appear
under ESX or Qbox because they
support more than one. If you are starting from nothing rather than adding to a
running server, the readymade builds are assembled
rather than assorted. For the map side of a build, see the
MLO interiors.
Frequently asked questions
Does QBCore compatibility mean it will work on my server?
It means the resource uses QBCore's framework exports. Your inventory, targeting resource, database wrapper and core version still have to line up. Each listing states what it was built and tested against; read that section before you buy.
Will these work on a QBCore fork?
Sometimes. A fork that kept the original export names usually works. One that renamed or removed them does not, and no framework label can tell you which you have. Check the resource's requirements against your fork's documentation.
Why do the same resources appear under ESX and Qbox as well?
Because many of them genuinely support more than one framework. The framework pages are filters over the same catalogue, not separate stock.
What if a script needs a dependency I do not run?
Treat the dependency as part of the price. Some are free and widely used, others are paid resources in their own right. The listing names them so you can check before checkout rather than after.
Are versions and update notes shown on the listing?
Where the resource publishes them, yes. The listing is the authoritative place for supported versions, required resources and what changed; this page only groups by framework.