> ## Documentation Index
> Fetch the complete documentation index at: https://rust-co.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Character selection, identity, slots and world spawn for RCO Identity.

RCO Creator is the part of RCO Identity that owns the journey from **"I connected"** to **"my character is in the world."**

It replaces the stock multicharacter/selection and spawn flow, while your framework continues to own the rest of the character: jobs, money, inventory, permissions and normal gameplay systems.

## 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:

```text theme={"dark"}
select character
create/delete character
identity fields
character-slot rules
selection scene isolation
spawn choice
spawn transaction
framework handoff
```

Appearance is responsible for the actual face/body/clothing snapshot.

That separation is why Creator requires `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](/rco-creator/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:

```text theme={"dark"}
/rcospawns
```

to create, move, rename, enable/disable and reorder spawn locations without editing live Lua coordinates.

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

<CardGroup cols={2}>
  <Card title="Installation" icon="download" href="/rco-creator/installation">
    Clean start order and stock resources to disable.
  </Card>

  <Card title="Lifecycle" icon="arrows-rotate" href="/rco-creator/lifecycle">
    How RSG/VORP are handed a ready player.
  </Card>

  <Card title="Spawn locations" icon="map-location-dot" href="/rco-creator/spawn-locations">
    In-game spawn editor, Last Location and selector modes.
  </Card>

  <Card title="API" icon="code" href="/rco-creator/exports">
    Open selection and query selection state from other resources.
  </Card>
</CardGroup>