Roblox AI Banned Me for Self-Defense Against a Coordinated Stream-Snipe Raid. Management Approved the Appeal, but Support Bots are Looping
Hello Reddit community,
I am making this post because I am trapped in a nightmare technical loop with Roblox Support, and I need to bring human attention to how automated AI moderation is failing veteran players.
The Coordinated Raid (Violation of Anti-Harassment Principles):
I am a mature content creator with a completely clean 4-year record on Roblox—never received a single warning or strike before. Recently, a toxic group of haters organized a malicious, targeted stream-snipe raid on my live broadcast. They severely harassed me and instigated a targeted provocation. According to fundamental safety rules (like Reddit Rule 1 and Rule 3 against bullying and instigating harassment), no system should be used as a weapon against a user. However, the automated Roblox AI blindly flagged my defensive reaction to this live abuse, completely failing to understand the context of the harassment.
Management Approval & Technical Glitch:
Roblox Senior Management has already investigated this matter, looked at the raid context, and explicitly acknowledged that the restriction was a false positive caused by a server-side error. Furthermore, their engineering logs confirmed my profile is stuck in a corrupted database "Ghost State" (Error 529). Just recently, their backend glitched further under the hood, incorrectly pulling a dead archival ticket from months ago and mixing up my account data.
The Support Loop:
Even though senior leadership approved the recovery, line-level support keep automatically closing my new technical tickets with generic 6-month rule templates. Front-line staff simply do not have the administrative rights or database access to overwrite a corrupted user table state, yet the automated system refuses to route my case to actual live engineers.
I do not need a standard policy appeal—my innocence and 4-year clean record are established. I strictly need a live Customer Service Supervisor or a DevOps Engineer to manually switch back to Active.
Please upvote this so a human community manager can see this database lock and escalate it to the engineering desk. Thank you!