ESX Setup
Complete guide for setting up 0r-multicharacterv3 with ESX framework.
β
Requirements
ESX Legacy (1.9.0+) or ESX Infinity
ox_lib
oxmysql
A compatible inventory
A compatible clothing script (skinchanger or alternatives)
π Quick Setup
Step 1: Enable Multicharacter in ESX
Edit es_extended/config.lua:
Config.Multichar = true -- Enable multicharacter supportStep 2: Disable Default Multicharacter
# server.cfg
# ensure esx_multicharacter <-- Comment out or remove
ensure 0r-multicharacterv3Step 3: Start Order
ποΈ Database
ESX uses the users table for character storage:
identifier
Character identifier (char1:license, char2:license)
firstname
First name
lastname
Last name
dateofbirth
Birth date
sex
Gender (m/f)
job
Job name
job_grade
Job grade
accounts
Money accounts (JSON)
position
Last position (JSON)
skin
Appearance data (JSON)
π§ Character Identifier Format
ESX multicharacter uses a specific identifier format:
Examples:
char1:abc123def456- First characterchar2:abc123def456- Second characterchar3:abc123def456- Third character
Configure the prefix in config/config.lua:
π Data Conversion
The script converts ESX data to a standardized format:
β‘ Events
Server Events
Client Events
π Character Deletion & Reindexing
When a character is deleted, remaining characters are reindexed:
Configure tables in config/database.lua:
π Complete Configuration
π ESX vs QBCore Differences
Identifier
char1:license
citizenid
Gender
m/f
0/1
Money Storage
JSON accounts
JSON money
Skin Storage
users.skin
playerskins
Player Object
xPlayer
Player
β Troubleshooting
"Multichar not enabled" error
Ensure in es_extended/config.lua:
Skin not loading
Check
users.skincolumn has dataVerify skinchanger is started
Ensure skin format is correct
Character reindex issues
If characters are out of order after deletion:
Job not showing correctly
The script reads job labels from ESX's job system. Ensure jobs are properly configured in your database.
Last updated