Troubleshooting and support
Start with the console line printed a few seconds after start:
[lumo-multicharacter] ready — framework: qb- Missing → the resource is not starting; look for an error just above.
- Wrong framework → your core starts after this resource (the console names it in a warning), or force it with
Frameworkinbridge/config.lua.
Common symptoms
| Symptom | Fix |
|---|---|
| Selector never appears; you load straight in | The old selection still runs. QBCore: stop qb-multicharacter. Qbox: useExternalCharacters = true in qbx_core/config/client.lua. ESX: Config.Multichar = true in es_extended/shared/config/main.lua (older: es_extended/config.lua) and don't start esx_multicharacter. Deleting the esx_multicharacter folder turns current ESX's default multichar off. |
framework: standalone on a framework server | Ensure qb-core / qbx_core / es_extended before this resource. |
framework: qb on Qbox | Set Framework = 'qbx' in bridge/config.lua. |
| Stuck in the room after picking a character | Your spawn script has a custom name: add it to Config.SpawnResources. Or remove it and let Config.LastLocationFallback place the player. |
| Blank interface | html/dist/ must be inside the folder. Check F8 for NUI errors. |
| Character list empty but characters exist | Look for a database error in the server console; check oxmysql connects to the right database. |
| New characters have no clothing menu | No appearance script started (lumo-clothing, illenium-appearance, fivem-appearance, qb-clothing, esx_skin). |
| Female characters preview as male | A character created with very old builds may have male appearance saved. Recreate it. |
| Starter items never arrive | Item names in bridge/config.lua (Qbox/ESX/standalone) or QBCore.Shared.StarterItems must exist in your inventory. |
/logout says no permission (standalone) | add_principal identifier.license:… group.admin in server.cfg. |
| Two creators open on Qbox | qbx_properties handles new characters; keep it in StartingApartmentResources in bridge/config.lua. |
Reporting a problem
Send through the store's Discord:
- Product, version and edition (escrow / open source)
- Framework and its version, FiveM artifact number
- The
ready — framework:console line - Steps to reproduce, what you expected, what happened
- Server console and F8 output around the problem
Never send database passwords, licence keys or full database dumps.