Framework and debug
auto unless startup reports an ambiguity.
Character slots
MaxCharacters is the hard ceiling. Discord/manual/custom slot resolvers can change how many slots a player gets, but never beyond that cap.
Full priority rules are documented in Character slots.
Logout / return to selection
Builds that expose the logout command use the Creator selection flow rather than disconnecting the player. Treat logout as a character lifecycle operation, not just a UI reopen: pending spawn/apply work from the old character must not continue into the next one. If your framework/build intentionally disables the command, use its supported return-to-selection integration instead of forcing a client UI open.Identity rules
Typical options include:Nationalities
Use the configured nationality list when you want a controlled set of values instead of arbitrary text. Keep the list readable for players — this is character creation, not a database enum screen.Selection scene
Config.Selection controls selection presentation/behavior, including how locked slots are shown. Scene coordinates should be treated as a complete setup (ped placement, camera and staging), not random independent numbers.
If you move the scene, test every slot with both male/female saved appearances and at high FPS before shipping it.
Spawn selector
A typical spawn section controls:- selector mode;
- Last Location availability;
- fallback spawn;
- the initial seed list of locations.
/rcospawns for normal live management.
See Spawn locations.
Starter package
Server-only example:Force Last Location for special states
Server-side logic can bypass the normal spawn choice for characters that must return to a specific persisted context, such as jail.Discord / custom slots
CreatorServerConfig.Discord, PlayerSlots and ResolveCustomSlots are covered in Character slots and Discord setup.
Spawn editor permission
CanManageSpawns decides who may use /rcospawns. This is separate from normal character permissions and should stay server-authoritative.
