ESX Scripts
ESX scripts, in short
ESX scripts are FiveM server resources written for ESX, the longest-running GTA V roleplay framework; ESX Legacy is its maintained line and its core resource is es_extended. They identify players by an identifier string rather than a citizen ID, and move money through named accounts — money, bank, and black_money — instead of a single wallet field. Vice Drip resources reach ESX Legacy through one open bridge module (vf_core), so nothing we ship calls es_extended directly.
This hub carries the ESX-specific parts: the accounts model, the identity shape, the society-account seam, and what a move off ESX actually costs. The catalog is the same catalog everywhere on this site — what changes per framework is how it reaches you and which assumptions it has to normalise.
What an ESX install assumes.
The accounts model is the thing that differs most
ESX does not keep one wallet field. Money lives in named accounts — money, bank, and black_money — and a resource moves value by naming the account it is touching. Anything written for a single money table has to decide which ESX account a given movement belongs to, and that decision is a design choice, not a rename. Our bridge normalizes this at one seam so a resource never has to encode an account name in business logic.
Identity is an identifier string, not a citizen ID
ESX resolves players through es_extended by an identifier string, commonly the license identifier, rather than through a generated citizen ID. Any resource that stores rows keyed on identity inherits that shape, which is why cross-framework data moves are database projects rather than config changes. ForgeCore exposes one normalized identity surface, so our schemas do not hard-code either convention.
Society accounts and job grades are their own seam
Shared job money on ESX has traditionally lived in society accounts handled by an add-on rather than in the core, and job grades carry their own shape. Any resource that pays a business, an agency, or a department is touching that seam. We treat society-style balances as a named bridge concern rather than assuming your server runs a particular add-on, and the bridge glue ships open so you can read the assumption before you rely on it.
ESX Legacy is the target — older forks are not
ESX has a long history and a lot of servers still run older forks with different conventions. Our support statement is deliberately specific: ESX Legacy, the maintained line, reached through a bridge adapter inside ForgeCore (vf_core). ForgeCore is free and 100% unescrowed, so the adapter is auditable before you install anything paid. The tested version matrix publishes with each release; no release has shipped yet.
What each direction costs.
We ship a bridge for all three frameworks, so we gain nothing from talking you into a move. These are the shapes of the work, not a recommendation. Longer form in the framework lock-in guide.
Staying on ESX Legacy
The largest accumulated resource library in this market targets ESX, which is a real advantage and also the trap: every resource that calls es_extended directly makes your framework choice a little more permanent. Audit how many of the ones you already run do that before adding more.
ESX → QBCore or Qbox
This is the expensive direction, and it is not a rename. Identity moves from an identifier string to a citizen ID; money moves from named accounts to a single money table with cash, bank and crypto fields; job-grade shapes differ. Every table keyed on the old model needs a reconciliation plan. Price the database work first — it usually dwarfs the cost of the resources.
Running ESX and QBCore-lineage servers side by side
Some operators run more than one city. The reason we ship one bridge rather than three builds is exactly this: the same resource, the same config surface and the same schema, with the framework resolved at start-up rather than at purchase.
What a bridge actually buys you
It does not make migration free — your other resources still have to move. It removes ours from the blast radius: they talk to ForgeCore, ForgeCore talks to whichever framework is running, so a framework change is a config problem for our stack instead of a rewrite.
Every resource, reached through the ESX Legacy bridge.
Statuses come straight from the product truth model. Prices marked Planned are targets pending the studio's pricing lock — not offers. Nothing below has a checkout path, and no entry carries a measured performance figure.
| Resource | Status | ESX path | Price |
|---|---|---|---|
| ForgeCorevf_core | Free · Open | is the bridge | FREE |
| CityPulsevf_announce | Free · Open | vf_core · ESX Legacy bridge | FREE |
| MoneyTrailvf_banking | In build · proof-pending | vf_core · ESX Legacy bridge | Planned · $39.99 |
| ShiftWorksvf_jobs | In build · proof-pending | vf_core · ESX Legacy bridge | Planned · $24.99 |
| TitleLock Garagevf_garage | In build · proof-pending | vf_core · ESX Legacy bridge | Planned · $24.99 |
| Heatlinevf_drugs | In build · proof-pending | vf_core · ESX Legacy bridge | Planned · $34.99 |
| ClosingTablevf_realty | In development | vf_core · ESX Legacy bridge | Planned · $39.99 |
| CleanTitle Housingvf_housing | In development | vf_core · ESX Legacy bridge | Planned · $39.99–44.99 |
| MainStreetvf_business | In development | vf_core · ESX Legacy bridge | Planned · $39.99 |
| Watchtower Adminvf_admin | In development | vf_core · ESX Legacy bridge | Planned · $39.99 |
| TurfLedgervf_gangs | In development | vf_core · ESX Legacy bridge | Planned · $27.99 |
| CaseLink MDTvf_mdt | In development | vf_core · ESX Legacy bridge | Planned · $44.99 |
| ChainLock Evidencevf_evidence | In development | vf_core · ESX Legacy bridge | Planned · $29.99 |
| LifeLine EMSvf_ems | In development | vf_core · ESX Legacy bridge | Planned · $29.99 |
| K9 Tracevf_k9 | In development | vf_core · ESX Legacy bridge | Planned · $19.99–24.99 |
| SkyWatch Reconvf_drones | In development | vf_core · ESX Legacy bridge | Planned · $34.99 |
| SkyForge Showspyrotech | In development | vf_core · ESX Legacy bridge | Planned · $29.99–34.99 |
| Sidekick Litevf_companion | In development | vf_core · ESX Legacy bridge | [price-pending] |
| Veilbreakers: Daemon Protocolvf_daemon | In development · not for sale | vf_core · ESX Legacy bridge | Planned · $39.99 |
Resources on internal hold have no public page, price or listing and do not appear here. Full descriptions live on the FiveM scripts hub.
Eight criteria for an ESX script.
No vendor scores. We do not run other sellers' code, so rating them would be invented precision dressed as research. The criteria are what transfer between servers; a score never would.
| Criterion | Why it matters on ESX | How to test it |
|---|---|---|
| Server authority | ESX's account model makes money movement explicit, which helps nothing if the client is the thing deciding that a movement happened. | Ask which side validates the mutation, and whether every net event checks source, permission, rate limit and argument types. |
| Framework support | "ESX supported" can mean ESX Legacy or an older fork with different conventions. The two are not interchangeable and the store page rarely says which. | Ask specifically whether ESX Legacy is the tested target, and for the tested framework and artifact versions per release. |
| Escrow split | If the account-handling layer is escrowed, you cannot inspect which ESX account a resource debits — on a money system, that is the one thing you most want to read. | Ask for a file-level manifest, and specifically whether the framework bridge and money seam ship open. |
| Dependencies | ESX resources often assume add-ons for societies, inventory, or menus. An undeclared assumption is a first-boot failure with a confusing error. | Read fxmanifest.lua for declared dependencies, then grep for exports of add-ons you do not run. |
| Data portability | Rows keyed on an identifier string are the single biggest cost in any later framework move. Whether you can read them decides whether that move is possible at all. | Ask for the schema and confirm the tables are readable with plain SQL rather than only through escrowed code. |
| Runtime proof | A resmon screenshot is not reproducible. Without method, client spec, player count and date, a performance figure is a marketing number. | Ask what was measured, on what hardware, at what player count, on what date. |
| Support SLA | Long-lived ESX servers carry years of accumulated configuration, so integration questions are the norm rather than the exception. | Ask for first-response and hotfix windows in hours, and what counts as a severity-1. |
| Changelog | ESX's age means abandoned resources look identical to maintained ones until the day they break. | Look for dated entries and a version string you can compare against the copy you installed. |
Our own answers to all eight, including the unproven rows, are in the Proof Center.
What to verify before buying.
Cfx.re's own platform documentation is the neutral source for how FiveM resources, manifests, dependencies and asset escrow work, and it is where the platform's guidance on installing third-party and paid community resources lives — research what a resource depends on, and take care with paid community assets. Check any seller's claim, ours included, against docs.fivem.net rather than against a store page.
- 01
Read fxmanifest.lua before you install: declared dependencies, the lua54 flag, and which files the manifest lists as escrowed.
- 02
Ask whether the target is ESX Legacy specifically, and which framework and artifact versions were tested for the release you are buying.
- 03
Ask which ESX account a resource debits and credits for each money movement, and whether that logic ships open.
- 04
Ask how any performance figure was measured: method, hardware, player count, date. No method means no measurement.
- 05
Ask what happens to your identifier-keyed rows if you uninstall, and whether the schema is documented.
- 06
Ask for the support window in hours, then check the changelog's most recent dated entry against it.
- 07
Read the license terms: modification rights, multi-server use, and what happens on a refund.
- 08
Cross-check every technical claim — ours included — against the platform documentation rather than a store page.
ESX, answered honestly.
Do Vice Drip scripts work with ESX Legacy?
They are built to reach ESX Legacy through a bridge adapter inside ForgeCore (vf_core), our free, fully unescrowed bridge module — no resource calls es_extended directly. ESX Legacy is the stated target; older ESX forks are not, because their conventions differ enough that claiming support would be a guess. The tested framework and artifact version matrix publishes with each release, and no runtime proof is published across the catalog.
How does the bridge handle ESX accounts — money, bank and black_money?
By making the account an explicit part of one normalized money seam rather than something scattered through business logic. A resource asks the bridge to move value; the bridge decides which ESX account that maps to. That is deliberate: on a framework where money lives in named accounts, the mapping is the part a server owner most needs to be able to read, and the bridge glue ships open so it can be read. Whether the underlying ledger behaves under live load is a runtime question, and that remains unproven.
What about society accounts and job grades?
Shared job money on ESX has historically lived in society accounts handled by an add-on rather than in the core. We treat that as a named seam in the bridge instead of assuming your server runs a particular add-on, and job grades are read through the same normalized job surface every framework adapter exposes. Because ForgeCore is unescrowed, you can confirm what it expects from your install before committing to anything paid.
I run ESX and I am considering QBCore or Qbox. How big is that move?
Bigger than it looks, and the cost is in the database rather than the resource list. Identity moves from an identifier string to a citizen ID and money moves from named accounts to a single money table, so every table keyed on the old model needs reconciliation. We ship for all three and will not push a direction; the question worth answering first is how many of your current resources bind directly to es_extended, because those are what actually make the move expensive.
Can I buy an ESX script from Vice Drip today?
No. Nothing in the catalog is cleared to sell — there is no Buy button and no checkout path anywhere on this site. ForgeCore and CityPulse are free and 100% unescrowed; every other entry shows a build status and a planned price that is a target, not a commitment, pending the studio's pricing lock. Verified 2026-09-02.
Status honesty: no runtime proof is published across the portfolio — nothing here has completed its core loop on a live FiveM server, on ESX Legacy or on any other framework, and no resmon figure has been measured. Tested framework and artifact versions publish with each release. Nothing on this page is on sale: no Buy button, no checkout, no purchase path. Planned prices are targets pending the studio pricing lock. No reviews, ratings, install counts or revenue figures are published, and no next-generation Rockstar-title compatibility is claimed.
Last verified: 2026-07-23