I have the issue that everytime i publish an update to my assets (scripts), they get moderated for “Misusing Roblox Systems”, and when i request an appeal it sometimes gets accepted, sometimes denied. If it gets accepted my assets stay online until i publish the next update to them (or publish the same again without any changes). My assets are getting moderated since November 4, before that everything was fine. And if there is actually something wrong with my assets then please tell me.
Hey, thanks for reporting and sorry for the troubles. We recommend appealing the asset(s) for now for approval. We’ve alerted the team of the issue and are working towards a fix in our systems
Thanks this is good to hear, bc this moderation issue annoys me i even had to stop making updates for them so they not unavailable for other people. Is this actually a moderation issue or do my assets actually have smth that is not allowed?
No wonder some of my games are getting broken, randomly getting an asset distribution disabled would break them, (some of their core functionality is in a main module that auto updates)
It might have something to do with ModuleScripts, it appears most models with ModuleScript get flagged for “Misusing Roblox Systems”, whether or not require is used
well, if it’s not the entire problem it’s at least part of it. that we can say because everything I upload with ModuleScripts, regardless of if they use require at all (they also comply with what is listed on the Best Practices) gets flagged for this
When is this issue gonna be fixed? The Moderation issue is still there, if this issue can’t be fixed or smth ig i will upload a backup module in case one gets offsaled.
I’m also enjoying that this topic is still up to also let you acknowledge a similar issue with my resource here.
I think the toolbox’s automatic moderation completely blocks behaviours that may be related to the “obfuscating” functions such as getfenv(), setfenv(), etc… This finally causes completely innocent practices, such as:
Name = Value
-- INSTEAD OF
local Name = Value
to trigger the moderation (similar to getfenv()[Name] = Value). My resource is a mod of some 11 years old building tools with thousands of lines, and getting rid of this behaviour is extremely long and disruptive for the people who use my mod.
Appeals indeed work, but it’s just impossible for me to pull updates without waiting hours (heck, even days on the weekends) to fix a single bug.
I would please really like to get more details on the other elements that can cause the flags to happen while a fix is being worked on to provide a policy-compliant version of my resource. I’m in a dead end right now, and I can’t just force everyone to install a file each day for a mere fix.
I think I’ve found part of the issue here. It seems that the automatic moderation system is being overly aggressive with ModuleScripts, flagging them even when they comply with best practices. This could be due to the complexity of the system and its tendency to misinterpret innocent code patterns.
One common issue with this approach is that it can lead to false positives, where assets are flagged unnecessarily. In your case, you’ve mentioned that one of your assets doesn’t use require or ModuleScript, but still gets flagged for “Misusing Roblox Systems”.
To provide more context, I’ve looked at the two assets you linked and they seem to be following best practices. However, it’s possible that there are other factors at play here.
Regarding the appeal process, I’ve noticed that some users have reported inconsistent results when appealing their moderated assets. This could be due to a variety of reasons, including changes in moderation policies or issues with the appeal system itself.
In terms of redistributing your module back to public, you might want to try uploading a new version and then appealing again. However, I understand that this can be time-consuming, especially if you’re waiting hours or days for updates.
It would be great to get more details on the other elements that can cause flags to happen while a fix is being worked on. This could help us better understand the issue and provide a policy-compliant version of your resource.
i cant appeal my model because there is only 1 thing that is shown on the screen happened on august 10 2025
also i noticed assets containing require() started to get disabled without any id attached on it
what do i do now? if i contact roblox support, it will be time consuming
(edit: no new appeals are showing up but content distribution disabled still show up on inbox)
