> For the complete documentation index, see [llms.txt](https://docs.gta.clothing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gta.clothing/how-to-guides/bring-an-existing-add-on-pack-into-dct.md).

# Bring an Existing Add-on Pack into DCT

Turn a clothing pack you already built into a DCT project, check it and build it again

Already have clothing packs that you built before you used Durty Cloth Tool? You do not need their old working files. DCT reads the built pack itself, a FiveM resource or a Singleplayer DLC pack, and turns it into clothing in your project with the settings the pack carries. From there you can rename, reorder, optimize and add to it like any other clothing, and build it again for your server.

This guide covers one pack, a zip and a folder that holds several packs. For every format DCT reads, see [Importing from a built resource](https://docs.gta.clothing/basics/useful-to-know/import-and-export-formats.md#importing-from-a-built-resource).

## Before you start

* Adding from a built resource needs an active **Advanced** or **Ultimate** license. See [License Activation](https://docs.gta.clothing/getting-started/license-activation.md).
* Keep an untouched copy of the pack. DCT does not change the pack you import from, but you will build the new version into a different folder and compare the two.
* Keep each pack complete: its manifest (such as `fxmanifest.lua`), its `stream` folder and its `.ymt` and `.meta` files together, or the whole `dlc.rpf` for Singleplayer. Without the `.ymt`, DCT can only add the models as loose clothing, without the order and settings the pack had.
* Decide where the clothing goes. To start a new project from the pack, use **Start from a built cloth resource** on [Home](https://docs.gta.clothing/basics/useful-to-know/home-and-quick-look.md), or drop the pack on Home. To add it to a project you already have, open that project first.

{% hint style="info" %}
Did DCT build the pack? Then the project it came from is the better source, because a built pack cannot carry your own item names, tags, project settings or History. When that project is on this computer, the review offers to open it instead, see [A pack DCT built](#a-pack-dct-built).
{% endhint %}

## Import the pack

1. Under the item list, open **Add** and choose **From another source > Add from built resource...** (or press **Ctrl+K** and paste `>Add from built`).
2. Pick the pack's manifest, its `dlc.rpf` or its ped variation `.ymt`. You can also drop the pack's folder, its manifest or a zip of it on the item list, or pick it with **Add from file(s)** or **Add from folder(s)**.
3. Read the **Add from built resource** review. **Recognised as** names the kind of pack DCT found, and **Collections found in the resource** lists each clothing collection with its **Gender** and how many **Components**, **Props** and **Textures** it holds. **No model** and **No texture** count the entries the pack lists without a file, and **Import notes** explains anything DCT will handle differently.
4. Untick a collection you do not want under **Import**. When DCT could not tell a collection's gender, choose **Male** or **Female** for it.
5. Check the **Options**, described in [What DCT keeps](#what-dct-keeps) and [What DCT changes](#what-dct-changes). The line below them says how many drawables and textures will be added.
6. Choose **Import**. The progress panel shows the import and can be cancelled; clothing that was already added stays.

When the import ends, a summary says how many drawables, reservation dummies, texture variations and metadata notes it added. Continue with [Check the result](#check-the-result).

### A zip or a folder of several packs

* **A zip:** drop it on the item list or pick it with **Add from file(s)**. DCT unpacks it and opens the review of each pack it holds. When a zip holds several zips, such as one per platform, **Choose the zips to add** asks which to add. Tick only one platform, because the others usually hold the same clothing. See [Zip archives](https://docs.gta.clothing/basics/useful-to-know/import-and-export-formats.md#zip-archives).
* **A folder of several packs**, such as a server's `[clothing]` folder: pick it with **Add from folder(s)** or drop it. Each pack opens its own review, one after the other. Resources without clothing, such as scripts, are left out and named in the status bar.
* **A pack DCT split into several resources:** pick the first one. The review offers **Also import the further resource folders of the same Durty Cloth Tool build (split resources), in order**.

### A pack DCT built

A pack DCT built remembers its project. When that project is in your recent projects, the review shows **Open project**, which opens it instead of importing. When it was moved, renamed or made on another computer, **Locate project...** lets you pick its `.dctproj` file, and DCT opens it only when it is the project that built the pack. You can still choose **Import** to rebuild the clothing from the files.

### Asset Escrow packs

A FiveM pack protected by Asset Escrow is added whole, together with its `.fxap` key, and its clothing is marked **Escrow protected**. Only import packs you are entitled to use. See [Work with Asset Escrow Clothing](https://docs.gta.clothing/how-to-guides/use-asset-escrow-clothing.md) for what you can change and how to build them.

## What DCT keeps

* **The order of each collection.** Every drawable comes in at the place the pack's `.ymt` lists it. With **Keep the collection order: import ymt entries without a model file as reservation dummies** on (the default), an entry without a model becomes a [reservation dummy](https://docs.gta.clothing/basics/good-to-know/placeholders-dummy-ids.md), so the clothing after it keeps its number. A listed texture without a file becomes a dummy variation for the same reason.
* **The clothing itself.** Types, texture letters, skin tone spelling, alternate models and mesh physics (YLD) files come with their drawables.
* **The settings.** With **Import metadata (behaviour flags, heels, hair options, audio, shop data, first person settings)** on, DCT reads [behaviour flags](https://docs.gta.clothing/game-mechanics/behaviour-flags.md), [heel heights](https://docs.gta.clothing/basics/essential-knowledge/high-heels.md), the hair options of hats, [audio presets](https://docs.gta.clothing/basics/essential-knowledge/audio-presets.md), [shop data](https://docs.gta.clothing/game-mechanics/shop-meta-file.md) and first person settings from the pack's `.ymt` and `.meta` files.
* **Tattoos and overlays** in the pack, with their placements and shop settings. See [Tattoos & Overlays](https://docs.gta.clothing/tattoos-makeup-and-overlays/addon-tattoos.md).
* **The collection name**, when you start from an empty project: **Use the resource's collection name for this project** sets the project's [Clothes collection name](https://docs.gta.clothing/basics/essential-knowledge/build-options.md#clothes-collection-name) to the pack's.

## What DCT changes

* **Clothing added to a project that already has clothing** comes after the drawables already there, in each type. Its numbers in game then change, so update scripts or outfits that refer to it by number.
* **Files the `.ymt` does not list** are added too, because they usually belong to the pack. **Also add the N texture variation(s) that sit beside their models but are not listed in the ymt** adds textures the pack's `.ymt` forgot, and **Also add the N model file(s) no ymt lists** adds loose models through the regular file import. Both start ticked; untick them to bring in only what the `.ymt` lists. These textures did not show in game before, so the rebuilt pack offers more variations than the original.
* **Copies of the game's own clothing lists**, which packs that replace game clothing ship, do not become hundreds of reservation dummies. The items that have files come in as new add-on clothing, not as replacements, so their numbers in game change.
* **Files the game never loads for the pack**, such as another skin spelling of a model, are not imported. The log names them.
* **Settings DCT has no control for** cannot be kept. The summary counts them as notes about metadata, and the [Logs](https://docs.gta.clothing/basics/useful-to-know/logs.md) list each one.
* **Tattoo collections** are named after your project when you build. Update scripts or shop configurations that use the pack's original tattoo collection name.
* **Duplicates are not checked** during the import, so the pack comes in exactly as it is. You check them right after.

## Check the result

1. In the summary, choose **Find duplicates**. **Find & Remove duplicates** lists clothing the project already had or the pack held twice. Untick what you want to keep, then confirm. Reservation dummies are never listed. You can run the scan later from **Tools > Find & Remove duplicates...**.
2. If the summary mentions warnings or metadata notes, open **View > Logs Output** and read them.
3. Open the [Error List](https://docs.gta.clothing/how-to-guides/review-and-tune-project-findings.md) with the **Error List** button (or press **Ctrl+K** and paste `>Error List`). Start with **Errors**: a missing or unreadable file, or more clothing of one type than a collection can hold, needs attention before you build. Select a finding to jump to its clothing.
4. Choose **Fix safe findings** to repair, in one step, what needs no choice from you, such as missing mip maps. Its review shows what changes, and everything it fixes becomes one restore point in [Project History](https://docs.gta.clothing/basics/useful-to-know/project-history.md). Work through the remaining **Warnings** with their own **Fix** actions.
5. Preview a few drawables of each type in the [3D preview](https://docs.gta.clothing/basics/essential-knowledge/3d-preview-clothes.md), including clothing with heels, hats or first person settings.
6. Save the project.

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-1157d57487be7926ec4945aab037061d9859b964%2Ferror-list-warnings.png?alt=media" alt="The Error List with messages hidden, showing 1 error and 1 warning: High heels without a heel rig on Female 1 shoes with the Fix Rig as high heel, and Drawable without textures on Hoodie with the Fix Add texture, each with its level, rule, description and More actions button."><figcaption><p>The Error List with messages hidden: each finding names its rule and item, with its Fix action on the right.</p></figcaption></figure>

<figure><img src="https://2130288373-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRsXe3tqSiAvM8iKYjngE%2Fuploads%2Fgit-blob-d8fc285c4cf46d991b803bf8e3bb43d1c69d9199%2Ffind-duplicates.png?alt=media" alt="Find &#x26; Remove duplicates after a scan: one group of two drawables with the same model, the kept Male 16 top and the ticked duplicate Male 16 top copy, each with 3D preview and Mark as not a duplicate, Keep this instead on the duplicate, and Remove 1 selected duplicate at the bottom."><figcaption><p>Find &#x26; Remove duplicates: review clothing the pack held twice or the project already had.</p></figcaption></figure>

## Build the pack again

1. Choose **Build project** (or press **Ctrl+K** and paste `>Build project`).
2. On the **Output and target** tab, under **Target resource type**, choose **FiveM Resource** or **Single player RPF**, and for FiveM the edition your server runs.
3. Further down the same tab, check the **Clothes collection name**. Keep the pack's name when your scripts and saved outfits should find the clothing where it was; a new name makes a new collection.
4. Choose a new, empty **Build output folder**. Never build into the folder of the pack you imported from, or into a folder with your own files: a finished build replaces what it built there. See [Build Output Folder](https://docs.gta.clothing/basics/essential-knowledge/build-options.md#build-output-folder).
5. Read the **Build overview**, which lists every resource the build makes, then build.
6. On a test server, replace the old pack with the new build. Do not run both, because they hold the same clothing. Test both genders, texture variations and saved outfits in game, see [Testing Addon Clothes](https://docs.gta.clothing/getting-started/testing-addon-clothes.md).

{% hint style="success" %}
Your pack is now a DCT project. Add new clothing to it, [optimize it](https://docs.gta.clothing/how-to-guides/optimize-clothing-models-and-textures.md) or [build it as several resources](https://docs.gta.clothing/how-to-guides/build-large-clothing-resources.md) as it grows.
{% endhint %}

## Troubleshooting

* **The models came in without their settings.** Without an active license, packs found in a folder or zip are added as loose clothing, without the order and settings of their `.ymt` and `.meta` files, and a status line says so. Remove those items, activate a license and add the pack again.
* **The resource could not be read.** Pick the manifest, `dlc.rpf` or `.ymt` of a complete pack. When a pack holds models but no ped variation `.ymt`, this import has no clothing list to read; add its models with **Add from file(s)** instead.
* **A zip is refused.** DCT does not unpack password protected zips or zips with unsafe file names, and leaves out other archive kinds. Unpack it with a zip program and add the folder.
* **A protected file was refused.** An Asset Escrow file without its `.fxap` key cannot be added. Add the complete downloaded resource, see [Work with Asset Escrow Clothing](https://docs.gta.clothing/how-to-guides/use-asset-escrow-clothing.md).
* **Fewer items than files.** Files the game never loads are left out, and the log names them. When you added the pack with **Only male** or **Only female**, the other gender starts unticked in the review.

## See also

* [Import & Export Formats](https://docs.gta.clothing/basics/useful-to-know/import-and-export-formats.md)
* [Review and Tune Project Findings](https://docs.gta.clothing/how-to-guides/review-and-tune-project-findings.md)
* [Cloth Analysis Report](https://docs.gta.clothing/basics/essential-knowledge/cloth-analysis-report.md)
* [Build Options](https://docs.gta.clothing/basics/essential-knowledge/build-options.md)
* [Placeholders/Dummy Ids](https://docs.gta.clothing/basics/good-to-know/placeholders-dummy-ids.md)
