this one is easier to use:
So we’ve followed your method, but our server is only supporting 12 meta files in total, both male and female included in the 12 files.
Heels working adds an additional “slot” to females. So if you have heels in one pack and have them all adjusted to work and the item checked for heels, females now take up two slots. One for the clothing pack and one for the heels.
You can have heels and hats…I put my heels and hats in the same folder. I had over 100 heels and about 50 hats. I believe it also takes up one more space to do the hats. On both genders.
So if I have two packs for females and two packs for males. And in one of the female packs I have heels and hats (and the adjustments checked). Add on two packs. Guys don’t typically wear heels so they just get the ‘extra’ for hats.
So it ends up being 4 for female and 3 for male (slots) taken up in my previous scenario.
Hey! I’m not 100% sure what you mean, but just to clarify—when I said not to put heels and hats in the same slot, I was talking about generating creaturemetadata with both included. It can technically work, but in my experience, it tends to be unstable and can cause crashes. Don’t ask me why—it just does!
The safest approach is to keep heels and hats in separate packs, so they each have their own creaturemetadata file.
That said, feel free to run your setup however works best for you! I’ve just personally seen crashes, warped body models, and other weird glitches when they’re merged. 