Letting us know that it is happening to you is fine, but there are threads where users will post daily (or multiple times a day) and each post gets angrier and angrier without providing any information. That quickly makes a thread really long for no reason and often times we know it is happening (the MMs) and we want it fixed but we are waiting for someone to be on to do so. It is much better to post something like, "this is still happening and here is when it happened, what browser it happened on and the error I received". It really is a matter of it being difficult to wade through the spammy things to find the actual problem because sometimes that problem is not even explained in the first post so the MMs and the programmers have trouble finding it.

Okay I was about to say that I also post on bug threads to add that whatever bug is happening to me too. I feel that it not only lets staff know that the problem is more widespread than the person that reported it and gives a shameless bump to the topic. Shameless because bugs are annoying and I shouldn't have to feel bad that this really super irritating bug is now on page 2 and will probably be forgotten about now so I bump it back to page one so maybe, just maybe, it will be fixed.

To be honest I'm just glad that backseat moderation is allowed here. On another forum I go on you can get in trouble for basically doing something that a moderator should have done, even simple things like telling someone that there's a thread for something already and redirecting them. The mod edits your post and it says [MODERATOR: backseat moderation] or something stupid like that.

I enjoy helping out on the problems and bugs forum, whether the MMs there have noticed my presence or not idk lol, I just like helping redirecting duplicate threads to the proper one or maybe telling people that something isn't a bug and that something just changed. At that point all Destiny and Reya have to do is swoop in and lock the thread and move it to dismissed which I feel is pretty helpful because then they can spend time addressing the other bugs instead of having to deal with duplicate threads because somehow people lose the ability to read once they enter P&B and end up making a thread for a problem that is literally on the first page already.....

Yeah, I also occasionally jump on a P&B topic to let the OP know it's not a bug / how to fix it / open a ticket / maybe even tell them to go to the appropriate topic xD I never even considered that could be a potential issue, imo it's just users helping users (who get their answer quicker) and MMs (who only have to lock it afterwards). At least within Subeta's smallish userbase, it thankfully tends to work well ^-^; I dont even want to imagine people getting in trouble for giving actual good / well intentioned advice asdjskd SO happy it isnt a thing!!

Aah thank you for the clarification! That makes sense, angry repeats of the same report (especially within small time frames, like everyday) won't make the issue get solved faster and help no one.

I have this feeling that sometimes people are a bit scared of posting on P&B when they see "it has already been reported", but, on the other hand, I suspect a bug topic that barely has a couple posts could strike people as "smaller bug" or possibly get lost among other threads :c

i kinda wish we could vote/like/support a thread in the bugs and problem forum. Then perhaps the P&B forum can be ranked that way (or just the top 5-10, so that new topics dont get drowned out). That way we can see whats "important" in the sense of how many people are facing this issue/want a fix, and removes the spam fillers.

Im not sure if moderators have access to these things, but perhaps if something is on a development queue, if you could add that in, that would be great. This is different that just letting the programmers know. Since they might acknowledge the problem, but not actually have enough incentive to dedicate time towards fixing it yet.

I'll admit, if I post a bug thread, I do ping programmers and keith, only because then it actually gets fixed. Even before I would ping them, I would sit and wait weeks, then see 1 person ping programmers or keith and it's fixed before the end of the day. So why can't we ping staff that can fix the issue?

For what it's worth I think the amount of QoL updates and updates in general that have been going on lately is nothing short of amazing. It's been fantastic to see so much work going in to the site that's plain for everyone to see. Though there are obviously still and always going to be people who complain because on certain thing still isn't fixxed, Overall the site is getting better and better especially in the last month or two.

Very low impact to you does not make it meaningless to your userbase. As far as I can see, the forum is not so active as to be prohibitive for the programmers to check on them at least every couple days, if not daily. The lack of response is obviously disheartening to not only the users, but also the staff who is playing middleman. This isn't something that is being brought up for the first time and it shouldn't be a surprise that users are upset.

I think you might have mis-read his post, he said low impact as in a relatively small amount of users being impacted in a relatively small way. A minor inconvenience is a minor inconvenience and unless it's something that's blatantly obvious and will only take a few minutes to fix at most, should be put at the end of the list. And obviously he and the other programmers do read the forums, fairly often even, but the system they have in place means that it's not their job to peruse the forums for bugs to fix, instead it's their job to fix the bugs, which makes a hell of a lot more sense. They're the only ones who CAN do those things, I'd really rather they not waste their potential bug fixing time on reading user complaints that are already being read and made note of by the people who's job it is to do so...

They clearly have a system in place and quite frankly I think it's working just fine... Bug fixes take time, they need to find the source and then find a solution for it, don't expect instant results because you noticed some small thing and posted about it right away, that's not how anything works, ever.

- Your post here is incredibly helpful! Can it please replace Keith's thread and remain as the permanent first thread in Problems & Bugs?

Also, to you or anyone else working on these things - It would be really, really helpful to have a forum search back. A lot of times, I do go to Google to try to find my Subeta problems, but it only brings up really old threads, like 2011/2012, when I know that there are more recent threads.

I'm not sure how average price hovers being inaccurate for many months or priced(but unbuyable) gallery items showing up in shop search and impacting autopricing are impacting a relatively small amount of users in a relatively small way.

Well neither of those problems have any real impact on the site, average price hovers are just a novelty more than anything, they don't decide the future value of items (and by the way they currently work just not in the same way as they used to). And priced unbuyable items is no different than unpriced unbuyable items, and special note is made on the shop page of items being priced higher than 50m, right at the top. I'm sure these were just two examples, but my point is that they have different criteria than some people might prefer when they rank things, but they are doing a shit ton of work as of late. There's no use in complaining because you don't like their precedence and if they have to stop to reply or explain, they're wasting time that could be used solving the problems that people are complaining about.

I just want to throw out here that if anyone has any suggestions, ideas, comments, or questions regarding the P&B forum, you are more than welcome (and encouraged) to contact and myself. :)

We have been trying a lot of different things to keep the forum organized and up-to-date for users.

Your post on the first page (56264110) is really informative! That should be at the top of the P&B forums...really. It's more helpful than keith's 'Reporting a bug- READ THIS FIRST' topic (no offense, Keith). I see so many topics titled "huh?" or "What in the world is this...?" and you have to open them to find out what it is.

I get really frustrated sometimes like everyone else, but I think that you and Reya are doing an excellent job, especially with the kind of limited power you ladies have.

I think the one thing I hate about the p&b Forum is that you don't know if your problem is still on a list.

I had a board that I made about the beanbags and quickly replied and said she'd let someone know. It took a month before it got fixed. I had to have someone bump it for me because honestly the lack of communication made me wonder if anyone actually cared still. Obviously some bugs are more important - but I think once a week you and going though and just going "This is still on the list to be looked at" would be amazing. Because for the one feature I still use on site (Beanbags) having that broken and zero communication was nearly enough to make me leave because if that doesn't work what am I sticking around for, ya know?

I love this post.

This is actually something we've been trying to do so that even the programmers can be updated (though it's usually closer to monthly). I do apologize that we haven't completely kept up with it.

I know it's not an all-inclusive list, but this is a list of known bugs: 🌟 Known Errors List - 11/9/14

I have also been trying to use the Known Bugs Sub-Forum some more so you know what has been reported.

I guess if it seems like something not many people are having issues with, I'll refrain from posting and pinging people about it. Sorry! I just know usually pinging the programmer group has usually helped get the issue solved for me. xD

See thats good and half the time I don't read either of those threads - but I think the bonus to someone popping in even twice a week to go "This is still on the to-do list" might bring more users who have the problem with MORE information that could help, ya know?

I totally understand, which is why we've been trying to stay on top of it. It just can be difficult with the number of existing and incoming bugs. Especially when we do try and followup with the users and they just never respond, even when they are active and making other reports (and then finding out it was user error, haha)...

And it's not that we don't want users to post that they are also having trouble with an issue, it's all about the method. They just need to include more information. :o