My Clothing IDs Changed
Saved outfits point at the wrong shirt. The files are usually fine.
Difficulty: Intermediate · Affects: both · collection natives are CONFIRMED
INFO
Search: clothing ids changed, wrong outfit, setpedcomponentvariation, collection natives, ensure order.
Global IDs moved
collection + local index did not · Intermediate
Cause
CONFIRMED by Cfx: custom collections sit after vanilla+DLC. A Title Update inserts official collections; every custom global index shifts.
Confirm
Same files, new game build or a pack ensured earlier. Local index inside your_collection still matches.
Fix: Use collection natives, not a frozen global drawable number. Lock ensure order in server.cfg.
Absolute vs collection-local
Global (absolute)
Count from the start of the ped. Moves after DLC and when packs are inserted earlier.
Old shop scripts that store a raw drawable number break.
Collection-local
Count from the start of this collection. Stays stable when DLC is inserted in front.
Use SetPedCollectionComponentVariation / GetPedDrawableVariationCollectionName / LocalIndex.
Docs: collection-based natives. Client-side GTA V natives.
Other reasons global IDs move
ensure | A new add-on pack started before yours sits earlier in the global list. |
Removed | A pack taken out collapses later global indexes. |
Rebuild | Items reordered inside a rebuilt YMT (“position number”). |
Replace | Replace packs shuffling vanilla collections. |
ensure order is not a YMT crash fix. It is an ID-order lever.
Lock the order and do not shuffle it between deploys:
ensure zaiders_core
ensure zaiders_eup
ensure zaiders_extraWhoever is ensured first sits earlier in the global list.
What not to do
WARNING
Rebuild the pack because IDs moved
The files are usually fine. Scripts stored a global index.
WARNING
Shuffle ensure to “add YMT slots”
Order does not add slots. It only moves IDs.
WARNING
Clear cache
Saved outfits and global indexes are not a cache problem.