Could you please check if this category still covers issues with accessories in terms of aesthetics? The reason why I ask: I recently saw this post on a report by a member of the team which states,“…we won’t be making any aesthetic changes”. Like the situation with gears, I fear this will set a precedent that will jeopardize similar reports such as this report about asymmetry with the Summer Valk. Currently, the category’s description states,”This category is for reporting issues with…Roblox-created catalog assets on the Marketplace…” Although examples of issues that are applicable to the category are provided, this statement is vague and makes it appear that both technical and aesthetic issues can be reported (as no limitations are stated). If aesthetic issues with accessories are no longer going to be considered, then the category’s description should state this.
Hooksmith, I really appreciate and respect you because you seem to care about this feature request despite not being directly responsible for this category to my knowledge. I think it would be very appropriate and professional if the team who is responsible for this category directly acknowledged and addressed this request. It has been over 2 weeks now which is plenty of time for this to have been reviewed and considered. I’m very eager and hope to see something happen soon!
Also, are issues with an accessory’s position considered obsolete due to the planned revamp to the Avatar Editor for custom positioning, scaling, and rotating of accessories? You might remember that I first voiced this concern with this post in “The Big Bug Reporting Update”. My report about the Timeless Valkyrie Helm’s position was closed for this reason. I feel that it would be nice to know which types of issues (e.g., aesthetic, gears, and position) with catalog assets are considered obsolete before I make a report. These are important questions that need to be answered because the response to each of them will set a precedent that will impact the state of similar reports in the category.
If this is a problem, I would suggest stating in the category’s description that it’s a requirement to own the asset in order to report issues with it. I feel that most users (including myself) report issues with a catalog asset whenever they see them regardless if they own the item or not.
Even if it isn’t owned, the model asset can be used in games to increase the visual fidelity of the game or to make cool NPC armor and things like that. These are bugs, and they need to be fixed.
I was nice at the start of making this request, but I’m going to be very frank after waiting for a month now. I’m very disappointed; The lack of response to my questions and this request is unacceptable and embarrassing. I hope some higher-ups have seen this request.
I’m afraid that this request was immediately disregarded as “low impact” even though I mentioned precedents that have been possibly set that will impact reports in the category. Users are wasting their time and the team’s time by reporting issues that are considered obsolete. I hope that those precedents have genuine reasons to support them and aren’t just phony excuses to close reports in order to reduce the backlog (doing this just looks lazy).
Overall, I’m very concerned by incompetence. From seeing the backlog, it’s obvious that there are issues with the handling of these reports. I understand that high impact issues are often prioritized over low impact issues; However, I think there should be a decent balance between triaging both. As minor issues build up over time, addressing them will only become more overwhelming. Additionally, the lack of response to my questions and this request explains a lot about the current condition of the category. If a well written request can’t even be answered in a timely manner (i.e., 1-2 weeks), then how can it be expected that the backlog of reports in the category will be eventually addressed?
Hooksmith has done all he can do. It’s the team(s) assigned to the category turn to acknowledge this request and make improvements for the better.
As a side note, isn’t it ironic that the criticism in this request hasn’t been addressed? It appears that the team(s) involved with this category dislike criticism. Let’s be open to criticism and not be stubborn. Don’t be scared of me, I just want answers.
Hi. I’m getting caught up on this particular thread and will help get the right people in the conversation as well.
Just to provide some internal context, as much as I can.
There’s definitely no internal effort to try and silence any criticism or not address it. Nor is there any attempt to ignore it and hope it goes away.
To my knowledge there’s also not been any explicit de-prioritizing of any category of bugs or feedback.
There’s been a lot of growth at the company that in some cases has complicated ownership and processes around various reporting channels. Just growing pain stuff, not intentional.
I can very much appreciate that it’s frustrating in addition to having bad optics, but we don’t take that lightly and are focused on trying to make the whole platform and ecosystem better wherever we can.
There’s a lot of disparate asset types at this point in time and some of those have some deep roots in various systems across the platform, so it’s not always trivial or even straightforward to resolve some bugs, especially if it involves data structures or other functionality exposed to devs or is tied to other internal functionality that would hurt backwards compatibility (again, speaking generally in case that context is helpful to understand why some things seemingly take forever).
All of that being said, I’m sorry this has been frustrating for you and we do appreciate the honesty.
I really appreciate the transparency in your response, but will staff follow up soon? I believe the handling of this category will become more efficient if the issues mentioned in this thread are addressed. Currently, this response appears to be all talk, no action because it’s been almost a month since a follow up(s) from staff was promised. I hope this is being actively discussed internally, and that’s why there hasn’t been a response yet.
Just to reiterate, here are the main questions that I have besides the problems mentioned in the OP.
Does this category still cover issues with accessories in terms of aesthetics?
Are issues with an accessory’s position considered obsolete due to the planned revamp to the Avatar Editor for custom positioning, scaling, and rotating of accessories?
Is it a requirement to own the catalog asset in order to report issues with it?
It’s been over 2 months since my last reply, and staff have yet to provide a follow up or update on this request. Although the staff member who last posted on this thread seemed to have good intentions, it appears that they’re inactive on the forum. Can I please receive an update on this request?
Just to confirm, some of the issues that were mentioned in the OP are still occurring. For example, this report about the incorrect naming of specific accessories is currently marked as “Fixed” despite the names still being incorrect. This has been pointed out on that report, but staff haven’t followed up yet.
Also, when can we expect old reports in this category to be addressed? Right now, it appears that only new reports are being addressed. As Alpkurt2 said, some of these old reports have a decent impact. These old reports aren’t going to fix themselves.
Recently, I noticed another issue with the handling of reports in the category: Some reports are being marked as “Closed” without any communication or fix (1, 2, 3). The handling of the category still isn’t very efficient. Since 5-23-24, the total number of unresolved bug reports in the category has risen from approximately 110 to 176 (a 60% increase). I hope to see improvement soon!
Yes, this actually happened when I reported the deletion of a free shirt item uploaded by Roblox themselves for the Coco event in 2017. This is the response I received:
This was around the time Roblox began hiding the Catalog pages of moderated assets, so I can see how there could be confusion with locating an asset that is no longer visible. Still, in the event that I do have to make a report for the deletion of a Roblox-created item, is Catalog Asset Bugs the right place?
@Hooksmith and @PerfectlyCromulent Could one of you please give me an update on this feature request? I don’t understand why it isn’t being prioritized. These issues are definitely impactful because multiple users have voiced their bad experiences with the category and several reports affected by poor handling have been mentioned.
On a side note, how does the specific team(s) that is assigned to this category prioritize reports?
The reason why I ask: A report for the Kitty Ears was recently addressed. It doesn’t make sense that they were prioritized over other older reports in the backlog because the report was relatively new and a low impact issue. Don’t get me wrong, it wasn’t a bad thing that the team fixed them.
Just a quick 2c: note from the other thread I told you that impact/effort make up the two main factors of prioritizing issues. There’s a “context switch” needed when you work on something that hasn’t been touched for a while vs. something you touched recently. This can impact the effort needed to address an issue and so it might be trivial for someone to quickly fix something on an item they recently worked on vs. finding all the files and context about an item made ages ago.
If it’s hard to find the source files of assets, then it’s safe to assume Roblox internally is under disarray, deplorable in my opinion, and should suggest serious internal restructuring.
This does not feel like you properly understood the spirit of my post above.
Context switching is always difficult for older works, try thinking about how much effort it takes you to work on a year-old Roblox project vs one you worked on yesterday.
I was answering your concern about older vs newer reports in the general sense. I don’t know the whole story about each catalog item published by Roblox.
I’m happy to report that I’ve seen the handling of this category significantly improve during the recent months: More reports are being resolved , gears are starting to be fixed, and mass criticism is being addressed.
The main problems that remain are reports in the backlog aren’t being addressed, issues that can’t be fixed aren’t stated in the category’s description (1, 2), and lack of quality control testing. As I’ve stated previously, it seems that mainly new reports are being resolved. I feel that it’s important for old reports to not be overlooked (especially, considering that most of them are of similar or greater impact). Most of these new reports seem to be about trivial issues with old accessories. Maybe, this problem is due to prioritization not being optimized. I understand that it’s probably more difficult to prioritize due to the recent influx of reports caused by YouTuber coverage of the category.
I’m making this reply to support the OP! “Second this!” (as they say)
When this feature request was made and published by the OP, I read the replies of each forum user and I was not expecting that there would be some problems regarding prioritization. When I read @PerfectlyCromulent’s response, I understood that there are some problems with ownerships between these channels and they are trying their best to fix for the better for the company, which is comprehensive as everything has its ups and downs, but always looking forward to seeing a bright future.
However, we are talking about a response from 6 months and 20 days… You might think everything is good because it’s almost a year and everything should have been changed, right? From my perspective, the handling system of #bug-reports:catalog-asset-bugs remains imperfect. Even worse, the communication is odd.
Exhibit A:
The “Astronaut Helmet” had problems with its texture and model when it was published. It was eventually fixed but remained with a bit of a problem analyzing the new version. The person who addressed the fix allowed me to ask if there were any questions or concerns, and so I used it. To my surprise, the person never replied… They did the same thing for other bug reports:
Since December of 2024 (last year), the number of bug reports regarding problems with assets that are in the Roblox Marketplace (previously called “Catalog” and “Avatar Shop”) grew and it seems that the team that has to deal with these problems seems to be overwhelmed. If you were to do an “investigation”, you might encounter two situations:
QA Testers analyze and submit a ticket for the team. Then, after some days, the status changes from “Open” to “Closed” without any response.
No tickets are submitted, but, after some days, they close the report.
Roblox gears. According to researches, they were published back in 16 years ago with the simple purpose of being sold and used in-game. They have been used for Roblox experiences via gamepasses + to projects that depend on them to make their in-game content entertaining for the targetted audience. As Roblox released new technologies, most of them started to break and couldn’t be used any longer.
In November 2023, a user reported a bug regarding the visuals of the gear “Dual Illumina - Roblox” when wearing into your Roblox avatar. One of the swords was not attached to the left hand. The problem was not fixed because they no longer support nor intend to fix those that could be made or already exist in the Marketplace:
After the same user reported that other gears were broken regarding the visuals in their Roblox avatars, the person who addressed the previous fixes declined this request. This is now hypocrisy.
This whole situation is a mess and no matter how much the OP points out this problem, it looks like they are being ghosted and/or this feedback is not being taken seriously whatsoever. I suppose you can say that this message below is now an irony:
Now, I’m not sure how this team will review my comment, my thoughts about this, whether receiving a hateful reply or anything else similar, however, one thing is certain, ghosting and not addressing things properly is not professional.
From what I can remember, the catalog team is fairly small compared to what it used to be.
Recently the forum has had almost a double or triple increase in activity, so it’s understandable why some things may be on the back burner compared to others. While I do believe that sometimes there is a lack of following up in the channel or responding to stuff still not working properly, it’s understandable that it takes them a while to assess changes on items with more prominent backgrounds, like the Workclock headphones, for example and that there may be more critical or important things they need to do before touching an item again.
The team tries their best, and they’ve pushed a lot of good out. Like Proven Right has said in this post it would be nice if stuff like the stance on gears would be clarified permanently It would benefit both People reporting and the people who work hard to fix these bugs
I’d like to add that in my experience the issues of #bug-reports:catalog-asset-bugs isn’t solely based in how Roblox staff handle these reports. Since “The Big Bug Reporting Update” as you called it, there have been a number of users commenting on bug reports about inconsistencies in assets, shading errors, placement issues, and the like as if they should not be handled as bugs.
Personally I have seen these arguments made and posted multiple times on bug-reports of this nature:
“This shouldn’t be fixed because I enjoy the bug that is being reported.”
While yes, I think it’s important to recognize that many users have come to expect these assets in their current “bugged” forms, I also think its important to realize that many of these items weren’t always like this. I understand that due to the recent incident with the WCHPs people are up in arms about changes being made to their beloved items, but not every situation is directly comparable to this. Please use your due diligence and critical thinking.
“This goes against the history of Roblox” (Refactor of argument 1).
Many of the bug-reports I see this on are actually attempting to restore items to their classic appearance, rather than how they looked when Roblox modified shading, textures, and some other things. A good example of this would be the Banded Top Hat series as discussed Here.
“I don’t like the proposed fix to this bug, so I don’t think it should be considered a bug.”
This is counter-productive. If you have a better fix please describe it.
“There are other bugs that deserve more immediate attention.”
Again, this is counter-productive. The goal of the #bug-reports forum should be reporting ALL bugs, not just those that are the most pressing. If you know of an immediate threat to Roblox security, please make a report on it or go through the HackerOne process.
I don’t see many of these comments under bug-reports getting flagged as that section seems to be used more as a general discussion of the bug and solutions to it. I think this is good, but as a rule of thumb please limit your criticism to what is constructive.
I’m not sure to what extent this has an effect on staff taking these reports on, but since at the end of the day we are all human I think it’s safe to say that it is present to some degree. Please be respectful of your fellow bug-reporters and Roblox staff alike.
