The calibration system scans your server's clothing files to build a collection database. This is required when you add or remove addon clothing packs.
| Scenario | Calibration Required? |
|---|---|
| Fresh install with default clothes only | No |
| Fresh install with addon clothes | Yes |
| Added new addon clothing pack | Yes |
| Removed an addon clothing pack | Yes |
| Updated existing addon pack | Yes |
| Using only base game + DLC clothes | No |
Default clothes (base game and DLC) are automatically detected without calibration. Calibration is only needed for custom addon clothing packs.
/clothescallibrateall
Scans all clothing collections (base, DLC, and addons) in one operation.
When to use:
Requirements:
Full calibration can take several minutes depending on how many addon packs you have. The server will notify you when complete.
/clothescallibrate [rarity] [addonName]
Scans a specific rarity tier or individual addon collection.
Parameters:
| Parameter | Values | Description |
|---|---|---|
rarity | base, dlc, addon | Which tier to scan |
addonName | (optional) | Specific addon name |
Examples:
Use selective calibration after adding a single new addon pack - it's much faster than full calibration.
/clothesvalidate
Checks all collection data files for errors and integrity issues.
What it checks:
When to use:
/creationrepriceall
Regenerates prices for all clothing items based on your pricing configuration.
Behavior:
priceOverride flagCalibration creates JSON files in the collections/ folder:
Each component has a JSON file containing item data:
collections/addons/mypack/male/torso.json
| Field | Description |
|---|---|
localIndex | Item's index within the collection |
textureCount | Number of texture variations |
hash | Unique identifier for the item |
priceOverride | If true, manual price is preserved |
label | Custom display name (optional) |
The calibration system scans these clothing components:
| Component | ID | Description |
|---|---|---|
face_skin | 0 | Face/Head |
mask | 1 | Masks |
hair | 2 | Hair styles |
arms | 3 | Arms/Gloves |
pants | 4 | Legs/Pants |
bag | 5 | Bags/Parachutes |
shoes | 6 | Shoes/Feet |
accessory | 7 | Accessories |
shirt | 8 | Undershirt |
vest | 9 | Body armor/Vest |
decals | 10 | Decals/Badges |
torso | 11 | Torso/Jacket |
| Component | ID | Description |
|---|---|---|
hat | 0 | Hats/Helmets |
glass | 1 | Glasses |
ear | 2 | Earrings |
watch | 6 | Watches |
bracelet | 7 | Bracelets |
Place your addon clothing packs in the server's resources folder.
Launch your server and connect as an admin player.
/clothescallibrateall
The server will notify you when calibration is complete.
/clothesvalidate
See Previews Guide for recording preview images.
/clothesstudio
Place the new addon pack files in your server's resources folder.
Restart the server or refresh resources to load the new addon.
/clothescallibrate addon newpackname
/clothesvalidate
/shootclothes addon newpackname
Delete the addon pack from your server's resources folder.
Delete the folder: collections/addons/packname/
Delete the folder: previews/addons/packname/
Restart the server to apply changes.
Problem: Command does nothing or returns error
Solutions:
Problem: New addon items don't show in menus
Solutions:
/clothesvalidate to check for errorsProblem: Full calibration runs for extended time
Solutions:
/clothescallibrate addon packnameProblem: Validation shows errors
Solutions:
Backup before major changes - Copy collections/ folder before large operations
Use selective calibration - Only calibrate what changed, not everything
Validate after calibration - Always run /clothesvalidate to confirm success
Document your addons - Keep a list of installed addon pack names for reference
Test in staging - Calibrate on a test server before production if possible
Last updated 27 days ago