> 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/guides/admin-guide.md).

# Admin guide

The free admin menu, custom peds, closing a player's menu and the admin tools.

Admin commands are restricted to the ace group in `Config.Commands` (`group.admin` by default):

```properties
add_principal identifier.license:YOUR_LICENSE group.admin
```

## The admin menu

**`/clothingshop`** (alias **`/pedmenu`**) opens a **free** menu with all six sections (FACE & BODY, FACE ADJUSTMENTS, OVERLAYS, HAIR, APPAREL, TATTOOS) and every clothing category.

| Command            | What it does                                          |
| ------------------ | ----------------------------------------------------- |
| `/clothingshop`    | Open the admin menu on yourself                       |
| `/clothingshop 12` | Open it on player 12 (they don't need to be an admin) |
| `clothingshop 12`  | The same, from the server console                     |

Opening it on a player gives them a 60-second permission to use the admin menu, so it works even though they aren't an admin. Nothing they pick is charged.

{% hint style="info" %}
illenium's own `/pedmenu` must be off (`Config.EnablePedMenu = false` in illenium), as described in [illenium-appearance setup](/visionstore-docs/scripts/advanced-clothing/illenium-setup.md).
{% endhint %}

## Custom peds

| Command                         | What it does                                    |
| ------------------------------- | ----------------------------------------------- |
| `/giveped 12 a_m_m_business_01` | Give player 12's **character** that ped model   |
| `/giveped 12 reset`             | Remove it and put the character's own skin back |

Both also work from the server console. You get a notification with the result:

| Message                                                            | Meaning                                                                                                         |
| ------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------- |
| **Unknown ped model: x**                                           | The name is wrong, or the player's game doesn't have that ped. Nothing changed.                                 |
| **The ped model x could not be loaded**                            | The model didn't load in time (`Config.CustomPeds.modelTimeoutMs`). Nothing changed.                            |
| **... has the clothing menu open - try again once it is closed**   | Wait until the player closes the menu.                                                                          |
| **... has no character loaded**                                    | The player is still at the character selection.                                                                 |
| **...'s loaded character has no custom ped - nothing was changed** | A reset on a character without a custom ped.                                                                    |
| **The game refused to change the ped of ...**                      | An anticheat is probably blocking model changes. Whitelist `illenium-appearance` and `Chapo_advanced_clothing`. |

Assignments are per **character**: a player's other characters are not affected. For add-on peds, make sure the ped's stream resource is started and that step 4 of [illenium-appearance setup](/visionstore-docs/scripts/advanced-clothing/illenium-setup.md) is applied. More in [Custom peds](/visionstore-docs/scripts/advanced-clothing/configuration/custom-peds.md).

## Close a player's menu

If a player is stuck in a menu, run this from any server script or your admin menu:

```lua
TriggerClientEvent("Chapo_advanced_clothing:client:forceClose", targetId, "admin")
```

It closes the menu as a cancel (nothing is bought), and also works on the character creator, which normally refuses ESC.

## Admin tools

| Command           | Permission                                            | Used for                                                                                                                                                         |
| ----------------- | ----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `/clothingcolors` | `chapo.clothing.colors` ace, or the `command` ace     | Build the colour filter index. See [Colour filter](/visionstore-docs/scripts/advanced-clothing/guides/colour-filter.md).                                         |
| `/clothingmap`    | `chapo.clothing.thumbnails` ace, or the `command` ace | Map clothing collections, only when adding your own thumbnails. See [Add-on thumbnails](/visionstore-docs/scripts/advanced-clothing/guides/addon-thumbnails.md). |

Grant a dedicated permission to your admin group if needed:

```properties
add_ace group.admin chapo.clothing.colors allow
add_ace group.admin chapo.clothing.thumbnails allow
```

## Debugging

Set `Config.Debug = true` in `config/config.lua` and restart the resource. Debug lines prefixed `[Chapo_advanced_clothing]` then appear in F8 and the server console, zones get outlines, and every purchase is logged on the server. Player identifiers are never printed.


---

# 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/guides/admin-guide.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.
