Creator is easy to install once the ownership is clear: there must be one character selector and one spawn flow.
RCO Creator requires RCO Appearance.
1. Stop the stock resources Creator replaces
Appearance replaces the last three; Creator replaces multicharacter/spawn. vorp_core stays running. RCO integrates with it; RCO does not replace the core.2. Start resources in order
Creator will not start correctly before Appearance because new-character creation and character preview depend on the appearance engine.
3. Database
Creator creates its own tables automatically on a normal host. Appearance has separate persistence tables.
No manual SQL import should be required unless the database user is prevented from creating/updating schema.
4. First test
Do not start by testing only an existing character. Test the full path:
Then test a second character slot. Character switching is where duplicate lifecycle/old-resource conflicts usually become obvious.
5. Check framework handoff
After the final spawn:
- RSG HUD/inventory resources waiting for the normal loaded lifecycle should initialize once;
- VORP should complete its normal character/spawn initialization once;
- the player should not still be in the selection routing bucket;
- the saved appearance should already be applied.
See Character lifecycle if a gameplay resource starts too early or twice.
6. Spawn admin permission
Admins can manage spawn locations in-game with /rcospawns.
Explicit ACE example:
You can also customize the server-side permission function. Full guide: Spawn locations.
Already using a third-party multicharacter? Do not just add ensure rco-creator on production. First identify who currently owns login, character creation, deletion and spawn; then replace that flow deliberately.
