ESX Scripts

ESX Legacy specifics these scripts rely on

Every resource here was tagged ESX by its creator, and many carry a [QB/ESX] prefix, which means one download with a framework line in the config. The rest, including Custom Shops Pro, the Watch Dogs style Vehicle Hacking script and the CodeM mStaff admin menu, are built on ESX Legacy’s xPlayer object and the es_extended export. Three install details separate a clean ESX setup from an evening of console errors.

The SQL file touches your core tables

Unlike QBCore, ESX keeps jobs, job grades and (without ox_inventory) items in the database. A job script’s .sql file therefore inserts into jobs and job_grades, sometimes into items, and business scripts such as Player-Owned Businesses or the DRC Hornys Job add addon_account_data rows for society money. Read the file before you import it. A stray DROP TABLE or a duplicate job name will overwrite data you already configured.

Old shared-object calls

Newer ESX Legacy builds expect exports[‘es_extended’]:getSharedObject() instead of the old esx:getSharedObject event. A script that still relies on the event can load, print nothing useful, then fail on the first ESX call. The listings here are maintained, but if you are reinstalling an older build from your downloads, that one-line swap at the top of the client and server files fixes most “ESX is nil” reports.

Inventory and menu choices

ESX servers split between the stock inventory with esx_menu_default and the ox stack with ox_inventory plus ox_lib menus. Crafting (ESX/qb-crafting v2), vehicle shops and the Pets by RAINMAD script each name which one they target, and dual-inventory scripts expose it as a config string. Pick the line that matches your server before you touch anything else. ESX cities share the interiors and all of the free scripts in the store, and the jobs shelf states ESX support on each listing.