Only one character selector can run at a time. Disable your framework’s
default multichar before starting this resource.
The resource folder must be named exactly awoken_multicharacter (underscore) for both
QBX/QBCore and ESX. It will refuse to start if the name doesn’t match.
Prerequisites
qbx_core or qb-coreox_liboxmysql- An appearance resource:
illenium-appearance, fivem-appearance, or ox_appearance
- A spawn selector:
qbx_spawn, qb-spawn, or um-spawn (optional - none spawns at last position)
es_extended (ESX Legacy)ox_liboxmysql- An appearance resource:
illenium-appearance, fivem-appearance, ox_appearance, or the traditional esx_skin + skinchanger stack
Steps
Disable the default selector
Comment out your framework’s built-in multichar in server.cfg and add the new resource:For QBX, open qbx_core/config/client.lua and set: Set the framework
Open config.lua. The default is 'auto', which detects qbx_core first then falls back to qb-core. You can set it explicitly if needed: Set your appearance resource
See the Configuration page for supported values and the full option list. Start the server
Boot up. On start the resource prints a banner and the detected framework:Framework: qb means it fell back to qb-core. If it shows Unknown or defaults to qbx
unexpectedly, make sure your framework resource starts before awoken_multicharacter.
Set Config.Debug = true for verbose startup logging (DB setup, slot lookups, etc.). Disable esx_multicharacter
Comment it out in server.cfg and add the new resource:awoken_multicharacter must start after es_extended and oxmysql. Enable multichar in ESX
Open es_extended/config.lua and set:Without this ESX spawns the player straight into the world and skips the selector. Set the framework
Open config.lua and set the framework to 'esx', or leave it as 'auto' (auto detects qbx_core first, then qb-core, then es_extended): Set your appearance resource
Supported values: 'illenium-appearance', 'fivem-appearance', 'ox_appearance', 'sn_appearance'. Leave it as any other value (or empty) to use the traditional skinchanger + esx_skin stack.See Configuration for the clothing editor behaviour per resource. Start the server
Boot up and confirm the console shows the framework was detected as ESX:On first start the resource sets up its schema - it adds a multichar_scenario column to
users and creates a multichar_players table. Both operations are safe and only run if
the column or table doesn’t already exist. Set Config.Debug = true to log these steps.
Verify it’s working
Connect to your server. You should hit the character selector rather than spawning directly into
the world. The console logs character slot counts and Discord role cache status on each connection.
If you’re still spawning into the world, the two most common causes are:
- The old multichar resource is still running. Check every
.cfg file, not just server.cfg - a resource ensured in a category file will still load even if you commented it out in the main config.
qbx_core’s built-in multichar flag wasn’t set to false.
Config.Multichar = true is not set in es_extended/config.lua.esx_multicharacter is commented out in one cfg file but still ensured in another (category files, etc.).
