Skip to main content
Rust Co
RCO Identity Complete Character Ecosystem
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:

RCO Creator

Character selection, identity, slots and world spawn.

RCO Appearance

Face, body, MP + NPC clothing, barber, tattoos, wardrobe and appearance persistence.

​
The flow players actually see

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:

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

​
If you are installing for the first time

1

Install Appearance first

Appearance provides the persistent character look, clothing catalog and editor used by Creator.
2

Install Creator

Disable the stock selector/spawn resources for your framework, then start Creator after Appearance.
3

Create a test character

Go through selection → creation → appearance → spawn once before changing dozens of config values.
4

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.

​
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

Quick Clothing

Hat, mask, shirt, coat, boots, sleeves, collar and more — commands, exports and events for radial menus.

Housing & hotel wardrobes

Open saved outfits safely from houses, hotel rooms, camps or custom interiors.

Character lifecycle

Know when RSG/VORP considers the player fully spawned and ready for gameplay scripts.

Spawn editor

Manage spawn locations in-game with /rcospawns instead of editing coordinates on a live server.

​
Need help?

Open a ticket in our Discord. 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.