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
- ESX
- QBCore
- Qbox
Pacific Bank Heist
A structured FiveM bank heist with laser puzzles, thermite, voice-acted NPCs, weapon-tier loot control, and police integration. ESX, QBCore & Qbox. Event injection protected.
$10.00
New
- ESX
- QBCore
- Qbox
Advanced Wheel Boot
A multiplayer-synchronised FiveM wheel boot script with real steering restriction, optional wheel-damage physics, lockpick removal, and 0.00ms idle. ESX, QBCore, and Qbox compatible.
$12.99
- ESX
- QBCore
- Qbox
Brake Overheating
Realistic brake heat mechanics for FiveM — temperature-based brake fade, synchronized caliper glow, and brake upgrade integration. Standalone compatible, 0.00ms idle, works on all vehicles including mods.
$9.00
New
- ESX
- QBCore
- Qbox
Smash N Grab 2.0
FiveM car looting script letting players raid NPC vehicles with seat-based loot placement, configurable odds by vehicle class, minigame break-ins, NPC reactions, and police dispatch — no entity limit impact.
$9.99
Sale
- QBCore
- Qbox
QBCore Framework V3
Premade QBCore V3 FiveM server with custom EUP, Cayo Island, PMA-voice, MDT, advanced drug processing, and full civilian and criminal job coverage — immersion-ready on install.
$80.00
![Latest QBCore Framework V7 [NoPixel 4.0 Inspired]](/uploads/card/29d450513a2b02f57f656184ccb3ed97.webp)
Sale
New
- ESX
- QBCore
- Qbox
DRC Advanced Bahama Mamas Job — Marc MLO Bar Job for QBCore & ESX
Advanced Bahama Mamas bar job for FiveM — duty system, drink crafting with animations, boss menu, dance platforms, and 3000+ lines of open-source code. Runs on ESX and QBCore with Marc or XnBahamaMamas MLO.
$10.00
- QBCore
- Qbox
QBCore Framework V8
A current-gen QBCore V8 FiveM server package — 400+ vehicles, 50+ police cars, civilian and criminal activity systems, TOS-compliant assets, and verified stable at 50+ concurrent players.
$110.00
- ESX
- QBCore
- Qbox
Animal Control Job
Six-step FiveM animal control job for ESX, QBCore, and Qbox — bait placement, habitat-specific spawns, server-side anti-cheat, anti-grief job cancellation, and configurable per-animal payouts at 0.02ms resmon.
$10.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.