Skip to main content
When Appearance misbehaves, start by reproducing one exact action with Config.Debug = true. Then turn debug back off after you have the logs. A useful report looks like: “VORP, existing female character, open tailor → switch coat → Cancel → head disappears.” That is much easier to solve than “appearance bugged.”

​
Resource does not start

Start rsg-core or vorp_core before rco-appearance.
Stop the conflicting RSG/VORP appearance, wardrobe, barber or stock VORP character resource listed in Installation.
Do not run RSG and VORP cores together. Fix the server start list instead of forcing RCO to guess.

​
Character loads with the wrong look

First run:
If the correct saved look returns, the database snapshot is probably fine and the issue came from a later visual mutation by another script. If the wrong look returns again, check migration/persistence instead:
  • did this character ever save an RCO appearance?
  • is a legacy barber/clothing script still writing its old table?
  • is this a third-party appearance schema that RCO cannot automatically migrate?

​
Save works until relog

That almost always means another system is still being treated as authority somewhere. Do not keep a legacy shop that writes playerskins/VORP skin data and expect it to overwrite the canonical RCO snapshot permanently.

​
Cancel does not restore what the player had

Reproduce with only one category change and capture client logs. Save/Cancel should operate on the editor’s original/working snapshot separation. If a custom integration is manually applying appearance while the RCO editor is open, disable that integration during the test.

​
Quick Clothing refuses an action

This is not automatically a bug. Read the returned reason. Examples such as blocked_by_coat, blocked_by_vest or unsupported_npc_clothing mean RCO deliberately refused a composition it could not prove was visually safe. See Quick Clothing.

​
Sleeves or collar does nothing

Sleeves/collar require a compatible MP wearable state on the current garment. RCO does not invent a transform for NPC clothing or for an MP shirt that does not expose the required state.

​
House/hotel wardrobe opens but cannot save

Make sure the integration opens the wardrobe from server code:
A client-only persistent open is intentionally not authorized. See Wardrobe integrations.

​
Player becomes visible while using noclip

Current Appearance apply flows preserve external entity visibility/alpha through appearance transactions. If a custom noclip still conflicts, tell us which resource/natives it uses and reproduce with /reloadskin while noclip is active.

​
Existing character migrated badly

RCO supports the stock framework legacy paths, not arbitrary third-party schemas. If the old data is empty, malformed or from another appearance resource, automatic conversion may intentionally skip it instead of persisting a broken snapshot. Read Migration before trying to “fix” the data by copying rows between tables.

​
What to send in a support ticket

Include:
  • RSG or VORP;
  • whether the character is new or migrated;
  • exact action sequence;
  • client F8 output around the problem;
  • server console output around the same time;
  • whether /reloadskin restores the look;
  • names of any third-party clothing/barber/housing/noclip resource involved.