Fix ESX Multicharacter Problems
Diagnose ESX multicharacter not working, stuck character selection, blank NUI, failed relog and missing characters using current esx_multicharacter source.
When esx_multicharacter does not open, characters are missing or selection shows a black screen, inspect the client F8 console and server console first. The interface needs both its NUI frontend and database-backed character information.
1. Verify startup dependencies
The current esx_multicharacter/fxmanifest.lua declares es_extended, esx_context, esx_identity and esx_skin as dependencies. It also imports esx_lib; the core uses oxmysql for the database.
Ensure every resource exists with its fxmanifest.lua directly inside its folder. Check the server.cfg guide for correct startup.
2. Fix a blank screen or NUI timeout
The current client script waits for the nuiReady callback and reports NUI Failed to load after 10000ms if the interface fails to respond.
- Open F8 in game and find the earliest error.
- Confirm
esx_multicharacter/web/buildfiles were deployed. - Check the
ui_pagepath andfilesin the resource manifest. - Temporarily disable conflicting third-party character-selection, spawn and loading-screen scripts.
- Test with an unchanged official resource before editing its UI.
3. Characters not appearing
ESX multicharacter uses identifier prefixes such as char1:.... If you migrated databases, verify that the player identifiers and the users table still match.
- Check that
oxmysqlconnects to the intended database. - Verify existing identifiers without exposing them publicly.
- Compare backup records before changing any identifiers.
- Test a new player on a staging server to separate migration from startup issues.
See ESX database schema.
4. Config keys actually used
| Key | Current source behavior |
|---|---|
Config.Slots | Default 3 character slots |
Config.Prefix | Character identifier prefix, default char |
Config.Relog | Enables the /relog command |
Config.CanDelete | Controls character deletion |
Config.Spawn | Client-side selection scene location |
5. Relog failures
With Config.Relog = true, the client calls the esx_multicharacter:relog callback. F8 logs include [esx_multicharacter] Relog failed with a reason when it fails. Inspect the callback, conflicting scripts and the current player lifecycle before retrying.
Related
Frequently asked questions
Independent documentation
Last updated on
Fix ESX Is Nil / getSharedObject Errors
Fix ESX is nil, attempt to index a nil value and no such export getSharedObject in ESX Legacy, with verified imports.lua examples and resource load-order checks.
Tools for ESX Development
Useful tools for building and running an ESX Legacy server - VS Code extensions, database clients, txAdmin and community web tools for clothing, assets and merging.