So right now I'm mostly moving toward getting rid of the saved outfits feature entirely and moving it to the "shared" outfits (with the option to make them private).

Reasoning: That is in a separate table and makes it easy to save things like the base state, and the salon hair state. It's not as easy to do with the current saved outfits feature because they're saved as a part of your current avatar (aka if you change your base, it'll change in all of your outfits, or salon hair).

So - one way or another this will happen. :)

We'll just refund people who've paid for slots :)

And the posting from outfits was removed a bit ago.

[edit]

The systems are entirely different.

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.

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.

+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 :|