Shops & overlays

Physical editor locations are defined in Config.Stores. A store entry answers three practical questions: where does the player interact, what editor should open, and where should the character stand while editing?

Store types

`type`	Opens	Typical place
`clothing`	Tailor / clothing editor	Tailor shop
`barber`	Hair and face-related editor	Barber chair
`wardrobe`	Saved outfits	Wardrobe / changing room
`tattoo`	Tattoo / overlay editor	Tattoo or custom creator location

Example store

{
    id = 'wardrobe_valentine',
    type = 'wardrobe',
    label = 'Wardrobe',
    prompt = vector3(-325.95, 806.58, 117.89),
    fitting = vector4(-327.77, 807.77, 117.89, 254.59),
    blip = vector3(-327.07, 807.77, 117.89),
    showBlip = true,
},

Use a unique id for every location. prompt is the interaction point; fitting is the character position/heading while the editor is active; blip controls the map icon location.

Physical wardrobe vs house/hotel wardrobe

A type = 'wardrobe' entry is useful for a fixed public location. For a private house, hotel room or camp, do not generate hundreds of fake Config.Stores entries. Call the server-side wardrobe API when your own interaction succeeds:

exports['rco-appearance']:OpenWardrobe(source)

That opens saved-outfit mode only. Full guide: Wardrobe integrations.

Tailor save behavior

The player is free to preview clothing while the editor is open. The saved appearance changes only when the final save succeeds. That distinction is important with NPC clothing, because changing one visible mesh can also require body alpha/wearable-state changes underneath. RCO keeps that composition inside the working snapshot instead of treating every preview frame as permanent data.

NPC clothing and alpha controls

NPC garments may use body alpha to hide the skin that would otherwise clip through the mesh. Some categories can require both upper and lower body alpha (for example, garments that span more than one body region). Do not try to reproduce that logic from an external clothing script by directly removing MetaPed categories. Use RCO’s editor/API so the garment and its body state stay together.

Custom tattoos and overlays

Put the streamed texture asset in your resource as documented by the pack, then register the overlay in config/overlays.lua or an addon file under config/addons/. A good addon file should contain only one logical pack. That gives you a clean way to disable a broken pack without touching your base overlay list.

An overlay entry is configuration; the actual texture still has to exist and stream correctly. If the option appears in the UI but nothing changes on the ped, verify the texture dictionary/name first.

Testing a new store

Before copying the entry to ten towns:

test the prompt;
confirm the fitting position/heading;
preview and cancel;
reopen, save one change and relog;
test at night if the interior is dark;
if it is wardrobe mode, switch outfits quickly and verify the final outfit persists.

Getting Started

Guides

Reference

Store types

Example store

Physical wardrobe vs house/hotel wardrobe

Tailor save behavior

NPC clothing and alpha controls

Custom tattoos and overlays

Testing a new store

​Store types

​Example store

​Physical wardrobe vs house/hotel wardrobe

​Tailor save behavior

​NPC clothing and alpha controls

​Custom tattoos and overlays

​Testing a new store

Store types

Example store

Physical wardrobe vs house/hotel wardrobe

Tailor save behavior

NPC clothing and alpha controls

Custom tattoos and overlays

Testing a new store