What players see
- a character selection scene with their real saved characters;
- locked/available character slots;
- character creation with server-side identity validation;
- the Appearance editor for a new character;
- a configurable spawn selector;
- optional Last Location behavior;
- the final handoff into normal RSG/VORP gameplay.
What Creator owns
Creator is responsible for:rco-appearance.
The important lifecycle rule
RCO does not invent a parallel framework lifecycle for every HUD, inventory or medical script to learn. On RSG, the normal player-loaded lifecycle is completed after the spawn transaction is actually ready. On VORP, Creator hands the character back through the expected VORP character/spawn lifecycle instead of trying to become a second core. Read Character lifecycle before changing a HUD or medical resource because of RCO.Server-authoritative identity and spawn
The UI is a client interface, not the authority. Character slot count, identity validation, spawn choice authorization and the final character/session transition are checked server-side. For example, the spawn UI sends a location ID; it does not get to tell the server arbitrary final coordinates as truth.In-game spawn management
After first setup, admins can use:Existing servers
Creator is designed to replace the stock RSG/VORP selector/spawn path cleanly. If you already have a third-party multicharacter with custom tables/events, treat the move as a migration project. Two character selectors should never be active for the same player.Where to go next
Installation
Clean start order and stock resources to disable.
Lifecycle
How RSG/VORP are handed a ready player.
Spawn locations
In-game spawn editor, Last Location and selector modes.
API
Open selection and query selection state from other resources.

