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 That Run on ES Extended - ESX Scripts

Scripts in this category

110 products
FiveM Scuba Diving Script | Advanced Underwater RP Sale
  • ESX
  • QBCore
  • Qbox

Advanced Scuba Diving V3

Advanced Scuba Diving V3 builds a full underwater economy: boat rental, oxygen-tracked dive tanks, shipwreck loot, skill-based crate minigames, and a quest system with XP leaderboard. ESX, QBCore, Qbox — one purchase.

$9.00 $10.00
FiveM Slaughterhouse Job Script – ESX, QBCore & Qbox Sale
  • ESX
  • QBCore
  • Qbox

Realistic Slaughtering Job /w Animations

FiveM slaughterhouse job with a full catch-to-grind processing chain, XP-gated success rates, dynamic market pricing, and dual delivery options for ESX, QBCore and Qbox servers.

$15.00 $30.00
Free FiveM Dodgeball Script | 1v1 to 5v5 Minigame
  • ESX
  • QBCore
  • Qbox

FREE FiveM Dodgeball Game

Free standalone FiveM dodgeball script with 1v1 to 5v5 match formats and a Vespucci Beach court included. No framework dependency — compatible with ESX, QBCore, Qbox, and Gamzky Scripts.

FREE
FiveM Police Vehicle Trunk - Interactive Storage Popular
  • ESX
  • QBCore
  • Qbox

Police Vehicle Trunk

Give FiveM officers a proper equipment trunk — visual prop layout, per-vehicle item config, clothing slots, job-gated access, and 0.03ms active usage. ESX, QBCore & Qbox.

$10.00
FiveM Gun Menu Script – CS2-Style Weapon Shop
  • ESX
  • QBCore
  • Qbox

GFX GunMenu for FiveM

CS2-style FiveM gun menu with configurable colors, stock, and pricing. Delivers weapons to inventory or hand. Minimal setup. ESX, QBCore, Qbox and standalone compatible.

$10.00
FiveM Outfit Items Script – Job Uniform Shop QBCore
  • ESX
  • QBCore
  • Qbox

Outfit Items

FiveM outfit items script with job and grade-based access, live character previews, and wearable inventory items that apply full uniforms instantly. QBCore, ox_inventory, ox_target ready.

$6.00
FiveM Electrician Job Script – 0.00ms, ESX & QBCore
  • ESX
  • QBCore
  • Qbox

FiveM Electrician Job

FiveM electrician job with a 4×4 circuit-board puzzle, randomized fusebox dispatch, auto-detecting ESX and QBCore support, and a verified 0.00ms active resmon — white-collar civilian work at £5.99.

$5.99
FiveM Pay and Spray | Multi-Location Vehicle Shop
  • ESX
  • QBCore
  • Qbox

Pay And Spray

Per-location Pay and Spray script for FiveM with individual pricing, job locking, livery preview, chameleon paint, and vehicle repairs. Runs on ESX, QBCore, and Qbox with broad inventory, banking, and fuel compatibility.

$6.00
FiveM Vehicle Respray RGB Script — JG Mechanic 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
BLVCK HUD V2 — FiveM HUD With Synced Nitro System
  • ESX
  • QBCore
  • Qbox

BLVCK HUD V2

BLVCK HUD V2 delivers three switchable HUD styles, server-synced nitro visible to all nearby players, cinematic mode, and an optional stress system for ESX, QBCore, and Qbox servers.

$5.00
Illenium Appearance Reskin - NoPixel Clothing
  • ESX
  • QBCore
  • Qbox

Illenium Appearance Reskin (NoPixel Inspired)

NoPixel-inspired illenium-appearance reskin for FiveM. Replaces qb-clothing and esx_skin with rank-based wardrobes, tattoos, plastic surgery, and ox_lib UI. ESX, QBCore & Qbox.

$25.00

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.