Skip to content

Clothing and props

Clothing packs contain variation metadata, component models, textures and shop-apparel definitions. Use a pack made for the ped model that will wear it.

With resources.pack.path = "client", a male freemode collection can use this layout:

client/
└── assets/
└── harbor_clothing/
├── content.xml
└── stream/
├── mp_m_freemode_01_harbor.ymt
├── mp_m_freemode_01_harbor.meta
├── mp_m_freemode_01_harbor/
│ └── <component YDD/YTD files>
└── mp_m_freemode_01_p_harbor/
└── <prop YDD/YTD files>

Use the names and files from your export. Keep the variation YMT, component folders and prop folders together in the resource. Female collections use the corresponding mp_f_freemode_01 assets and declarations.

The loader preserves collection prefixes when component and prop folders match the variation metadata. Exported filenames containing ^ also retain their prefix, with ^ interpreted as /. Flattening the folders or removing these prefixes can break model and texture lookup.

For packs delivered as RPF files, see RPF archives.

For the layout above, add this content.xml:

<?xml version="1.0" encoding="UTF-8"?>
<CDataFileMgr__ContentsOfDataFileXml>
<dataFiles>
<Item>
<filename>stream/mp_m_freemode_01_harbor.meta</filename>
<fileType>SHOP_PED_APPAREL_META_FILE</fileType>
</Item>
</dataFiles>
</CDataFileMgr__ContentsOfDataFileXml>

Use the actual shop-apparel filename from the pack. Models, textures and the variation YMT are discovered automatically.

Publish the resources, restart the server to select the release, then restart GTA through the helper to load the new collection.

setComponentVariation and setProp take global drawable indices across the ped model’s loaded collections. Resolve collection-local indices to global indices before applying them. Collection item 0 can have a different global index.

The clothing guide shows how to query a loaded ped, preview items and apply selections on the server. Keep mappings for each model and recheck the catalogue after adding, removing or replacing collections. Use the Torso, Undershirt and Tops combinations required by the clothing pack.

Check all supplied texture variations, matching body components and props. Inspect the outfit from a second client and after leaving streaming range and returning.

Symptom Check
The new items are missing from the available indices Check the target ped model, variation YMT, shop-apparel declaration and client metadata errors.
A different item appears Check whether a collection index was used as a global index, or whether the loaded content changed.
Clothing is invisible or textures are incorrect Check collection prefixes, folder names and the complete YDD/YTD asset set.
Arms or an undershirt clip through a top Check the Torso, Undershirt and Tops combination required by the pack.
Clients show different outfits Confirm they loaded the same resource release and use the same ped model. Apply shared selections on the server.

Metadata errors are recorded in the client logs. Changes to collection metadata or the asset set require a GTA restart. Follow the restart rules when publishing updates.