ESX Legacy Installation
The txAdmin recipe is the supported path. The manual route below is for adding ESX to a server that already exists.
Prerequisites
Do not use XAMPP. The ESX documentation says the same thing, for the same reason: it is not built for a production workload and has caused data loss on live servers. Install MariaDB directly.
Pick the install location carefully. Moving the folder later means updating
absolute paths in server.cfg and in txAdmin.
Method 1 — txAdmin recipe
Start FXServer
Run FXServer.exe on Windows or run.sh on Linux. txAdmin opens its setup wizard in a browser tab.
Link your Cfx.re account
Sign in with Cfx.re and set a backup password. If your antivirus flags FXServer.exe, verify that it came from the official artifact download before taking action; do not disable antivirus protection as a routine setup step.
Choose the deployment type
Select Popular Recipes, then ESX Legacy.
Set the resource path
Change the default to a dedicated folder rather than accepting the suggestion.
Enter database credentials
The deployer creates the schema and imports every SQL file the recipe needs.
Start the server
Once the recipe completes, start the server from the txAdmin dashboard.
Method 2 — manual installation
Clone the monorepo
Copy the core folder
Copy the [core] folder from the clone into your resources directory. Keep the square brackets — FXServer treats bracketed folders as resource groups, so ensure [core] starts everything inside.
Add oxmysql
Download the latest oxmysql release into your resources folder.
Import the SQL
Import [SQL]/legacy.sql from the repository into your es_extended database. It is the only file in that folder and creates the core tables (users, jobs, job_grades, items and the rest).
Configure server.cfg
set onesync on
set mysql_connection_string “mysql://user:password@localhost/es_extended?charset=utf8mb4”
ensure chat
ensure spawnmanager
ensure hardcap
add_ace resource.es_extended command.add_ace allow
add_ace resource.es_extended command.add_principal allow
add_ace resource.es_extended command.remove_principal allow
add_ace resource.es_extended command.stop allow
ensure oxmysql
ensure esx_lib
ensure es_extended
ensure [core]
The four add_ace resource.es_extended lines let es_extended manage ACE groups at runtime. This mirrors the reference server.cfg in esx_core; compare against it after each ESX update.
Verify OneSync compatibility and any build requirements against the installed ESX release and recipe before running production players. See OneSync.
Validation
To make yourself admin, set the group column on your row in the users table
to admin, then reconnect. Restrict access to database administration tools and prefer the supported in-game/framework permission workflow for the installed ESX version.
Rollback
- Stop FXServer
- Drop and recreate the database, then restore your last dump
- Restore the previous
resourcesfolder andserver.cfg - Confirm players can connect before attempting the install again
Keep the previous resources folder until the new install has survived a week of
normal load. See Backups.
Next steps
- ESX structure — the ESX object and xPlayer
- ESX resources — what ships and what to add
- Developing a script →