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

# RCO Identity

> The complete character flow for RedM: selection, creation, appearance, clothing, wardrobe and spawn.

<div className="rco-seal">
  <img src="https://mintcdn.com/rust-co/cmZU40uKikQC_d6z/logo/dark.png?fit=max&auto=format&n=cmZU40uKikQC_d6z&q=85&s=db6db35452234de39f7136329f760680" alt="Rust Co" noZoom width="512" height="512" data-path="logo/dark.png" />

  <div className="rco-wordmark">
    RCO Identity
    <small>Complete Character Ecosystem</small>
  </div>
</div>

RCO Identity is the character layer of your RedM server. From the moment a player connects to the moment they are standing in the world, **Creator** and **Appearance** work together as one flow.

You do not need to understand every internal piece before installing it. The important split is simple:

<CardGroup cols={2}>
  <Card title="RCO Creator" icon="hat-cowboy" href="/rco-creator/overview">
    Character selection, identity, slots and world spawn.
  </Card>

  <Card title="RCO Appearance" icon="user-pen" href="/rco-appearance/overview">
    Face, body, MP + NPC clothing, barber, tattoos, wardrobe and appearance persistence.
  </Card>
</CardGroup>

## The flow players actually see

```text theme={"dark"}
Connect
  ↓
Choose a character
  ↓
Create one if needed
  ↓
Build the character's appearance
  ↓
Choose a spawn
  ↓
Enter the world
  ↓
Tailors, barbers, wardrobes and quick clothing during gameplay
```

Creator owns **who the player is playing and where they enter the world**. Appearance owns **what that character looks like**. Creator requires Appearance, so the normal start order is always:

```cfg theme={"dark"}
ensure oxmysql
ensure rsg-core      # or vorp_core
ensure rco-appearance
ensure rco-creator
```

## Before you install

RCO Identity is a replacement for the stock character/appearance stack, not another layer on top of it. Running the old selector, spawn or clothing resources at the same time is the fastest way to get duplicate UIs and two resources saving different versions of the same character.

<Warning>
  If your server already uses a **third-party** multicharacter or appearance system, do not treat the switch as a hot swap. RCO can migrate the supported stock RSG/VORP data, but it cannot automatically understand every custom database schema on the market. Test the migration on a copy of your server first.
</Warning>

## If you are installing for the first time

<Steps>
  <Step title="Install Appearance first">
    Appearance provides the persistent character look, clothing catalog and editor used by Creator.
  </Step>

  <Step title="Install Creator">
    Disable the stock selector/spawn resources for your framework, then start Creator after Appearance.
  </Step>

  <Step title="Create a test character">
    Go through selection → creation → appearance → spawn once before changing dozens of config values.
  </Step>

  <Step title="Add your integrations">
    Housing/hotels can open the RCO wardrobe, radial menus can use Quick Clothing, and HUD/medical scripts can keep following the normal framework lifecycle.
  </Step>
</Steps>

## Built for RSG and VORP

The same package supports **RSG Core** and **VORP Core**. The user experience is intentionally similar, but the lifecycle underneath is not identical. RCO follows each framework's expected login/spawn contract instead of pretending both frameworks work the same way.

That matters most for:

* framework login events;
* death/medical state;
* legacy appearance migration;
* stock compatibility exports;
* character identifiers and persistence.

When a guide differs by framework, this documentation calls it out explicitly.

## Integration highlights

<CardGroup cols={2}>
  <Card title="Quick Clothing" icon="shirt" href="/rco-appearance/quick-clothing">
    Hat, mask, shirt, coat, boots, sleeves, collar and more — commands, exports and events for radial menus.
  </Card>

  <Card title="Housing & hotel wardrobes" icon="door-open" href="/rco-appearance/wardrobe-integration">
    Open saved outfits safely from houses, hotel rooms, camps or custom interiors.
  </Card>

  <Card title="Character lifecycle" icon="arrows-rotate" href="/rco-creator/lifecycle">
    Know when RSG/VORP considers the player fully spawned and ready for gameplay scripts.
  </Card>

  <Card title="Spawn editor" icon="map-location-dot" href="/rco-creator/spawn-locations">
    Manage spawn locations in-game with `/rcospawns` instead of editing coordinates on a live server.
  </Card>
</CardGroup>

## Need help?

Open a ticket in our [Discord](https://discord.gg/j67u6pbnDs). Tell us whether you use **RSG or VORP**, what you were doing when the problem happened, and include the relevant client/server console output. A short reproduction is much more useful than a screenshot of a single error line.