Legal Record
Roblox Platform Access Case
Six Roblox communities belonging to Lucky 7 Entertainment LLC were locked on 20 July 2026. The account enforcement that locked them was appealed and reversed the same day, and Roblox confirmed in writing that the asset which triggered it had been approved. The communities were not restored at the time. Four of the six were unlocked on 22 August 2026, thirty-three days later. Two remain locked.
We are publishing this record because we have been unable to obtain a substantive response through Roblox’s ordinary support channels. Between 20 July and 12 August 2026 we opened five support tickets, supplied every item of information requested of us, and were told on 24 July that our case had been escalated to a specialist. No specialist has contacted us. Our President wrote directly and was told that Roblox could not discuss the matter with him because he does not own the account. The account owner had been writing to Roblox continuously that entire time.
The affected communities are not social groups. They hold the development, testing, moderation and team administration for five active projects, including DELTARUNE: Tower Defense. While they remain locked we cannot publish updates, manage group-owned assets or administer our teams, and internal release dates have moved as a result.
On 22 August 2026 Roblox unlocked four of the six, including those carrying our active development, testing, moderation and team administration. Their restoration resolves the operational core of this dispute and we record that without qualification. Two archived communities remain locked, and Roblox has declined to discuss them on the ground that they are held by a related company account.
Current status
- Account
- Restored. Appeals recorded as accepted on Roblox’s own systems.
- Flagged asset
- Confirmed approved by Roblox on 21 July 2026.
- Four communities
- Unlocked by Roblox on 22 August 2026.
- Two communities
- Still locked.
- Primary support case
- #176870385, open since 20 July 2026.
- Specialist escalation
- Stated by Roblox on 24 July 2026. No response received.
- Formal notice
- Served on Roblox Corporation by certified mail, 13 August 2026. Delivered and signed for 18 August 2026.
- Response requested by
- 14 September 2026.
- FTC report
- Submitted, per correspondence of 22 August 2026.
Read the full record
The complete case file sets out the chronology, the affected communities and their group IDs, the support history, the business impact and the resolution we have asked Roblox to provide. It reproduces the correspondence in full, including every message Roblox sent us. Public redacted issue, reference L7-RBLX-2026-001-PUB, Revision 3, dated 22 August 2026.
Record of updates
A note on how we are handling this
We would prefer to resolve this directly with Roblox, and we have said so in every message on the record. This page exists so that our position is documented and open to scrutiny, not to pressure anyone.
Please do not contact Roblox staff, moderators or support agents about this matter on our behalf. The names of the individual support agents who replied to us have been removed from the published file for the same reason. They were doing their jobs and they are not parties to this dispute.
Get in touch
Representatives of the other party, press and legal enquiries: snowzbunz@lucky7entertainment.com , using the subject line [RBLX-L7] Group Support. We respond promptly.
The published file is redacted to remove personal information, third-party details and payment data. Every ticket number, community ID, asset ID, date and Roblox statement remains intact and unaltered. The redaction policy is set out on page 2 of the file. The complete unredacted case file has been served on Roblox Corporation and provided to the Better Business Bureau, and is available to Roblox, a regulator or legal counsel on request. The BBB complaint confirmation published here is redacted to remove personal details, the complaint reference and the private case-access links contained in the original.