- ESX
- QBCore
- Qbox
FiveM Pepperspray Script
Adds a job-restricted pepper spray addon weapon to FiveM with configurable cone, range, paralysis duration, and gas mask immunity. ESX, QBCore, Qbox. Under 0.03ms at peak.
$15.00
Scripts That Run on ES Extended
Everything filed here names ESX among the frameworks it supports. ES Extended has moved a long way across its versions, so the useful question is not whether a resource is "ESX" but which ESX it was written against. The listing answers that.
Scripts in this category
110 products
- ESX
- QBCore
- Qbox
Bodybag Script
Close crime scenes properly with bodybag placement, configurable job or item gates, statebag sync that survives restarts, and 0.00ms overhead. ESX, QBCore, and Qbox supported.
$10.00
- ESX
- QBCore
- Qbox
Free Towing Job Script
Free FiveM towing job script with NPC missions, player-to-player requests, /towbilling to society accounts with optional commission splits, and server-side anti-exploit distance checks. QBCore, ESX, Qbox.
FREE
New
- 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
- ESX
- QBCore
- Qbox
Drug Manufacturing Jobs (Gang Integration)
Complete FiveM drug operation script for ESX, QBCore, and Qbox — upgradeable labs, burner phone dark web sourcing, multi-drug production, built-in money laundering, and 0.00ms server load.
$20.00
- 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
- ESX
- QBCore
- Qbox
FiveM Pet System
Dynamic pet system featuring leveling, breeding, and over 400 accessories
$15.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 is a moving target
es_extended has changed its API more than once. A resource built against a
legacy release can call functions that later versions deprecated, and a resource
built against a current release can assume helpers an older server does not have.
Neither shows up as an error until the resource starts.
Check these before you install
- The ESX version it was tested on. This is the single most useful line in an
- ESX listing. Legacy and current are not interchangeable.
- How it gets the player object. Older resources fetch it one way, newer ones
- another. A mismatch here is the most common cause of a resource loading and then
- doing nothing.
- Inventory. Item handling is not part of the framework contract. Confirm the
- resource expects the inventory you run.
- Database wrapper. Most resources assume
oxmysql. If you run something else, - check before buying.
- Society and job hooks. Anything with a boss menu, payroll or society account
- is touching code that varies between builds.
Reading a listing quickly
Requirements first, then supported versions, then the feature list. If the first
two do not match your server, the feature list does not matter. If they do, the
preview media is the fastest way to judge whether the implementation suits your
city.
Related shelves
Many of these resources also run on QBCore or
Qbox. For a server that does not exist yet, the
readymade builds arrive with the framework already
wired in. Map work is separate: see MLO interiors.
Frequently asked questions
Which ESX versions do these resources support?
It varies by resource, which is why each listing names the version it was built and tested against. ES Extended changed its API across releases, so a resource written for one may not run unmodified on another.
What is the difference between ESX Legacy and the newer releases here?
Mainly how a resource retrieves the player object and which helper functions exist. A resource written for one style can load without error on the other and still do nothing. The listing tells you which it targets.
Do I need a specific inventory?
Often, yes. Item handling sits outside the framework, so any resource that gives, takes or displays items carries an inventory assumption. The requirements section names it.
Can I run these alongside QBCore resources?
Not on the same server. A server runs one framework. Resources that support both are built to detect which is present; they do not bridge the two.
Is a resource that lists ESX, QBCore and Qbox worse at all three?
Not inherently. Multi-framework support is usually a compatibility layer around the same core logic. Judge it on its requirements and preview media as you would any other listing.