Sale
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
Sale
Sale
![Latest QBCore Framework V7 [NoPixel 4.0 Inspired]](/uploads/card/29d450513a2b02f57f656184ccb3ed97.webp)
Sale
Sale
- QBCore
- Qbox
FiveM Lore Friendly Cars Pack 300+ Vehicles
310+ FiveM vehicles organised by GTA fictional manufacturers — Vapid, Declasse, Grotti, Karin and more. Includes police packages, emergency variants, and utility vehicles. Compatible with QBCore, Qbox, ESX, and any framework.
$189.00
$750.00
- ESX
- QBCore
- Qbox
Holographic & Audible Notifications
ElevenLabs-powered TTS notification script for FiveM — fire voiced, holographic alerts from any resource via a single export. Smart caching, 30+ languages. ESX, QBCore, Qbox compatible.
$5.99
Sale
- ESX
- QBCore
- Qbox
FREE Snake Cam / Under Door Camera
Free FiveM snake cam gives officers a live under-door feed before breaching. Auto door detection, configurable angles, item-gateable, 0.02ms active. ESX, QBCore & Qbox.
FREE
- ESX
- QBCore
- Qbox
FREE Drone Script for FiveM
Free, open-source FiveM drone script with full controller support, Fivemanage aerial screenshots, night vision, configurable HUD, and signal-loss mechanics. ESX, QBCore & Qbox ready.
FREE
New
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
- 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
- ESX
- QBCore
- Qbox
Custom Shops Pro
Custom Shops Pro is a full player-owned shop system for FiveM with loyalty tiers, coupon campaigns, pawn and dirty money support, 55+ staff permissions, and deep analytics across ESX, QBCore, and QBox.
FREE
- ESX
- QBCore
- Qbox
Lusty Pawn Shop - The Ultimate Buy & Sell System
FiveM pawn shop script with dirty money payout routing, unlimited map locations, player-owned shop support, and anti-exploit event guards. QBCore, ESX, Qbox — configurable buy-sell economy in one resource.
$10.00
- ESX
- QBCore
- Qbox
Vehicle Selling and Auction System
Player-to-player FiveM vehicle marketplace with fixed-price listings and timed auctions, real-time bidding, full mod spec preservation, dynamic lot entity management, and server-side validation. ESX, QBCore, Qbox.
$11.99
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.