QBCore Scripts, Tested on Live Servers

Browse packages listed with QBCore support. Each product names its supported frameworks and dependencies; ESX and Qbox support are available only where the listing explicitly includes them.

QBCore Scripts, Tested on Live Servers - QBCore Scripts

Scripts in this category

41 products
QBCore Mechanic & Customs Job V2.5
QBCOREQBOX
$20.00
Vehicle Hacking Script for FiveM
New
ESXQBCOREQBOX
$15.00
Police Dispatch, Map & Radio for FiveM
ESXQBCOREQBOX
$20.00
Self-Driving Autopilot Script for FiveM
ESXQBCOREQBOX
$8.00
In-Game Help & Ticket System for FiveM
ESXQBCOREQBOX
$10.00
Body Investigation Tools for FiveM
ESXQBCOREQBOX
$9.00
Gang Territory & Turf Wars for FiveM
New
ESXQBCOREQBOX
$15.00
Vehicle Auction & Sales for FiveM
New
ESXQBCOREQBOX
$11.99
Police Shield Script for FiveM
ESXQBCOREQBOX
$9.00
Tracker Dart Script for Police RP
ESXQBCOREQBOX
$9.00
Player-Owned Market Script for FiveM
Bestseller
ESXQBCOREQBOX
$10.00
Graffiti & Tagging Script for FiveM
New
ESXQBCOREQBOX
$15.00
QBCore & Qbox Casino Script Suite
New
QBCOREQBOX
$20.00
Advanced Mechanic Script with Dyno & Stance
ESXQBCOREQBOX
$30.00
Drift Tyres & Car Lift for FiveM
ESXQBCOREQBOX
$20.00
Advanced HUD V7 with 4 Speedometer Styles
Bestseller
ESXQBCOREQBOX
FREE
Minigame Bundle: Lockpick, Hotwire & More
ESXQBCOREQBOX
$10.00

The framework most servers start on

QBCore is where most FiveM cities begin, because it arrives with the pieces a roleplay server needs already wired together — jobs, inventory, phone, bank. The trade-off is that a fresh QBCore install is recognisable on sight. Players who have been around a few cities can name your framework from the spawn screen.

What changes that is not more scripts, it is the right ones. A garage that handles impounds and job vehicles properly. A dealership players run themselves. A mechanic job with real work orders rather than a menu. Each one replaces a stock behaviour with something your regulars have to learn, and learning it is what makes a city feel like somewhere instead of a template.

Written for qb-core, not a fork of it

The resources here target current QBCore and use the framework's own exports and events rather than patching core files. That is the difference between an update you apply in a minute and an update that costs you an evening.

Most also carry ESX and Qbox support in the same package, so a framework change later does not mean repurchasing the shelf.

Fitting them to your city

Job names, item names, prices, keybinds and permissions are all config, so a resource can be pointed at the jobs your server already runs. Where something needs an inventory or a target system, it works with the ones QBCore servers actually use rather than insisting on one.