I recently reported a Roblox game that contains content clearly harmful to minors via the Illegal Content Report Form, specifically involving a “glory system.” After submitting the report, the moderation tool responded that the game had already been reviewed, removed from the platform, and deleted from the system.
However, despite this message, the game is still publicly visible and fully playable. When I attempt to report it again, the system continues to display the same message “that the game has already been removed” even though nothing has changed.
This behavior is deeply concerning because it creates a false sense of action. It suggests that moderation has already addressed the issue when in reality, the content remains accessible. If this is a broader issue in the report handling system, it means that harmful or illegal content could persist on the platform indefinitely, while users are misled into thinking it’s been dealt with.
For a platform with a large number of younger players, this poses a serious safety risk. Games containing explicit or exploitative systems may continue to spread or attract minors, and players who try to report them have no effective way to escalate the issue once the automated system decides it’s “already been removed”.
What makes this even worse is that the game’s in-game GUI contains a Discord invite link, which leads players directly to an external server. From there, players can be exposed to explicit, exploitative, or otherwise inappropriate content that clearly violates Roblox’s Community Standards and puts users at serious risk.
This bug needs urgent attention both to ensure that moderation reports reflect the real state of a game, and to prevent harmful content from slipping through due to a reporting system error.
UPDATE: The game was eventually removed (likely not because of the reports I made), but only after several hours of being publicly available. This delay combined with the misleading “already removed” message makes it seem like the report system may have detection or synchronization issues.
A private message is associated with this bug report
