> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/advanced-clothing/configuration.md).

# Configuration

Which files you can edit, and where each setting lives.

The core of the script is protected by Cfx.re Asset Escrow, but everything you might want to change is in **open files**:

```
Chapo_advanced_clothing/
├── config/
│   ├── config.lua          ← general: locale, tax, payment, camera, showroom, thumbnails, outfit bags, commands
│   ├── shops.lua           ← store / barber / tattoo / surgeon locations, wardrobes, job & gang outfits, locked items
│   ├── sections.lua        ← shop types, sections, price profiles (barber, tattoo, surgeon...), character creator
│   ├── prices.lua          ← base price per clothing category, item overrides, job discounts
│   ├── categories.lua      ← the clothing menu tree
│   ├── names.lua           ← display names for specific items
│   ├── compatibility.lua   ← clipping rules between tops / arms / undershirts
│   ├── hotspots.lua        ← clickable body hotspots
│   └── colors.lua          ← colour filter
├── shared/locales/         ← en.lua, ar.lua
├── bridge/framework/       ← framework adapters, client + server
├── install/                ← ox_inventory items + optional SQL
├── html/                   ← the interface (plain HTML / CSS / JS) + 4,778 thumbnails
└── tools/                  ← optional Node.js helpers for your own thumbnails
```

{% hint style="info" %}
After editing a config file, **restart the resource** (`restart Chapo_advanced_clothing`) or the server. The `onResourceStop` handler closes any open menu cleanly and puts the original appearance back.
{% endhint %}

## Settings by topic

| Page                                                                                                                 | What's inside                                                                                                   |
| -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| [General](/visionstore-docs/scripts/advanced-clothing/configuration/general.md)                                      | Debug, language, interaction, camera, keys, player state, commands, UI, theme, illenium integration             |
| [Prices and payment](/visionstore-docs/scripts/advanced-clothing/configuration/prices-and-payment.md)                | Category prices, item overrides, job discounts, tax, cash / bank, ownership, barber / tattoo / surgeon profiles |
| [Shops and locations](/visionstore-docs/scripts/advanced-clothing/configuration/shops-and-locations.md)              | Every shop field, shop types, the shipped stores, boutiques, fallback entries for illenium                      |
| [Wardrobes, uniforms and locks](/visionstore-docs/scripts/advanced-clothing/configuration/wardrobes-and-uniforms.md) | Wardrobe and locker locations, job / gang outfits, locked items                                                 |
| [Appearance sections and creator](/visionstore-docs/scripts/advanced-clothing/configuration/appearance-sections.md)  | The six sections, the character creator, tattoo catalog, add-on faces                                           |
| [Clothing catalog](/visionstore-docs/scripts/advanced-clothing/configuration/clothing-catalog.md)                    | Categories, item names, compatibility rules, hotspots, thumbnails                                               |
| [Outfits, sharing and bags](/visionstore-docs/scripts/advanced-clothing/configuration/outfits-sharing-bags.md)       | Outfit limits, favourites, share codes, nearby sharing, outfit bags                                             |
| [Showroom](/visionstore-docs/scripts/advanced-clothing/configuration/showroom.md)                                    | The optional private showroom interior                                                                          |
| [Custom peds](/visionstore-docs/scripts/advanced-clothing/configuration/custom-peds.md)                              | `/giveped` and per-model data for non-freemode peds                                                             |

## Languages

Set `Config.Locale` to `"en"` or `"ar"` in `config/config.lua`. The convar `setr Chapo_advanced_clothing:locale "ar"` in `server.cfg` overrides it.

With `Config.AllowPlayerLocale = true` (default), each player can pick their own language with `/appearancelang <code>` or the language button in the interface. The choice is remembered for next time.

To add a language:

1. Copy `shared/locales/en.lua` to `shared/locales/<code>.lua` (for example `fr.lua`).
2. Translate the values. Keep every key and the `%s` placeholders.
3. Set the `meta` block at the top: `code`, `name`, `dir` (`"ltr"` or `"rtl"`) and `font` (`"latin"` or `"arabic"`).
4. Set `Config.Locale = "fr"`, or let players pick it.

Missing keys fall back to English. No manifest change is needed: every file in `shared/locales/` is loaded.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://visionstore.gitbook.io/visionstore-docs/scripts/advanced-clothing/configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.