🚧 [BG+] Wear Costume - I'm not sure where this goes yet because I haven't decided if I'm overriding, standalone, or a mix of both. -- 2025 is the year I wrap up my PENDING Collection, right? RIGHT!
I've been obsessed with the "Wear Costume" interaction since I first encountered it some years ago but I didn't understand how to modify it back then and Sims4Me's override wasn't doing what I wanted.
My work on AXGW, Lovestruck's Costume Box BUGFIX and my Boutique eventually unraveled it.
I started overhauling this while I was working on my Boutique. It's one of many little projects that popped up back then that I need to finish. The "EnterBathing" BAND-AID I've been poking around made me look at it again.
So here's what's happening:
I am making this thing Base Game compatible.
Pack-specific costumes will be unavailable if you don't have the required pack.
I want this to work like my custom Pie Menus and Interactions, that is, it works for the Active/PC sim and on Target/NPC sims. I haven't reconfigured it yet, but the configuration works flawlessly Elsweyr, so it should work here.
I've untethered this from Holidays. It is always available in the Outfits Pie Menu. I haven't tested it on a Holiday yet to see if there's conflict, but it's currently all standalone so it shouldn't. If it does, I can fix it.
I want to add a custom interaction that quickly swaps your outfit back to whatever you were wearing or your Everyday 0 outfit. "Wear Costume" uses the hidden SITUATION outfit, this is different than how the Costume Box works - those are temporary Appearance Buffs, this replaces the SITUATION outfit.
I'm expanding the available costumes but I'm omitting some due to the way this works. "Wear Costumes" works with tags (not flags, tags - minor difference), which is great unless multiple CAS item swatches use the same tag, then the costume will randomize with mismatched colors and we're back to looking like clownies. As I do more CAS Overrides it might be possible for me to fine-tune this if I can define custom tags but I don't want this to rely on separate CAS Overrides. I might do to this what I intend to do to the Lovestruck Costume Box BUGFIX, which is include MERGED CAS Overrides specific to this release so it's an All-in-One thing, because there are some nice costumes I'm being forced to omit due to the clowning, like the damned Day of the Dead Walkby costume! I want it!
If adding and removing CAS item tags didn't require overriding CAS items with custom tags, this is how my Boutique would work. It's so bloody simple, but of course, as with everything CAS-related, EAxis has made a giant mess of these tags. There are Hot Dog outfits all over the place, in tags they don't belong in. What the !@#$? Why?!
Also, "Wear Costume" suffers from the same RESTRICT OPPOSITE GENDER nonsense that the Lovestuck Costume Box suffers from. If I don't fix !@#$ from both sides, it ain't gon' work properly! !@#$'s sake! I don't understand HOW this game is such a mess. Simple !@#$ is the root cause of so much BS! I'M SORRY! PARTFLAGS IS MY SHTI- I have many shticks now but it began with PartFlags.
This is part of my Outfits PiMP Override, but it requires a lot of coding so it's getting it's own post. It's not terribly difficult coding, it's just a lot of it.
TBC...
BUT WAIT!
DID YOU KNOW THAT WE CAN DO CUSTOM INTERACTIONS WITHOUT THE USE OF TS4SCRIPT OR XML INJECTOR?!
I should double check it actually works by itself before claiming I can do something I was lead to believe we couldn't do... BUT I GON' CLAIM IT ANYWAY! I !@#$ING DID IT! <CACKLES MANIACALLY> 😹
It's a claim because while it's not configured to use XML Injector, XML Injector is in my Mods folder and I need to verify before I make an arse of myself.
If it is working on it's own, it still requires modifying a specific handful of Tuning resources to add the custom interactions - on the bright side, these Tuning resources don't flag sims as "modded".
The issue of course is if more creators adopted this, which I doubt they would, the end-user would have to manually "merge" the custom entries because creators are unnecessarily weird about things. XML Injector / TS4SCRIPT is more end-user friendly when looking at it from this angle, except for the obvious MALWARE concerns - everyone wants to compile their PYTHON code and expect you to just "trust me bro". 😾😹
This requires more testing, but if it actually works the way I'm claiming it does and those specific Tuning resources are versatile enough to not LastException for missing custom interactions, then I think I will try it out on my other projects that currently rely on XML Injector, including AXGW, Lovestruck's Costume Box BUGFIX, and my unreleased work-in-progress custom Pie Menus.
I have nothing against XML Injector, but SCUMBUMBO ain't with us no more and I don't trust any bros that much. 💀
I'm totes not trying to make "WW Lite" because I don't trust WW! Totes not! What possible reason would you have to think that besides me planting that thought in your mind. 😹