With all due respect, could you please provide sources for your claims? I want to believe you, but you need proof. Specifically, I’m referring to these statements.
Only someone who works at Roblox could know this. IMO it isn’t right for a report to be unresolved without any communication from the team for over a year regardless of workload.
I believe Roblox’s last Make-A-Wish, Hallows Valk, is still accessible, so I don’t know where you’re getting this information.
Last public Make-A-Wish, this bug report is an example of Roblox’s ability to remove catalog pages for hidden/private assets, andnthe make-a-wish items most likely fall under this.
I’m speaking based on what I’ve observed from public sources. For example staff members like Klaugrana001 responding/most likely being assigned to catalog asset bug reports (1, 2), and MisoPonyo is a 3D generalist as noted in one of the Roblox Level Up videos. They most likely work on asset bugs due to their skill set and Roblox groups. We also know that there are most likely not engineers handling 3D art assets, as there are most likely dedicated artists that are not part of the engineering force. I also generalized a bit; if a catalog bug was related to rendering or the website, an engineer from those teams would be most likely assigned to the issue. My conclusion could be wrong, but I believe that there being dedicated artists that handle bugs like these are the most likely case scenario
I see your point, but your reasoning is merely based off of speculation without any official statements as you said. Even though Roblox has the ability to hide accessories, this hasn’t been confirmed to be used on any Make-A-Wish items AFAIK (appeals to ignorance fallacy). Also, we don’t know Klaugrana001’s exact job position, and MisoPonyo was last seen on the forum in 2022. However, I do acknowledge that you could be right.
@Hooksmith Out of curiosity, has anything happened in response to this feature request? I just wanted to follow up because it’s been a week since this request was filed. Thanks again!
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.
I agree, I don’t appreciate the radio silence, pretending to ignore the problem and hoping that we will go away just isn’t appropriate.
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.
Staff will follow up regarding the skimmers.
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.
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!
This. My reports in this category have been abandoned for over a year (1, 2, 3, 4), marked as “Closed” without being fixed (1, 2), or even mistaken for a feature request by staff and completely locked.
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.
If this is the case, then it really doesn’t make sense that the Kitty Ears were fixed so quickly. They’ve been on the catalog since 2008.
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.
