Documentation
Update Clothing Creator (qs-clothing-designer) without losing a single published piece: what to keep, what to replace, backing up qs-clothing-data, moving to a new server and uninstalling.
Updating Clothing Creator means replacing one folder. Everything you made — designs, published clothing, imported templates, settings — lives in your database and in qs-clothing-data, and neither of them is part of a download.
Everything Clothing Creator puts on your server, and what to do with each piece when a new version comes out:
Piece | What it is | On an update |
|---|---|---|
|
The resource itself. |
Replace it. |
| Your uploads, the textures of every published piece, and your imported templates. | Keep it exactly where it is. Never delete, move or replace it. |
| Generated from your database and qs-clothing-data on every start. | Leave them. Deleting them loses nothing — the next start writes them again. |
The | Designs, published items, settings and history. | Keep them. New columns are added by the resource itself. |
Files you edited |
| Carry your changes over into the new version. |
Settings changed in game survive every update untouched: they live in
qs_clothing_settings, not in a file. A new version only changes the defaults of settings you never touched.
Export the whole database with HeidiSQL, phpMyAdmin or your host's panel, and copy the qs-clothing-data folder somewhere safe.
From the CFX Portal → Granted Assets, exactly as on the first install.
Copy config/config.lua, custom/config.lua, server/webhooks.lua and any bridge or locale you changed out of the old folder.
The new version writes the clothing declarations again on its first start, and a start with nobody online is the moment the game takes them. Restarting only qs-clothing-designer under players works too, but any change to the declarations then waits until the server is empty.
Delete the old qs-clothing-designer folder and drop the new one in the same place. Do not touch qs-clothing-data. Then put your values back into the new files — compare rather than overwrite, a new version may add lines.
A quiet console means a healthy update. Every published collection is rebuilt from qs-clothing-data with the new version on its own — nothing has to be published again.
Open /clothingdesigner → Admin. The capacity of every collection, the items waiting for a restart and your published items are all there. An item listed under Needs re-publishing lost its texture file from qs-clothing-data/items: open its design from Saved Designs and publish it again. Every other item keeps publishing normally in the meantime.
When a newer version is available, the console says so once at start:
[qs-clothing-designer] Update available: 1.0.2 -> 1.0.3Take three things with you: the database, the qs-clothing-data folder and qs-clothing-designer. Leave qs-clothing-meta and qs-clothing-assets behind if you like — the first start on the new machine writes both again from the other two. Add the same add_ace lines to the new server.cfg.
Remove the three ensure lines and the five add_ace resource.qs-clothing-designer lines.
Delete qs-clothing-designer, qs-clothing-meta and qs-clothing-assets. Delete qs-clothing-data only if you do not want to keep the clothes.
Run [sql]/clean.sql on your database. It deletes every design, published item and setting.
Published clothing leaves the game with the resources: a player wearing a published piece is left without it the next time their outfit loads. Keep the database and qs-clothing-data, and a later reinstall brings every piece back exactly as it was.