Summary
My Studio plugin “Studio Organizer” (Creator Store asset ID: 96423134102803) was disabled from the Creator Store for “Misusing Roblox Systems.” I’ve used all available appeals and the decision stands. I’m not asking for the decision to be reversed. I’m posting here to ask for clarification so I can comply with the rules when I publish a future version or a new asset.
What the plugin does
The plugin is a Studio-only productivity tool. It lets creators tag Instances in the current place using CollectionService, search and filter by name, and maintain a small favorites list. Tag metadata (e.g. colors, icons) is stored in plugin settings. It uses HttpService only for JSON encode/decode of that local data—no web requests, no external servers, no InsertService/LoadAsset, and no automation of publishing or economy systems.
What I’m asking
Could someone from Roblox explain which specific behavior or part of the plugin was considered to violate the “Misusing Roblox Systems” standard? For example, was it the use of CollectionService tags for organization, the way the plugin stores data, or something else? Knowing that would help me fix or avoid the issue in a future, fully compliant version.
I’ve read the Community Standards and Creator Store asset moderation guidelines and want to align with them. Any guidance would be appreciated.
Multiple of my plugins were subject to this punishment, and upon appeal they have been reinstated. I can confirm that Roblox has indeed put out some type of wave and banned many assets or users, although it’s safe to say that most victims do NOT deserve a termination whatsoever, and neither do many assets deserve to be disabled.
I also got my plugin unexpectedly disabled, and I also was using HttpService (to generate GUIDs). it seems likely that Roblox is blanket disabling plugins that import HttpService as some flawed attempt at combating malicious plugins, without even checking if any actual request calls are being made.
This may not always be the optimal option. Clicking a button to install a plugin/add to your library is far easier than setting up a local version, especially if you also don’t want to explicitly make it open-source.
True; treating the Roblox-hosted plugin as a mirror for the project would be a suitable approach, as at least then the source can’t be fully withheld by poor moderation practices.