ESX Legacy Addons

ESX Legacy Addons is the official collection of optional resources that sit on top of es_extended: jobs, shops, vehicles, housing, HUD, chat and admin tools. Install the whole folder for a ready-to-play roleplay server, or pick single addons and respect their dependencies.

OverviewCopy Anchor Link

Every addon lists its hard dependencies in fxmanifest.lua. FiveM refuses to start a resource whose dependencies are missing, and prints Couldn't start resource ... dependency ... not found in the console.

All addonsCopy Anchor Link

Installing addonsCopy Anchor Link

ensure oxmysql
ensure esx_lib
ensure es_extended
ensure [core]

ensure [esx_addons]

ensure esx_addonaccount
ensure esx_addoninventory
ensure esx_datastore
ensure esx_society
ensure esx_billing
ensure esx_policejob

Dependencies between addonsCopy Anchor Link

The table combines the hard dependencies from fxmanifest.lua with soft dependencies found in the code (exports, events and callbacks into another addon). Soft dependencies do not block startup, but the related feature breaks without them.

The chain most servers hit is job → esx_society → esx_addonaccount / esx_datastore / esx_addoninventory. Every society needs a row in addon_account (money), and jobs with a stash also need rows in addon_inventory and datastore. If a job's boss menu shows no money or the armory is empty, those rows are usually missing.

Security hardening SQLCopy Anchor Link

The repository root contains two SQL files related to the October 2026 security audit.

security_indexes.sqlCopy Anchor Link

This file is superseded. It only contains comments and a SELECT that prints a note pointing to sql/security_hardening_2026_10_02.sql. Running it changes nothing. The comments also warn against blindly adding indexes such as (identifier, id) on billing or (owner, plate) on owned_vehicles, because InnoDB secondary indexes already include the primary key.

sql/security_hardening_2026_10_02.sqlCopy Anchor Link

This migration enforces data integrity for the economy tables that esx_billing, esx_license, esx_addonaccount and esx_banking rely on. It runs as a temporary stored procedure and is safe to run more than once. Each step is skipped when it is already applied.

It first refuses to run (raises an error) when it finds:

• duplicate user_licenses rows for the same owner and type
• duplicate addon_account_data rows for the same account and owner
• addon_account_data rows with a NULL account name or an empty-string owner
• billing, users or addon_account_data tables that are not InnoDB

Then it:

Finally, it lists billing_payments rows still in state claimed (payments that started but were never applied). Review them manually; the script never refunds or replays them.

Common issuesCopy Anchor Link

• Couldn't start resource esx_xxx: a hard dependency is missing or starts later. Check the dependency table above.
• Duplicate entry errors on SQL import: the rows already exist, usually from the txAdmin legacy.sql. Skip that import.
• Boss menu shows $0 or no society found: the society_<job> row is missing in addon_account / addon_account_data, or esx_society started before esx_addonaccount.
• Hardening script stops with "Duplicate ...": find the duplicates with a GROUP BY ... HAVING COUNT(*) > 1 query, merge balances by hand, then run it again.

RelatedCopy Anchor Link

• Installation
• server.cfg
• esx_society
• Create a job
• Database schema

Frequently asked questions