So, about that hair salon...
Filter
Show Official Posts OnlyReplies
I remember making a post or several about it months ago pertaining to hoping the hex code input returns. (Among other users also mentioning wanting it back.)
Any news on that particular front or...?
I have no idea where to put this topic at this point either. Apologies.
I barely use my wardrobe anymore because of this. All those hairs (basically almost all of the redeemable hairs Subeta has made) feel worthless now. Seriously regretting redeeming them because I can't comfortably use them without the hex codes and I never would've thought those would go away. D:
Keith posted on tumblr about some kind of wardrobe update, but it was really vague (and didn't mention the salon). I hope this means he's going to start work on it again, because I've pretty much given up on using it since they dropped the ball again last year.
I'm terrified it means we'll see a wardrobe v4 though.
At this point, I'd be happy just being able to click on the color wall and have it actually work. I can't change -anything- in the hair salon. Hex code input by now is nothing but a far off dream.
Let us all dream of hex codes and proper redeem-colorations. So nice.
I would very much like to be able to click on a different color on the damned color wheel to change my hair color!
A v4 wardrobe. The stuff of nightmares...
Gods I miss my hex codes. I've also noticed that the newer items aren't being assigned colors for color matching anymore. Haven't been for a while. Then there's the no-nose issue on the shared HAs when you load them again. And you can't use any of your save slots that you paid money for. And you can't rely on the share HA feature anymore because it's broken. And all those hairs in the Hair Salon you paid for are basically useless because you can't add your own hex codes and clicking the right shade is ridiculously difficult. I find myself more and more regretting paying for a lot of things on subeta.
tbh at this point I wish they'd just let us remove our wigs from the salon At least then the hair would get some use 😭
all or nothing, it's written in blood.
There was a time when I was almost never using normal wigs because the hair salon & redeemable wigs were so convenient and customizable.
Oh my god! I hadn't thought of that, what a nightmare.
I&;ve also noticed that the newer items aren&;t being assigned colors for color matching anymore. Haven&;t been for a while.
Then there&;s the no-nose issue on the shared HAs when you load them again.
And you can&;t use any of your save slots that you paid money for.
And you can&;t rely on the share HA feature anymore because it&;s broken.
And all those hairs in the Hair Salon you paid for are basically useless because you can&;t add your own hex codes and clicking the right shade is ridiculously difficult.
I find myself more and more regretting paying for a lot of things on subeta.
In addition, shared avatars have updates applied to them that they shouldn't. Meaning, if you save an actual HUMAN avatar, then put a zapper skin on your current avatar, you will also get the zapper skin on your shared avatars. This honestly deters me from using zapper/zombie skins. :/ I think it's the same deal with salon hairs being applied to shared avatars but I'm not sure. Which if it is the case then that's another reason I don't use salon hairs. But I'm mostly irritated with the no-nose on the shared avatars. If it wasn't obvious I would really really like to use shared avatars to their full potential but all of this makes it very difficult.
he/him / 31 / EST |  | My best friend is |
Yes, the Salon (and the wardrobe to a lesser extent) is in a sad state at the moment ?. There are more long blog posts coming, but this is my priority.
I wouldn't call it a wardrobe 4.0, because it's using a lot of the same components as the 3.0 for the front end. What's really being shifted is the back end, which can be explained as:
- The /wapi.php API that was built on top of the old avatar system. Slow loading of items, loads them to a mongoDB for caching, just incredibly resource intensive.
- /slib/ which is the old avatar system, and builds the avatars themselves. Thousands of lines of code that are now just powering the avatar system
- The database structure from 7+ years ago, that has serialized variables (not the right practice anymore) that have to be turned to strings, then turned to JSON for the wapi.php controllers.
What I'm doing now is rebuilding those pieces. I'm replacing our home-made framework in /slib/ with Laravel, a battle-tested php framework. This will also set the base for more amazing API calls in the future to make the site faster (which I'm really excited for).
Secondly, I'm replacing the thing that renders the avatar, which is the /slib/avatar.php system. It's over 750 lines of code, brings in tons of classes, and means that when or I want to add a new feature like shared avatars, it's a heavy lift that takes a week. I was able to implement my avatar in a new system in 70 lines of code, with ease of adding new features (hair isn't included).
I have all of the tasks for "feature parity" on these worked out, and there is a real timeline that has been kept up so far internally.
I know there is MASSIVE FATIGUE for posts like this, with "working on an entirely new system!" especially after the last wardrobe rewrite (which was actually technically pushed on us faster than we'd have liked because of the XML changes) but this time it's be doing right. Tests are being written, timelines have been decided and being stuck to.
💖 ✨ 🤗
yep. there are several that i would use if i could just plop them on my head without the hassle of trying to select the right freaking color on a small color grid. >.>
[edit] whoops, should have refreshed before i posted. while i know it's frustrating for us, i can imagine it's also frustrating for staff as well. thanks for the post. it's nice to hear back from staff every now and then to see this kind of thing is being worked on. it's also super nice to see much newer and more current means are being used to code the new parts of the site!
It's always a real tossup. When developing the v3 wardrobe it seemed like the best past forward to use the older codebase as the framework, and it just ended up not really working well or being great planning. It got something out of the door quicker than otherwise, but just wasn't good planning :|
💖 ✨ 🤗
- It's good to see that something is being done with the wardrobe, but your focus on the back-end doesn't really address most of the issues people complain about. Cleaning up code is cool, and speed improvements would certainly be a plus, but I rarely see people complain about these things.
In this thread specifically, people are clamoring for a way to use hex codes on salon hair, but you didn't talk about that at all. If you're still using the old back-end for the current wardrobe, why did we lose the ability to use hex codes? Isn't that just a matter of giving us an input field, which is mostly a front-end fix if the old code is still in use behind the scenes. (And I know the current color picker submits hex codes, so it should absolutely work.)
I've posted a huge list of wardrobe issues before, and the majority of them seem to be front-end, which is why they're so bothersome for us players. Personally, I'd like to see these fixed first, before you delve into the back-end for speed improvements and things. Otherwise nothing really changes on our end and the wardrobe continues to be a usability nightmare, as it has been since release.
The front end is also being changed, in tandem. There needs to be changes to the way that it grabs information - which is what is going to resolve a lot of what you're asking for in that thread.
The majority of those items on your list seem like front end problems, but they're all tied to the way that the avatars are stored on the backend and the sort of hacky fixes I had to make to make them display in the new front end. This is resolved with a backend designed for a new system, and an API that makes it easy to change the items. Things like the shared items, way that items are listed, etc, are all back end storage issues.
The hex value isn't as simple as adding an input, and that was actually there at some stage of the wardrobe testing. It interfered with the color picker and the choice I made then is that more users will get benefit from the color picker vs just an input to put in a hex code. Like I said, we were running out of time before the wardrobe became unusable in updated versions of modern browser. Instead of going back and making more hacky changes to that front end, I'm spending my time on something a lot more valuable and useful going forward.
💖 ✨ 🤗
- So I understand why the salon wasn't finished before v3 was made live, but why is it still being put off in favor of back-end fixes? You say the hex codes were interfering with the color picker, which still sounds like a front-end problem, and it's something that will still need to be addressed eventually.
If you moved it up on your schedule and fixed it now, you'd make a lot of people very happy right away. And it doesn't need to be a "hack", because there's no immediate need to change how the back-end handles the hex codes we're already submitting via color-picker, right?
So, confirmed that we're waiting for another wardrobe instead of changes to the current one?
I really miss hex codes.
RIP Mom, I love & miss you more than you know. Tell Dede hi.
Ocean Conservation Namibia on YouTube... they do good work! https://www.ocnamibia.org