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

# 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

<Tabs>
  <Tab title="RSG Core">
    ```cfg theme={"dark"}
    # ensure rsg-multicharacter
    # ensure rsg-spawn
    # ensure rsg-appearance
    # ensure rsg-wardrobe
    # ensure rsg-barbers
    ```

    Appearance replaces the last three; Creator replaces multicharacter/spawn.
  </Tab>

  <Tab title="VORP Core">
    ```cfg theme={"dark"}
    # ensure vorp_character
    # ensure vorp_barbershop
    # ensure vorp_clothingstore
    ```

    `vorp_core` stays running. RCO integrates with it; RCO does not replace the core.
  </Tab>
</Tabs>

## 2. Start resources in order

<Tabs>
  <Tab title="RSG Core">
    ```cfg theme={"dark"}
    ensure oxmysql
    ensure rsg-core
    ensure rco-appearance
    ensure rco-creator
    ```
  </Tab>

  <Tab title="VORP Core">
    ```cfg theme={"dark"}
    ensure oxmysql
    ensure vorp_core
    ensure rco-appearance
    ensure rco-creator
    ```
  </Tab>
</Tabs>

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:

```text theme={"dark"}
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.

## 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](/rco-creator/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:

```cfg theme={"dark"}
add_ace group.admin rco.creator.spawns allow
```

You can also customize the server-side permission function. Full guide: [Spawn locations](/rco-creator/spawn-locations).

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