esx_identity
One resource instead of three
The entry flow into a roleplay server is usually split across three resources: the character selector, the identity form and the spawn selector. That is three dependencies, three different interface styles and three places where something can break.
Cube Multicharacter brings all three together. The character selector ships list, stats, create and delete, with a cinematic camera that hides the player and the HUD while it moves. Then comes the spawn selector, where you pick a point on the map or return to where you left off. And the identity form lives inside, which is why esx_identity and qb-identity stop being necessary.
What else it solves
The spawn points you declare in config appear on their own as cards and as map blips. Character deletion is a soft delete and also cleans up the framework data. And there is a command to adjust the slots of a specific player.
It runs on ESX, QBCore, Qbox and standalone with autodetection and manual override. The one requirement it does have, and it is worth knowing up front: OneSync Infinity.
Frequently asked questions
Do I have to uninstall esx_identity?
You do not need to use it, because the identity form is inside Cube Multicharacter. If you keep it active for other reasons, check that you are not left with two character creation flows competing.
What are Cube Multicharacter's requirements?
OneSync Infinity. The framework is autodetected between ESX, QBCore, Qbox and standalone, and can be forced manually.