Installation

Install RCO Creator without leaving a second selector or spawn system running.

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

RSG Core

# ensure rsg-multicharacter
# ensure rsg-spawn
# ensure rsg-appearance
# ensure rsg-wardrobe
# ensure rsg-barbers

Appearance replaces the last three; Creator replaces multicharacter/spawn.

VORP Core

# ensure vorp_character
# ensure vorp_barbershop
# ensure vorp_clothingstore

vorp_core stays running. RCO integrates with it; RCO does not replace the core.

2. Start resources in order

RSG Core

ensure oxmysql
ensure rsg-core
ensure rco-appearance
ensure rco-creator

VORP Core

ensure oxmysql
ensure vorp_core
ensure rco-appearance
ensure rco-creator

Creator will not start correctly before Appearance because new-character creation and character preview depend on the appearance engine.

3. Keep Creator and Appearance on the same release

RCO Identity is shipped as one package. Update both resources together.

Creator checks the local manifest versions of:

rco-creator
rco-appearance

If they do not match, the server console warns that the package is mixed.

Example:

[RCO Identity] Resource version mismatch: rco-creator v1.7.1 / rco-appearance v1.7.0. Update the complete RCO Identity package.

Do not fix this warning by editing only the version text in fxmanifest.lua. Install the matching resource files from the same release package.

4. Automatic version check

When Creator starts, it performs one lightweight server-side request to RCO’s public release metadata and compares the installed package with the current public release.

Normal result:

[RCO Identity] RCO Identity is up to date (v1.7.1).

When an update exists:

[RCO Identity] RCO Identity update available: v1.7.1 -> v1.7.2. Download the complete latest package.

The check is informational only:

• no player identifiers or character data are sent;
• there is no per-player request;
• there is no permanent polling loop;
• if GitHub/release metadata is unavailable, RCO continues starting normally.

Only rco-creator performs the remote version request because Creator + Appearance are released together. Appearance does not perform a second duplicate request.

5. 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.

6. First test

Do not start by testing only an existing character. Test the full path:

connect
→ selection
→ create character
→ appearance
→ choose spawn
→ enter world
→ relog
→ select the same character

Then test a second character slot. Character switching is where duplicate lifecycle/old-resource conflicts usually become obvious.

7. 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.

8. Spawn admin permission

Admins can manage spawn locations in-game with /rcospawns.

Explicit ACE example:

add_ace group.admin rco.creator.spawns allow

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.