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
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.
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.
Sale
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.
- 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.
- ESX
- QBCore
- Qbox
Prodigy 2.0 Inventory System
ox_inventory rework for FiveM with metadata-driven item uniqueness, configurable rarity tiers, backpack system, and built-in crafting UI. ESX, QBCore & Qbox. Base script unencrypted.
- 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.
- 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.
- ESX
- QBCore
- Qbox
Vehicle Shops
QBCore dealership script with public showrooms — test drives, financing, license checks — and player-owned operations with stock ordering, employee commissions, and sell-back. Tested with ox_lib, oxmysql, and major banking/inventory resources.
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.