Stream add-on clothing as a named collection whose drawable, texture and metadata names agree. Keep clothing assets separate from the appearance menu that selects and saves them. Renaming files without updating collection metadata can break both display and saved outfits.
Confirm the target GTA edition before installing or exporting assets. Legacy packages are not automatically Enhanced-ready; follow the official Enhanced asset-conversion guidance when that is your target.
Choose the correct workflow
Decide whether you are adding a freemode clothing collection, replacing an existing item or adding an ordinary world prop. These use different naming and metadata. Confirm the intended male or female ped and component/prop slot before exporting.
Use assets you may modify and distribute. Record the YMTEditor and exporter versions. Verify any current server entitlement requirement in the Cfx.re Portal; old Patreon-key instructions are not an installation procedure.
Prepare the collection
- Keep an untouched copy of the source assets. In the supported editor workflow, create or open the collection for the intended ped.
- Define the drawables and their textures in the YMT data. Preserve the naming convention emitted by that workflow; do not remove ped prefixes or renumber an existing live collection casually.
- Generate the matching apparel metadata and ensure its collection name agrees with the YMT and exported files. Configure skin/material flags according to the asset and editor documentation, not a universal number.
- Place the exported streamable assets in a dedicated resource’s stream directory. Keep the apparel .meta file at the path registered in fxmanifest.lua.
Register the apparel metadata
For a resource with customclothes.meta at its root, this is the manifest registration. The metadata content itself must be generated for your actual collection:
fx_version 'cerulean'
game 'gta5'
files { 'customclothes.meta' }
data_file 'SHOP_PED_APPAREL_META_FILE' 'customclothes.meta'See Cfx.re data-file types. Add ensure followed by the exact resource-folder name to server.cfg after required dependencies.
Integrate and test saved outfits
Check how your appearance resource identifies clothing. The collection-based native documentation explains collection-local selection; global drawable indexes can shift when collections change.
On staging, test every drawable and texture on the intended ped, common animations, clipping and skin/material appearance. Save outfits, reconnect, restart and test existing outfits as well as new ones. Use a fresh client to catch missing packaged files.
If an update changes saved outfit indexes, restore the previous collection and configuration while you plan an explicit data migration. Moving a folder into a group named test does not isolate it from a live server.