Automated moderation false flags the script `print("require")` as violating community standards

Bug Reports Creator Hub (create.roblox.com) Bugs
1

This automated system flags any content that may obscure engine features, such as getfenv and setfenv, script execution, including Custom Lua Virtual Machines, and the requirement of remote assets. The solution Roblox used was to moderate require(assetId), loadstring, InsertService:LoadAsset(), and ModuleScript.LinkedSource.

According to the Roblox Community Standards and the Creator Store requirements, one of the restrictions in scripts that are allowed to be distributed on the Creator Store is that you cannot have in a script require(assetId).

However, this is now different. If I uploaded a script to the Creator Store and made it public with this content:

print("require")

it should pass the content moderation system; however, it does NOT anymore.

Reproduction

  1. Open Roblox Studio
  2. Create a Script or ModuleScript in the Explorer (it can be anywhere, Workspace for example)
  3. Enter these contents into the script:
print("require")
  1. Right click the script in the Explorer
  2. Mouse over “Save / Export”
  3. Click on “Save to Roblox…”
  4. Select the Asset Category as “Model”
  5. Click “Save”
  6. Go to the creation Configuration page on the Creator Hub website
  7. Go to Distribution and enable “Distribute on Creator Store”
  8. Watch as it gets taken down for a violation

Expected behavior

If I uploaded a script to the Creator Store and made it public with this content:

print("require")

it would pass the automated asset moderation.

If I uploaded a script to the Creator Store and made it public with this content:

require(1125125952)("hello world")

it would NOT pass the automated asset moderation.

Page URL: https://create.roblox.com/dashboard/creations/store/*/configure

6 Likes
2

Hey @hovacmc , thanks for reporting. You should no longer get your assets forced offsale when this happens.
Also, btw these violations currently don’t contribute towards bans on your account.

1 Like
3

i cant require my own modules from a script because it get disabled and the appeal gets declined
why that happens?

1 Like
4

You can’t require external modules, even if you own them. See https://create.roblox.com/docs/production/creator-store#asset-moderation

Also, in the future try to create your own bug report. That makes it more likely to get attention from Roblox staff and doesn’t revive older threads

1 Like
5

Hate to revive an old thread, but I didn’t want to create a duplicate thread as the same issue is back.
I reproduced the exact same steps as I did back in November of 2025, and the issue happened again, uploading a module with the contents

print("require")

and making it public resulted in the model not getting distributed in the store for “Misusing Roblox Systems.”
I am marking this issue, which was previously fixed, as open again.

6

I also recently tried to distribute a couple scripts that weren’t malicious, including the print("hello world") script, and I’ve found some interesting results.

The majority of scripts appear under the Violations & Appeals, with some getting accepted, some getting denied (most are still under review, so it’s still inconclusive)
Another strange thing is that the original script I distributed, which solely contained print("hello world"), doesn’t even show up under the Violations & Appeals page. I can’t even appeal that asset.

The Creator Store requirements still state that only require(assetId) is disallowed. How does print("require") violate that?
Of course, the main issue lies in this blocking of legitimate scripts just wanting to call a ModuleScript that isn’t an external asset ID.
This bug effectively blocks all mentions of a commonly used Lua global, and this is the second time I’ve seen it happen almost 5 months apart.

1 Like
7

AI moderation unfortunately picks up many instances of require usage in models and plugins. Most of these instances are false-flags, yet they still end up causing problems. I had to appeal my plugins and even re-upload them multiple times.

Can’t use multi-script architecture for no reason lol.

2 Likes
8

its absolutely disappointing this hasn’t been fixed because roblox lazy moderation has resorted to their stupid ai. my module is suffering under the same issue if you try to getservice datastoreservice

9

Hey, thanks for reporting. We’re working on other broader safety fixes for the next couple months, but hope to eventually come back to fix this.

10

The same thing happened to me just now. After my asset was restricted, I updated it, removing the require for my module. But AI moderation still rejected this new version and left my asset restricted. I filed an appeal about this (on new version), should I wait until there is a response or re-submit as a new asset? (I think the appeal will be rejected)

11

Some spring cleaning: going to close this because it has the same root cause as this post Can't publish something like the "ReflectionMetadata.xml" due to an unintended action for Script based Assets. The stuff mentioned in your post is still a valid issue. In the meantime, I’d recommend appealing if you run into this.

1 Like