Installation

Install RCO Appearance cleanly on RSG Core or VORP Core.

The install itself is short. Most broken installs come from one thing: the old appearance resources are still running.

If you also use RCO Creator, install Appearance first and keep it above Creator in the start order.

1. Stop the resources RCO replaces

RSG Core

Stop these stock resources:

# ensure rsg-appearance
# ensure rsg-wardrobe
# ensure rsg-barbers

rsg-bathing and rsg-prison are not replaced and can stay.

VORP Core

Stop these stock appearance/character-shop resources:

# ensure vorp_character
# ensure vorp_barbershop
# ensure vorp_clothingstore

vorp_stores is a general item-shop resource and can stay.

provide is compatibility, not permission to run both systems. RCO can answer for legacy resource names so dependencies resolve, but the stock resource itself must still be stopped.

2. Put the resource in your server

resources/
└── [rco]/
    ├── rco-appearance/
    └── rco-creator/       # only if you use Creator

Keep the folder names exactly as shipped.

3. Use the correct start order

RSG Core

ensure oxmysql
ensure rsg-core
ensure rco-appearance
ensure rco-creator     # optional, but always after Appearance

VORP Core

ensure oxmysql
ensure vorp_core
ensure rco-appearance
ensure rco-creator     # optional, but always after Appearance

4. Database

On a normal installation, RCO creates the tables it needs automatically. You should not need to paste SQL manually unless your host blocks schema creation/alter operations.

Appearance persistence is separate from Creator persistence. Your existing legacy tables are not deleted.

5. Existing characters

If this is a fresh server, there is nothing else to do.

If players already exist, read Migration before production. Supported stock RSG/VORP appearance data can be converted when the character is first loaded into RCO. Third-party appearance databases are not automatically understood.

6. First smoke test

Do this before changing prices, locations or UI options:

1. Start the server and confirm there are no startup conflicts.
2. Join with a real character.
3. Open a clothing store.
4. Change one item and Save.
5. Reopen the store and confirm it is still equipped.
6. Run /reloadskin and confirm the saved look remains identical.
7. Open the editor again, change something and Cancel; the original look should return.
8. If using Creator, create a brand-new character and complete the whole creation → spawn flow once.

If something fails, turn on Config.Debug temporarily and reproduce the exact action. “It broke after installing” is hard to diagnose; “Save in tailor returns X after changing coat” is usually straightforward.

7. Next integrations

Once the base test passes:

• connect houses/hotels using OpenWardrobe;
• connect radial menus using Quick Clothing;
• review legacy scripts in Compatibility.