Using Multiple Clothing Packs
Quick answer
Packs do not know about each other. Each one adds its collections to the same server-wide budget, and each one's documentation only describes itself. The combination is your responsibility.
Difficulty: Intermediate · Affects: both
INFO
Search: multiple packs, several packs, pack a pack b, conflicts, combine, load order.
What stacks and what does not
| Behaviour | Reality |
|---|---|
| YMT slots | Stack across every started resource |
| TxdStore entries | Stack server-wide |
| Alternate variations | Stack server-wide |
| Global drawable IDs | Assigned by load order — they shift when packs change |
| Item names and categories | Independent — two packs can both call something "hoodie" |
Two packs can each be comfortably under every internal limit and still crash the server together. That is the normal case, not a defect in either pack.
Load order matters, but not for capacity
ensure order determines where each collection lands in the global drawable index. Change the order and saved outfits point at different clothes.
ensure zaiders_streetwear
ensure zaiders_formal
ensure eup_uniformsLock this order and document it. Reordering is not a crash fix — it is an ID lever, and using it casually breaks player wardrobes. See Clothing IDs & Outfit Shifts.
Common mistakes
WARNING
Merging folders
Copying three packs' stream/ contents into one resource folder does not merge their collections. The YMT files still load individually and still cost the same slots. Real merging requires repacking.
WARNING
Trusting per-pack documentation
A pack that says "uses 2 YMT slots" is telling the truth about itself and nothing about your server. Only your own budget is authoritative.
WARNING
Blaming the newest pack
The pack installed last is usually just the one that crossed the line. Removing it fixes the symptom and hides the fact that you are at capacity.
A workable policy for multi-pack servers
- Maintain one written clothing budget, updated on every install.
- Prefer fewer, larger packs over many small ones — the slot cost is per collection, not per item.
- Keep
ensureorder fixed and version-controlled. - Decide the game build deliberately, since it sets the ceiling for everything else.
- Test both genders after every clothing change.