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

# Installation

Short guide to get devix-appearance running on your server.

***

## Requirements

* **OneSync** enabled (recommended: Infinity).
* **devix-core** — Must be started **before** devix-appearance. Handles skin save, player identification, and (optionally) inventory integration.
* **Framework** — QB-Core, QBCore, ESX, or QBX; devix-core bridges to it. Start your framework before devix-core.

**Optional:** If you want **purchased clothing as inventory items** (e.g. clothe\_hat, clothe\_tshirt), you need **devix-inventory** and set `Config.ClotheItem = true` and `Config.ClotheItemInventoryResource = "devix-inventory"` in devix-appearance `config.lua`.

***

## Steps

{% stepper %}
{% step %}

### 1. Database

Import the SQL file so saved outfits can be stored:

* **File:** `devix-appearance/devix_appearance_outfits.sql`
* Creates the table `devix_appearance_outfits` (license, charid, outfitName, playerskin).
* Run it in your MySQL client or via your server’s DB setup.

Skin data is usually stored by devix-core (e.g. in a `playerskins` or similar table); if your setup uses a different table, ensure devix-core is configured for it. The outfits table above is only for the **Outfits** tab (saved outfits).
{% endstep %}

{% step %}

### 2. server.cfg

Start devix-appearance **after** devix-core (and your framework). Example:

```cfg
ensure oxmysql
ensure ox_lib
ensure [qb]          # or es_extended / qbx_core
ensure devix-core
ensure devix-inventory   # optional, for clothe_* items
ensure devix-appearance
```

Do **not** start devix-appearance before devix-core.
{% endstep %}

{% step %}

### 3. Config

* **config.lua** — Set locale (`Config.Locale`), barber and clothing shop coords, and whether to use inventory items (`Config.ClotheItem`, `Config.ClotheItemInventoryResource`). See [CONFIG\_MAIN.md](broken://pages/c79dc5beabfc8d7a54b8a16bca1dbf53949524f9).
* **config\_clothing\_prices.lua** — Optional per-drawable and per-shop prices when `Config.UsePerIdClothingPrices = true`. See [CONFIG\_CLOTHING\_PRICES.md](broken://pages/34753f5504c961c4f4755779a1582a6df65007b8).
* **config\_peds.lua** — List of ped models available in the “Character Model” selector. See [CONFIG\_PEDS.md](broken://pages/d25ca6620de38e7d1c158c5202efaae2b6eead29).
  {% endstep %}

{% step %}

### 4. Permissions (admin panel)

To use **/appsadmin**, the player must have permission. By default `Config.AppsAdminAce = "group.admin"`. You can set a custom ACE (e.g. `devix-appearance.appsadmin`) and add it to your admin group:

```
add_ace group.admin devix-appearance.appsadmin allow
```

{% endstep %}
{% endstepper %}

***

## Summary

1. Import **devix\_appearance\_outfits.sql**.
2. Ensure **devix-core** (and framework) before **devix-appearance**.
3. Edit **config.lua** (locale, shops, ClotheItem, etc.).
4. (Optional) Edit **config\_clothing\_prices.lua** and **config\_peds.lua**.
5. Restart the server or ensure the resources.

For config details see [CONFIG\_INDEX.md](broken://pages/5f284c1e0f747dd49aa3d6c271e38e5ce15cafe3). For chat commands (`/apps`, `/appsadmin`) see [COMMANDS.md](broken://pages/bdd9178773bfff40eee39bbf806bfef0aeb0698f). For opening the panel and exports see the main [README.md](broken://pages/b74b7849b17c7fb0defaef16982a0c4d932d937c).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://devix.gitbook.io/devix/devix-appearance/installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.