@gooochyeeeIt's odd that this is being brought up again now specifically, as the tags for this item are Female/Feminine and Allow For Random DISABLED. While it is not Gender Restricted, I don't see how this specific underwear could appear randomly on any male child sim.
I assume the reason it's not Gender Restricted is because, as @mightyspritesims correctly says, boys and men wear underwear like this and blue is consumerism for boys.
It's a PartFlag issue. EAxis didn't want to clone the item and make "boy colors" and they didn't bother to flag it properly. Swatches can be flagged independently of each other but I believe that leads to other issues.
THE ONLY WAY to see this in CAS is to swap the Fashion Choice filter or activate both. It is the equivalent of doing the same with YA or older sims and seeing opposite "fashion choice" items.
In other words, this is a non-issue as it's currently configured. (And yes, I did just verify these tags in S4S.)
EDIT: Also, because this specific swatch is AFR DISABLED while the "girly" swatches aren't, even girls won't have it randomly assigned to them in-game. From this, I think it was mean to be a standalone boys recolor. I'll be fixing that AFR flag in my BG PartFlag Fixes.
UPDATE #1: See my followup reply at #13. @gooochyeee is correct, there's an issue here and it has to do with the DefaultForBodyType. The CAS items are correctly flagged but the game is apparently ignoring them and applying the DefaultForBodyTypeFemale item to boys (per UPDATE #2, the issue is more complicated than this).
UPDATE #2: See my followup reply at #16 for my findings. Cheers!
@gooochyeeeYeah, something's not right here.
The blue underwear we're seeing is correctly tagged as Female/Feminine and DefaultForBodyTypeFemale and the briefs are correctly tagged Male/Masculine and DefaultForBodyTypeMale. They both have the correct Age flags as well.
I'll extract these two items as overrides and see if I can't get to the bottom of this cause these flags/tags all appear correct at first glance. (I'm currently overriding BG to fix PartFlags but I'm not at Clothing Bottoms yet so I didn't notice this myself.) It's NOT supposed to be doing what we're seeing. Even without the Restrict Opposite flags, it is supposed to work.
EDIT: Now that I think about it, I think this has been busted for some time. I think I noticed this on a family with a boy child I was troubleshooting for a simmer over on Reddit. I thought it odd the kid was wearing the blue undies since they're supposed to default to the blue briefs but didn't bother looking into it at the time. I just woke up. The memory bank wasn't fully operational yet. Lol. That was back in Feb 2024 if I'm not mistaken, or Jan 2024, sometime before the Malware incident, so if this is a bug causing the game to ignore the flags it could've been one of the many things broken in the Dec 2023 patches.
@gooochyeee
Okay, there's definitely some weirdness happening under the hood here.
Restrict Opposite Gender is the ONLY way this works.
If I flag a different item as DefaultForBodyTypeMale, both girls and boys use it even if it's only flagged for Male Gender and Masculine Fashion. The game doesn't appear to be differentiating Body Type for children, maybe because they both use the same uni___ bodies? It ONLY appears to be acknowledging the Gender.
If I remove the new DFBTMale item and simply flag that one blue underwear as ROGender ENABLED in an override, the blue briefs properly appear on the boys and the blue underwear properly appears on the girls.
Flagging the blue briefs as ROGender ENABLED in an override should work as well because whatever is in the Mods folder will override what the game is using, so it will force the game to use the blue briefs for the boys while blocking it for girls in a vice versa way.
I don't like ROGender flags because EAxis keeps screwing them up. For older sims, Teen and up, if you've got a Female/Masculine Frame sim or a Male/Feminine Frame sim, ROGender ENABLED forces you to wear the clothing for the "Gender", not the "Frame", which causes visual warping in different areas of the body because mismatched gender meshes don't play nice. All the reports about clothes warping necks and crotches is this; it's incorrect PartFlags.
I have never, in all the override fixes I've done so far, seen this occur with Teen+ clothing including DFBT<gender> flagged clothing. This is seems specific to Child and maybe younger ages because they use uni___ bodies.
I'm glad I saw this thread. I'm gonna have to keep it in mind to check Child and younger clothes to ensure they're functioning as intended cause I'm doing override mods for every content release to fix the incorrect PartFlags EAxis keeps giving us.
Cheers!
UPDATE: ROGender ENABLE the briefs instead. It's a separate item that's already AFR DISABLED and it has the desired effect of forcing the game to apply the briefs to the boys while leaving the underwear on the girls like it's already configured to but not doing Because Reasons™.
Double cheers! Chairs squared! <cackles maniacally> Now then, back to me figuring out how to squash the tummy bloat nonsense that EAxis insists on using.
@gooochyeee
So they changed it, didn't bother to check it, and now can't be bothered to fix it by simply ticking the box that was ticked and tacking it onto a patch.
This is the exact opposite of what they did to the fingernails a few years back when they added ROGender flags where their weren't any and gender-locked the nails instead of frame-locking them like it was before when it was working perfectly. At least in that instance it only took them some MONTHS to revert it, not YEARS as with this.
If EAxis reads this, y'all need to ROGender the underwear, not the briefs (as in my picture), because I assume in the game files the underwear ID puts it either before or after the briefs and that's why it's overriding the DefaultForBodyTypeMale flag on the briefs.
Honestly, how long does it take to simply open up a file, tick a box, tap save and slap it into the "next patch" folder?
We can mod here on PC/Mac but console-rs can't. We're all paying customers. It don't matter if the content was released 4 days ago or 10 years ago, it's still being sold and y'all still want us to buy it. C'mon, it's simple fixes.
