Documentation
Designing a garment on the UV canvas, publishing it to every player, and what the engine limits cost you.
Open the studio with /clothingdesigner. It is a full-screen editor with three parts:
A 107-piece template pack — base garments per slot, both genders.
A layered UV canvas — brush, eraser, text, shapes, images, AI.
A live 3D preview of the actual garment mesh with your texture on it.
Pick a base garment, paint it, publish. The resource builds the YDD/YTD/YMT files itself, in-process, and streams them to every player.
Publishing renders your design at full resolution, then the C# module patches the template YDD, compresses your textures to BC3 with mip levels, generates the CPedVariationInfo YMT, and writes the collection out in two halves.
The Declaration
GTA only takes clothing declarations while the freemode models are out of memory. That is the whole reason this is not instant every time.
Every used slot declares a few free cells ahead of use (Settings → Reserved cells per slot), so the next items in that slot never touch the declaration.
When one has to change — a new slot, a new collection, or a used-up reserve — the publish cycle does it live:
Every player is moved into a routing bucket of their own.
They press the refresh key, which leaves their game with no freemode model at all.
qs-clothing-meta restarts.
Everyone comes back with the new declaration.
Situation | What happens |
|---|---|
Alone on the server | It simply happens |
With other players online | The studio warns first and only goes ahead on Apply anyway |
Declined | The item waits for the next restart, an empty server, or Admin → Apply now |
:warning: A player whose game still holds a freemode model may crash — because they did not press, or because another script keeps a freemode ped around. That is what the warning is for.
Settings → Apply new slots live turns the live path off entirely.
The Drawables
The .ydd/.ytd files go out in a guarded cycle: every player takes published clothes off, the resource stops, the new files are written, the resource starts, and everything goes back on.
Only when a piece that was already published changes — an edit, a retire — does every player also press the refresh key while the resource is down, because their game may still hold the old version. A brand-new piece has no old version anywhere and skips that step.
Players are never moved for the refresh. They wait where they stand behind the refresh screen, and the key is only offered once their game has finished streaming.
If the output is byte-identical to what is live, nothing cycles at all.
What Is Instant
Action | When it is live |
|---|---|
Editing an item | At once |
Retiring one | At once |
Publishing into a free reserved cell | At once |
A new slot / collection / used-up reserve | At once if you are alone, after your confirmation if you are not |
illenium-appearance, qs-appearance, fivem-appearance, esx_skin, qb-clothing and friends pick new items up automatically — they enumerate drawable counts, and a publish raises them.
If your menu can display labels, qs-clothing-assets/integrations/labels.json maps every published drawable to its name.
Limits are enforced twice: live in the UI — meters, badges, a pre-flight in the publish dialog — and again on the server before any file is written.
Limit | Value | When you hit it |
|---|---|---|
Drawables per slot per collection | 128 | The creator opens an overflow collection automatically |
Texture variations per item | 26 (a–z) | Hard stop — the letters run out |
Texture slots per component per collection | 255 | Pre-flight blocks the publish |
Global prop indices per anchor | 256, shared with the base game | Warning by default. FiveM patches this limit, but the meter keeps you portable |
Retiring an item keeps its slot as an invisible tombstone, so player outfits never shift. The next publish reuses the slot.
Every ped clothing pack already on the server can become editable templates.
/clothingdesigner → Admin → Addon clothing → Scan resources.
The Scan
It reads the stream/ folder of every resource and groups the files the way FiveM streams them — by the name before ^. Folder names do not matter, exactly as in the game.
Importing
Import a whole collection, a slot, or single drawables.
Each one is validated and copied into qs-clothing-data/templates/addons/, together with what its pack's .ymt declares for it: character cloth (the .yld travels with its drawable), footstep audio, component flags, expression mods, prop render flags.
The pack itself is never modified, and once imported it is not needed for publishing any more. Imports run in the background with a progress bar.
Editing An Import
An imported template opens on the pack's own textures: one variation per texture it shipped, each a locked full-canvas layer you paint on top of — or hide, or delete.
What Cannot Be Imported
Case | Why |
|---|---|
Escrowed drawables | Asset Escrow encrypts them. Only the game of a player who owns the licence can open them; the server holds no key. The scan lists them as locked and explains why — ask the seller for an open version |
Alternate drawables ( | Not imported |
Match-previous drawables ( | Not imported |
Only import packs you are allowed to edit.
Good To Know
Imported templates get their own Addons category in the wardrobe.
Importing into a slot the studio keeps off by default — props, head, hair, arms — switches that slot on, unless you switched it off yourself.
Removing an imported template is refused while a published item is built on it.
Imported meshes are not client files. The studio fetches them from the server when an admin opens it, so players never download them.
Drop your own .ydd drawables into:
qs-clothing-data/templates/<male|female>/<slot>/Named like jbib_005_u.ydd, or the streamed name mp_m_freemode_01_x^jbib_005_u.ydd.
Then run /clothingdesigner → Admin → Scan & import.
Put its .ytd textures, its cloth (.yld) and the pack's .ymt next to it and the import picks those up too.
The template appears in the studio right away. Everything an import touches stays in qs-clothing-data, so an update never takes your templates, or the pieces built on them, away.
The shipped templates carry three files each:
File | What it is |
|---|---|
| The drawable the publisher builds on — RSC7 behind an 8-byte marker, so Asset Escrow never encrypts it |
| The studio's 3D preview, packed 16-bit |
| The UV guide drawn over the canvas |
Command | Who | What |
|---|---|---|
| Admin | Opens the studio |
| Console | Apply now — the same as Admin → Apply now |
Admin is your framework's admin: Config.AdminGroups on ESX, god/admin on QB, the ACE command on standalone.
The command's name is set in Settings → Commands — empty means no command.
Almost everything is set in game: /clothingdesigner → the gear icon → Settings. Changes are stored in qs_clothing_settings and take effect at once (a few are marked restart).
Section | Holds |
|---|---|
General | Language, debug logging, saved designs per player |
Commands | The admin command's name |
Textures | Published and preview texture size |
Slots / Capacity | Drawables per slot, reuse of retired slots, prop budget |
Images | Image links, allowed hosts, size limits |
AI | The AI texture tool, provider, model, limits |
Moderation |
|