Staff said that's not doable for various reasons, including the fact a lot of bugs only manifest themselves when there are a lot of users online. Also, a lot of people would complain about the downtime, especially if it happens over a weekend.

I'm also not impressed by anyone on this thread. Staff dropped the ball hardcore on a lot of things, and I really don't like the vibe of "WE CARE MORE ABOUT THE SITE THAN ITS OWN STAFF" I'm getting from part of the userbase.

Exactly. Taking the site down to fix things doesn't bode well, cause the errors could still be there once users come back on. xD

But I agree with ya. Keith and the rest have made their explanations as clear as day.

It's like this.

Users: ugh why cant it be fixed now. why are programmers on vacation. staff dont work. ugh lets jump on the bandwagon and whine (some) lets be reasonable and complains w/ valid reasoning. attempts to provide solution

Staff: 20% of the time - XYZ happened, we implement ABC, it works fine now. 20% of the time - XYZ happened, we implement ABC, shit hit the fan, we'll try again. 30% of the time - Yes, ABC is an issue, but i havent heard of a good enough solution, so it stays that way. 30% of the time - Yes XYZ happened, ABC is an issue, overly technical explanation

...AND thats why we couldnt do A,B,C,D solution.

then back to users complaining cause they dont understand or see why it has to be overly complicated.

You're perfect

Staff regularly doesn't respond at all. Or they respond and don't follow through.

So I'm skimming through and noticing complaints about the wardrobe in particular and I honestly...think it's a good thing they're going to redo the beta wardrobe. I use the old one because every time I try to use the new one it makes my computer lag horribly after about 10 minutes, and it's just overall so weird with how it loads that I wouldn't have liked it even if it were finished. I love the old wardrobe and find it much more convenient but I will be okay if all these awful kinks get worked out in the beta one as long as the staff feels it's the best they can do. If doing it in ember is doing the best they can do, I am more than willing to wait on them. At least they're working on it.

Also coding: a comma could be out of place and the whole thing could come crashing down so people who are saying it's an easy fix, you have no idea if it is or not.

There's a bunch of things really wrong with the site but it's not like staff has to answer to any of us personally if they aren't logged in for a few days. This thread got a surprising of staff response for the main "feedback" being "I'm disappointed."

This is one of the biggest things I take issue with. Staff DOES need to answer to us when they aren't logged in for A WEEK. Six and a half days, for example, is not "a few days" it is "a few" a couple times over. Add on to that that it's not one week here and there, or a four day weekend here and there, it is over and over again and that the lack of time on site seems to significantly correlate with the lack of shit done to fix/finish things on site. It also seems to correlate with the declining site revenue as evidenced via the Daily Goal bar. THAT was my feedback. I am disappointed that, overall, it seems that all we as users hear from the staff is that "they're working on it" or that "we just don't get it" as if we've never had jobs before or we're totally uneducated or like we haven't been on site for the better part of a decade and haven't watched all of it unfold.

I never. EVER. said it should be "simple" or that there should be a ABCD explanation or fix. But, for fuck sake, NASA launches are prepared for for two years. The beta wardrobe has been beta for almost as long. IT CAN NOT BE HARDER THAN LITERAL ROCKET SCIENCE.

[edit] Anon hate, guys? really? Real grown up way to make your point/give me shit

I don't think we are necessarily entitled to hear from staff every x amount of days or to have them post every time they're logged on with a status update for everything they're working on. I of course would love to see more open dialogue with staff, but there's only so many work hours in a day and I don't think it needs to be broken up in to 3 hours of dialogue and 5 hours of actual progress, that's rather ridiculous. And I'm not sure what you could possibly expect when we do hear from them other than "It's being worked on actively (or not)" and a technical explanation. What type of communication do you want? Just responses to threads like this? That certainly isn't going to instill and confidence in the site from me, that's for sure. In the last 2 years or so, there has been a significantly increased amount of staff and user conversation, I've definitely can't see any complaints with that. Other than that the actual problem is, well, the actual problems. You've said you don't need an explanation on that so I'll leave it at that.

Tell me, have you ever programmed something, ?

Also, how many people are working on a rocket launch? Hundreds? What are their budget.

Don't compare apples and octopi

I have to say that as a new user that is apparently unfamiliar with all of these "horrible problems" you're all on about, I've been very pleased with the site since joining. Occasional lag and downtime is no big deal to me - I came from Neopets and Flight Rising, two sites that are messed up ALL THE TIME. It's just made me realize that websites are run by human beings and aren't always perfect.

Also, the beta wardrobe works fine for me? As I said, I'm brand new, so maybe there are parts of the site that aren't working right that I don't even KNOW about, but on the whole, I don't think the site is limping along as badly as some of you say it is.

Additionally, every staff member I've ever seen post seems incredibly friendly and helpful. On any other site I've ever used, the staff members don't even communicate with players at ALL, so I love that the staff here get involved in the SB and comments/forums, because it really shows that they care enough to interact with their userbase. Also, has handled the couple of tickets I've filed exceptionally well and she's awesome! :D

I just want to say that the site runs WAY better now than it did when I first started two and a half years ago. Downtime has decreased dramatically as has lag and site errors, staff communication is up (even if people still want to hear more), and while there are still ongoing revamps in a number of areas lots of the changes have been very good too. We all take issue with certain things here and there that we would prefer be handled differently, but acting as if staff doesn't positively contribute to the site simply because they aren't logged into Subeta directly 24/7 is pretty much shenanigans if you ask me. Also, any additional time dedicated to user communication by staff takes away from actual programming time. Not saying more communication isn't a good thing in some cases, but sometimes it's just going to hamper the process too. Overall, I think staff deserves way more in the way of kudos than this thread affords them.

The programmers on staff have no reason to visit the site itself other than to try to duplicate bugs that they (for whatever reason) cannot recreate on their dev servers, or to interact with users. Just because they haven't been online here does not mean they haven't done any work. It does mean they haven't communicated with any users, but sometimes there is very little to say other than the tried and true, "We're working on it," and users don't always react well to that XD

That hasn't been online in four days is not concerning to me either. The art department does most of their work off-site as well.

Staff communication is about as good as it has ever been while I've been a member. That isn't to say it's perfect -- far from it! Response times still aren't stellar, and some issues don't get public responses nearly as fast as we (as a userbase) would prefer. But publicly shaming specific staff members, trying to get them to visit Subeta more often? That feels unnecessary. Staff has grown up a lot in the past few years -- shouldn't we, too? We can be critical and constructive at the same time.

I realize this isn't the suggestions forum and is the feedback forum, but for those of you complaining about staff involvement or transparency of what they're doing all the time or whatever, I suggest you come up with a solution that would satisfy you and suggest it. That's the only way to make this criticism constructive rather than just a complaint.

If you want site features to be moved faster / code to be written and fixed faster / whatever, I think there's already adequate explanation of why that's not easy.

If you want the userbase to have a tool to know what sort of bugs are being worked on, what counts as "priority" right now, etc (I mean behind the scenes stuff, not features so nothing gets spoiled), maybe suggest a once a week / twice a month / once a month "update" in the news? I understand this would just take time out of the staff's working time and would probably be not super specific and not 100% understandable, but at least it fixes the issue of people not knowing what the staff are doing.

If you just want staff to be online more often, well, we've already determined that doesn't really mean anything other than they're not replying to threads. Honestly I think this complaint is tied to the above one, so see the fix above.

Other than that, the other complaints I hear on here are just features not working, mainly wardrobe. I believe Keith already made a very detailed topic (thank you) explaining what they've done, why it failed, and what they project to do in the future. You can't really blame them for the failure, things fail all the time in programing.

BTW I'm not necessarily saying I support all of these suggestions, I just read through the thread and heard a lot of complaining and complaining and not a lot of positive feedback of WHAT EXACTLY YOU'RE LOOKING FOR that will fix this problem. I know I personally, after reading through this whole thread, don't know exactly what you want implemented that will fix the problem of "i'm disappointed". So I thought i'd help out.

The problem is that that sort of thing should be tested for before the feature goes live. :/

I feel so forgotten...

Well said !