Or you know the rest of the site as well. Wishlists were revamped and still broken. I think forums were given up on. Achievements still don't work properly. Basic site stuff needs to work before you can tack on all the extra jazz.
Anyway back to the topic at hand, I'm not happy about the decision to remove the Saved outfits. The new "Share" feature is kinda neat I guess but I would never try on someone else's outfit. I barely change mine other than the few I have as saved and rotate between. Being forced to use the Share feature just adds like three extra steps to easily swapping out my avatar.
Headshot by
Mostly it's fixing one of the problems. I'm sure you've looked at the forum threads, the outfits were 90% of the bugs reported over the past couple of months, because they work in a really antiquated way (serialized saving of the outfit but no other data, can't be loaded outside of the current avatar) and so instead of trying to shoehorn an old system from the old wardrobe into the new one, I decided to just rewrite it and add sharing features to it.
It has the same functionality as the current outfit slots (You can click on "wear" to put on all of the clothes) it just doesn't come with the same baggage for me on the backend.
💖 ✨ 🤗
- No, I totally understand (and support) the rewrite. I think you missed what I said about the semantics of it. :P
Letting us make shared outfits private is a little different from giving us the option to share saved outfits. The former is more convoluted when you consider that the 98% of the time the system will be used to save outfits for personal use. So saved outfits really should be the priority.
As you said, there are a lot of bug reports about saved outfits, and that hasn't been addressed.

Ohh I get what you're saying. Yeah, I can make it so that they're private to start :) I also want to beef it up a little bit with tags or something, since these are unlimited and can probably get a little crazy.
💖 ✨ 🤗
I thought we were trying not to do that anymore. :x

+1! They're stored in our MongoDB database, separate from the main site, so I'll be watching and if I need to cap it, that'll be fine. Otherwise Mongo is much better at storing a bunch of json data (which is what these are) that aren't being called 24/7.
The current system meanwhile is attached to the avatars and gets pulled up any time you load an avatar :|
💖 ✨ 🤗
- It's probably easier to start with a cap and raise it later, than to let people get used to absolute freedom and then shut them down. People don't respond to that as well, as I'm sure you've seen in the past (ornaments being the most recent example).

Yeah I think starting the cap moderately high (25-30 slots? I dunno.) and raising it slowly if needed might be the better way to go. Saying that you are trying to do away with unlimited stuff, then going and turning what was originally a limited feature into a free for all is not the way to build trust or confidence in what you say. No one really needs unlimited wardrobe slots I would think anyway.
Headshot by