> 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/essential-knowledge/build-options.md). # Build Options ## Introduction The **Build Project** window in **Durty Cloth Tool** allows you to package your project for FiveM or Singleplayer. Deprecated alt:V and RageMP builders remain available for legacy workflows. This window is essential when you are ready to compile and export your project.\ Here's a breakdown of the options and settings available within this window.

Durty Cloth Tool Build Project Window

## Target Resource Type In this section, you can select the type of resource your project is intended for. The available resource types are: * **alt:V Resource (Deprecated)**: Retains output for legacy workflows. The [official alt:V site](https://altv.mp/) states that the platform has shut down, and DCT no longer validates this output against a maintained runtime. * **Singleplayer RPF**: Packages the project for single-player DLCs using the RPF file format. * **FiveM Resource**: Exports the project as a FiveM resource and enables FiveM-specific patched-limit handling. * **RageMP Resource (Deprecated)**: Retains output for legacy workflows. The [official shutdown announcement](https://rage.mp/forums/topic/26561-long-term-eco-system-integration-pt-ii-final-outreach-cd/) ends RageMP support on August 31, 2026, and DCT no longer validates this output against a maintained runtime. {% hint style="success" %} When **FiveM Resource** is selected, DCT automatically uses FiveM's patched component, global prop, high-heel expression, and alternate-variation limits. It also checks the per-gender YMT slots used by the current project against the selected game build. You do not need to disable the 128 warning manually for FiveM components. {% endhint %} {% hint style="warning" %} DCT does not install or verify FiveM runtime patches and cannot count YMT files or alternate variations from other server resources. Keep both the client and server artifacts current and test the complete resource set. {% endhint %} ## Server Target Game Build (FiveM Only) This dropdown allows you to specify the target game build for the resource. The game build selection will determine which version of the game the project is intended for, ensuring compatibility with specific limits of the selected version of GTA 5. * **Server Build Selector**: Choose the game build forced by your server. Current choices include **3717 mp2025\_02, A Safehouse In The Hills** and **3889 mp2026\_01, The Kortz Center Heist**. ## Replace GTA DLC Clothes (Advanced) This section allows you to replace existing GTA DLC (R\* created) clothing resources. If you want to replace entire GTA 5 DLC clothing resource with your own, this option is for you. * **Show GTA DLC replace options**: When checked, this option reveals advanced options for replacing specific DLC clothing files. ## Clothes Collection Name Here, you specify the name of the collection of clothes that will be used in the final resource. This name will be mainly used internally for various things required by the game. * **Clothes collection name**: Enter a name for your clothing pack. * **Remove default added prefix**: Check this box if you want to remove the default prefix (mp\_m/mp\_f) which is by default automatically added to clothing resources for male or female characters. ## Extra Options This section provides additional export and organizational options that help customize how your project is structured upon export. * **Create sub folders for cloth drawable types**: Organizes different clothing drawable types (e.g., hats, shoes, pants) into their respective subfolders. * **Disable extra YMT files creation**: Prevents the generation of extra YMT files. YMT files are used for defining clothing metadata and structure in GTA 5. * **Disable extra alternate variation features**: Generates fewer alternate-variation entries. FiveM builds normally use the patched 512-result lookup capacity and include the complete supported hair references; disabling this option can make some hair features stop working. * **Create clothes info dump**: Generates a detailed information file containing metadata about the clothes in your project. * **Create tattoos info dump**: Generates a similar file but for tattoo packs. ## Dynamic Config Builders The **Dynamic Config Builders** feature allows the tool to automatically create configuration files for integration with FiveM servers. The following options are some of the dynamic config builders: * **Create xnTattoos config file (FiveM)**: Generates the xnTattoos resource configuration file for FiveM servers. * **Create qb-tattooshop config file (FiveM)**: Exports a config file for the qb-tattooshop resource on FiveM. * **Create ESX-TattooShop config file (FiveM)**: Generates a config file for the ESX-based TattooShop resource on FiveM. {% hint style="info" %} See [#dynamic-config-builders](#dynamic-config-builders "mention") article for more details. {% endhint %} ## Build Output Folder * **Build output folder**: This field specifies where the exported files will be saved. You can manually set the folder or browse for a location using the folder icon. {% hint style="warning" %} Choose a dedicated, disposable folder that contains only DCT-generated output. DCT clears and recreates the generated output before all build checks have finished, so an existing successful build can be removed even when the new build stops on an error. Never select your project data folder, a repository, your Desktop, or a shared resource folder containing hand-authored files. {% endhint %} ## Build Button * **Build**: Once you have configured all the options, click this button to start the build process. The tool will package the project according to the selected settings, generate any necessary configuration files, and export the project to the specified output folder. ## Best Practices * **Choose the Correct Resource Type**: Select FiveM or Singleplayer for current workflows. Use alt:V or RageMP only when maintaining historical output for an existing project. * **Check Config Builders**: If you're deploying to a FiveM server, ensure you generate the necessary configuration files to save time on manual configuration. * **Check Compatibility**: Always select the appropriate game build in the **Server Target Game Build** dropdown to avoid issues with outdated or incompatible game versions. *** This documentation covers the essential features and best practices for using the **Build Project** window in Durty Cloth Tool. ## DLC Load Order (RageMP and Singleplayer) For deprecated **RageMP** output and current **Singleplayer** output, you can define a DLC load order value that influences the order in which the generated DLC is loaded by the game. Adjust this if you need your pack to load before/after others for compatibility or menu ordering.