> 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/basics/useful-to-know/durty-cloth-projects.md).
# Durty Cloth Projects
Learn about Durty Cloth Projects
The **Durty Cloth Projects** system in Durty Cloth Tool is designed to manage your cloth modding work efficiently by organizing your files and data into a structured project folder. At the core of this system is the `.dctproj` file format and the project’s folder structure, which includes a critical **"data"** subfolder. This setup provides numerous benefits, especially when dealing with large or complex clothing packs, ensuring data consistency and smooth workflow.
Durty Cloth Tool Project Management demo
## Structure of a Durty Cloth Project
Most cloth projects in Durty Cloth Tool will have about the following structure:
```
.dctproj
/clothproject_/
/data/
datacache.dat
/previews/
/backups/
lastautobackup.dctproj
statuslog.txt
```
* **.dctproj File**\
This is the main project file, with a `.dctproj` extension. It contains references to all the assets, settings, and metadata for your project. It works similarly to a project file in any IDE, managing all the links between assets and keeping track of modifications and settings.
* **ClothProject Folder**\
The root folder that houses your entire clothing project. This folder contains all the files related to your project, and is where your projects associated data and files are stored.
* **Data Subfolder**\
The **"data"** subfolder contains important metadata and configuration files related to the clothing models, textures, and other resources. This folder is integral to your project’s integrity and ensures that all relevant data is organized properly.
* **datacache.dat**\
The datacache file contains various runtime information of models powering the clothes validations and quality checks inside of Durty Cloth Tool.
* **previews folder**\
Holds the cached thumbnails shown in the drawable and texture lists. It is disposable and can be cleared and rebuilt at any time.
* **backups folder**\
Holds the restore points behind [Project History](/basics/useful-to-know/project-history.md) and the rotated automatic backups.
* **lastautobackup.dctproj**\
When enabled this file is generated every minute, whenever the project is in an unsaved state. It will be automatically prompted to be restored on application startup and helps in cases where a rollback is required.
* **statuslog.txt**\
This file saves all logged information in your project.
## Project Format
Projects saved by Durty Cloth Tool 4 use the sealed project format **V8**.
* V5, V6 and V7 projects **upgrade automatically** when you open them. Before rewriting anything, DCT keeps a verified format upgrade backup in its own user data folder.
* Older legacy formats remain readable.
* Exports and item packages use the sealed format too, so a build that does not understand it cannot read them.
{% hint style="warning" %}
**A V8 project cannot be opened by an older Durty Cloth Tool build.** An older build leaves it closed and unchanged rather than damaging it. Keep this in mind before moving a project between the Experimental and Release channels. See [Updates & Channels](/basics/good-to-know/updates-and-channels.md).
{% endhint %}
A project saved by a **newer** format than your build understands is rejected before migration, autosave or any rewrite can touch it.
## How Durty Cloth Projects Work
The **Durty Cloth Projects** structure is designed to give cloth maintainers and content creators an organized workspace where assets are linked rather than scattered, allowing for efficient management of clothing resources. When working with multiple clothing models and textures, the structured project format helps:
1. **Project Data Integrity**\
By storing all project related data in the **"data"** subfolder, all required project files and references are kept in sync. This guarantees that when the project is loaded, all related data is restored properly, avoiding missing references or broken models and textures.
2. **Flexibility for Large Projects**\
For larger projects, such as those involving multiple cloth models, textures, or configurations, this structured approach reduces the risk of errors and improves performance by keeping everything organized in one place.
## Project Folder Relocation
Durty Cloth Tool Project Output Folder Setting
To move an existing project's data folder, save the project first, then choose the new parent folder under **Project Settings > Project Output Folder**. Confirm the move when prompted. The destination must not already contain a folder with the same project name.
* **Why Relocation Needs to be Managed by the Tool**\
The **.dctproj** file records where the project data lives. DCT copies and checks the data, including backups and history, and saves the new location before removing the original files. If copying or saving fails, the original project stays in place. If the move succeeds but the old folder cannot be fully removed, DCT keeps using the new location and reports the leftover folder in the status log. Renaming an existing project or enabling shared-project paths uses the same process.
## Project Actions
Durty Cloth Tool provides **Project Actions** to help maintain clean and efficient projects. These actions allow users to analyze and optimize their projects with ease.
Durty Cloth Project Actions
* **Optimize & cleanup project data**: Scans the project for unused files, calculates their total size, and prompts whether to delete them. Deleting unused files is irreversible and reduces project size, but it also removes the files an optimizer undo or an older restore point needs. See [Project History](/basics/useful-to-know/project-history.md).
* **Thumbnail Generator**: Writes thumbnail files for the project into a folder and keeps it in sync. See [Thumbnails & Visual Exports](/basics/good-to-know/thumbnails-and-exports.md).
* **Find duplicates...**: Scans the project for drawables and texture variations with identical file content and lists every group it finds, with thumbnails and a **3D preview** button to compare copies. Duplicates are ticked for removal by default; untick what you want to keep, use **Keep this instead** to keep another copy, and confirm to remove the rest. Unique texture variations of a removed drawable move to the kept one. The same drawable in the other gender and the same texture on another drawable only count when you turn on the matching option.
These actions ensure your project stays organized and optimized, making it easier to manage and reducing unnecessary clutter.
## Automatic Backup Save System
Durty Cloth Tool Automatic Project Backup Setting
To help safeguard your progress, Durty Cloth Tool includes an **automatic up-to-date backup save system** that monitors changes in your project. It can recover the last successfully written backup after a crash, so keep saving regularly as you work.
* **How it Works**\
Whenever there is an unsaved change in the project, a backup copy of the project is automatically created every minute. This backup system can be **enabled via the project settings** and works in the background to continuously protect your work.
* **Restoring from Backup**\
If there is an existing backup that is newer than the last manually saved state, the tool will prompt you to restore the backup when you load the project. This ensures you have the option to retrieve the most recent version of your work, even if you didn’t manually save the project before closing it.\
* **Backup Save Flow:**
1. **Enable Backup System**: Activate the automatic backup system in the **Project Settings**.
2. **Backup Creation**: The tool creates a backup every minute whenever there are unsaved changes.
3. **Auto-Restore**: Upon reopening a project, if a more recent backup exists than the last saved version, the tool will ask if you want to restore the backup.
DCT keeps **five** rotated automatic backups. A backup that cannot be read is preserved rather than deleted, and opening an unreadable project offers its newest readable backup while keeping the damaged file as a copy.
Backup writing happens in the background: the payload is captured briefly, then compressed, encrypted, verified and rotated without holding up your editing.
{% hint style="info" %}
Automatic backups protect you from losing unsaved work. To take back a change you made deliberately, use [Project History](/basics/useful-to-know/project-history.md) instead.
{% endhint %}
## Benefits of the Durty Cloth Projects System
* **Consistency Across Projects**\
The project system ensures that all related assets are neatly organized, making it easier to manage multiple projects without confusion or missing files.
* **Optimized Workflow**\
By keeping metadata in the **"data"** folder and linking assets through the `.dctproj` file, modders can quickly switch between projects, knowing that everything is consistently organized.
* **Scalability**\
For larger projects involving dozens or even hundreds of clothing models and textures, the project system scales easily, keeping everything manageable without losing performance.
## Summary
The **Durty Cloth Projects** system is a powerful core component of DCT to manage your clothing modding workflow. With a structured folder format and the ability to keep metadata organized, it optimizes the process of working with clothing resources. By ensuring consistency, performance, and ease of management, Durty Cloth Tool’s project system is designed for both small and large modding projects alike.
