ScriptNovaa’s record of reported copying concerns, notices to PlayVortex, and possible future legal action following a request for assistance from MassAttack.
Current status: pre-litigation dispute · No filed lawsuit recorded
Vortex acknowledged the October 3 and October 5 notices and disputed the allegations. IMI confirmed forwarding the full notice and declined immediate service suspension. The dispute remains unresolved; our requested October 7 response deadline remains on the record.
Published October 5 · Last updated October 6, 2026 · Publisher: ScriptNovaa · Contact: legal@scriptnovaa.com
Action requestedBegin October 5
Review the concerns, acknowledge receipt and identify the responsible contact.
Revised response deadlineOctober 7 · 5 p.m. ET
2026 · Replaces the October 10 deadline in the earlier notice.
Scope of public review18 game pages · 120 listings
Page descriptions and catalog names reviewed; selected visuals compared.
01 / Overview
What the PlayVortex dispute concerns
MassAttack is independent of ScriptNovaa and contacted us for assistance. ScriptNovaa raised concerns about possible copying of Roblox-related avatar assets and game content on PlayVortex.io. We contacted Vortex’s published email address, Roblox’s copyright contact, the domain registrar and identified service providers.
This is ScriptNovaa’s account of that correspondence. It is not a court filing, judgment or finding that Vortex infringed copyright. “Vortex Lawsuit” is the title of this public update about a dispute that may lead to future litigation.
Which site is involved?
The notices concern playvortex.io, also referred to here as PlayVortex or Vortex. They do not establish that vortex.io is the same operator or has any involvement. Similarly named websites and unrelated businesses are outside this record.
02 / Reported concerns
Potential issues raised for review
These are concerns about specific content and permissions, not a list of established violations. The reviewed public pages do not establish the origin of underlying asset files, source code or licenses.
Asset origin unresolved
Avatar models, character textures and faces
The notices question whether Vortex uses protected Roblox-related character models, textures or face assets without permission. A block-shaped avatar or a common face expression by itself does not establish that an asset was copied. We asked the operator to identify the source and permission for the questioned content.
Vortex catalog · 120 listing names inventoried, including 46 face listings. An exact Super Super Happy Face match was not established.
Earlier comparison corrected
The Crossbridges and Crossroads
The original report compared Vortex’s The Crossbridges with Roblox’s Crossroads. Subsequent review showed different layouts in their currently published thumbnails. We withdrew that comparison as evidence of infringement and sent the correction to the recipients of the report. The earlier description of Crossroads as an island divided by colored bridges was inaccurate.
ScriptNovaa has since raised a separate concern based on its team’s reported gameplay review, including a Rivals-style game. This is an allegation requiring specific comparisons; the Rivals-style game’s exact title and URL have not been established in this record. The thumbnail correction is not withdrawn.
MassAttack and ScriptNovaa raised a concern about similarities to Roblox games, including Arsenal. Our public-page review did not establish an Arsenal asset or code match. Arsenal is credited to ROLVe, so the rights in particular game content must be considered separately from Roblox’s own assets.
These pages were included in the notice for review of map artwork and assets. No exact protected-asset match was established. The supplied Roblox HQ comparison page is a user reupload crediting GFink; its existence does not establish Roblox ownership of every component or copying by Vortex.
The notices request removal of any protected code or assets used without permission, including in gameplay. The public-page review did not inspect or compare source code. Common genres, mechanics and broad game ideas were not established as copied protected material.
No copied text identified
Forum design and content
A concern was also raised about the Vortex forum. Its use of Discourse and familiar forum layouts does not establish copied Roblox forum content. No specific copied forum text was established in this review. Personal account details are withheld from this public record.
03 / Evidence record
Corrections stay visible
Accuracy matters when asking an operator or provider to act. The Crossroads comparison was corrected in messages to Vortex, Roblox, Cloudflare, OVH, Namecheap, hCaptcha and Resend. The broader concerns remain reported, but the withdrawn comparison should not be used as proof of a copied map.
Limits of this review
The review covered descriptions of 18 game pages linked from the Vortex home page, catalog listing names, and selected visuals. It was not an audit of every asset, a code inspection, or an adjudication of ownership. We do not claim to have identified “all copying items.” No provider response in this record establishes infringement.
Supporting correspondence is retained privately by ScriptNovaa. This page publishes summaries, not inbox screenshots or full emails. Personal names, operator email addresses, physical addresses, private IP addresses, account links, report identifiers and ticket numbers are redacted from the published source. Sensitive details are omitted completely. Requests for specific evidence or corrections can be sent to legal@scriptnovaa.com.
04 / Timeline
How the correspondence developed
Roblox, Vortex and Namecheap contacted
ScriptNovaa sent the initial review request to Roblox’s copyright contact, notified Vortex through its operator email and contacted Namecheap. Vortex later received a demand with an October 10, 5 p.m. Eastern response deadline.
Cloudflare forwarded the report
Cloudflare’s automated response confirmed forwarding the report (reference redacted) to the website owner and hosting provider, identifying OVH SAS as the host. Forwarding was not a determination of infringement. Resend and hCaptcha also received review requests.
The Crossroads comparison was withdrawn as evidence
After further review, ScriptNovaa corrected the map comparison. The final notice identified the questioned pages, requested asset-source and permission information, and preserved the October 10 response deadline. Roblox received the updated record.
Existing tickets used for follow-up
Roblox directed correspondence to its existing ticket. ScriptNovaa requested that its IP team contact Vortex directly. hCaptcha said the evidence did not establish an actionable violation involving its service and later closed its case after recording the correction.
Providers asked to help reach the operator
ScriptNovaa asked Resend, hCaptcha, Namecheap, Cloudflare and OVH to forward an urgent message. Providers were asked to review continued service under their policies and share publicly disclosable business or legal-notice contact information.
Begin today; respond by October 7
A revised notice demanded that Vortex begin addressing the concerns October 5 and provide a substantive response by October 7 at 5 p.m. Eastern. Delivery to Vortex was confirmed by the sending mailbox. Providers were sent the new deadline for their forwarding requests.
Vortex acknowledged the notices and disputed the claims
Vortex Interactive LLC challenged the evidence and reporting authority, raised a concern about the address entered in a provider report, and requested that formal correspondence go to its registered agent. It also requested preservation of related records. The operator response is summarized here without personal contact information.
IMI confirmed forwarding the complete notice without a bounce or reply to IMI. It declined immediate suspension on the current evidence. Replies to Vortex and IMI were prepared for review and have no verified delivery recorded in this update. A draft does not create a new delivered notice or change an existing deadline.
05 / Responses
What the recipients have said
Correspondence status as recorded October 6, 2026
Recipient
Reference
Recorded response
Vortex
Published operator email
On October 5, Vortex Interactive LLC acknowledged both notices and disputed the claims. It requested authorization details, questioned the accuracy of the report address, directed formal correspondence to its registered agent, and requested preservation of records. It did not admit infringement. A follow-up reply was prepared for review; delivery of that reply was not verified for this update.
Roblox
[Private references redacted]
Receipt confirmations received. A support reply linked its policies and asked us to use the existing ticket. We requested direct contact with Vortex; no enforcement decision is recorded.
Cloudflare
[Private references redacted]
Confirmed forwarding to the owner and host; identified OVH. The evidence correction was sent and acknowledged.
OVH
Host identified by Cloudflare
Copied on the correction and urgent follow-ups. No substantive OVH decision is recorded.
Namecheap
[Private reference redacted]
Confirmed receipt and said it would review under its policies, contacting us if more information was needed.
hCaptcha / IMI
[Private reference redacted]
On October 6, IMI confirmed that the full notice was forwarded to the account-holder email, with no bounce or reply to IMI. It declined suspension because the current evidence did not meet its policy threshold and hCaptcha does not host the content. It requires valid legal process for private identifying information and described standard record retention. A follow-up reply was drafted for review and has no verified delivery recorded in this update.
Resend
Email correspondence
Resend clarified that Resend provides email delivery and does not host the website content. We requested forwarding assistance and policy review.
A receipt confirmation, ticket number or forwarded report is not a ruling against Vortex. Google is not listed as having made an enforcement decision because no verified decision is recorded here.
06 / Revised demand
The response ScriptNovaa requested
Requested substantive response
October 7, 2026 5:00 p.m. Eastern
The revised notice replaces October 10. It requests acknowledgement and the start of corrective review on October 5. These are ScriptNovaa’s requested deadlines, not court-imposed dates.
Acknowledge receipt. Identify the person responsible for handling the notices and the correct legal or business contact.
Begin reviewing the questioned content. Examine the avatar assets and content on the listed game and catalog pages.
Explain origin and permissions. Provide a substantive response describing the source and permissions for the questioned assets.
Address unauthorized material. Remove any protected material used without permission and explain the steps taken.
Preserve relevant records. Retain source files, licensing documentation and relevant correspondence while the dispute is unresolved.
Respond by email. Send the acknowledgement and substantive response to legal@scriptnovaa.com.
Providers have been asked to review continued service, including a request for suspension. No suspension is confirmed. IMI declined immediate action; Cloudflare and hCaptcha are separate services. Provider decisions are governed by their own reviews and applicable process. They have also been asked for public business contacts, legal-notice addresses, public server information and formal disclosure procedures.
07 / Potential legal action
What may happen next
ScriptNovaa has told Vortex and the contacted providers that this matter is urgent and may involve legal action. If Vortex does not respond by the requested deadline, ScriptNovaa intends to consider further escalation with MassAttack and appropriate legal advice.
No lawsuit, court order or pending litigation has been established in this public record. We do not state that Roblox has agreed to sue, that Vortex is legally required to reply to a message, or that silence proves infringement. Any future filing or confirmed enforcement decision would require a separate, dated update.
Roblox and other rights owners control their own enforcement decisions. A formal infringement notice must be supported by the specific works, locations and authority required for that process. See the U.S. Copyright Office’s notice-and-takedown guidance.
08 / Questions
Clear answers about the dispute
Has a Vortex lawsuit been filed?
No filed lawsuit is recorded here as of October 6, 2026. This page documents the dispute and possible future legal action.
Is this an official Roblox notice?
No. This page is published by ScriptNovaa. Roblox was contacted and asked to address the operator directly. ScriptNovaa does not publish this page as Roblox’s official statement.
Did Vortex copy Arsenal or Super Super Happy Face?
The concern was raised, but no exact asset or code match was established in the recorded review. Those claims should not be presented as proven findings.
Why was the Crossroads comparison corrected?
The earlier description did not match Roblox’s current Crossroads page. The published map thumbnails have different layouts. ScriptNovaa corrected the recipients’ records rather than continuing to rely on inaccurate evidence.
Is vortex.io part of this dispute?
The notices identify playvortex.io. No involvement of vortex.io or another similarly named operator has been established.
How can Vortex respond or request a correction?
Send a response, licensing information, identification of the responsible contact, or a specific correction to legal@scriptnovaa.com. Include the relevant page URL and the statement being addressed.
How can community members help?
Join ScriptNovaa’s Discord for discussion and updates. If you have specific asset-origin evidence, send source URLs and a clear explanation privately to the legal mailbox. Avoid repeated messages, harassment, personal-information collection or presenting unverified allegations as facts.
09 / Community
Follow the updates. Support the effort.
ScriptNovaa’s regular website is paused while we focus on the Vortex dispute and potential lawsuit. Join our Discord community to follow updates and support the effort. The invitation is for community participation; this page does not collect donations or promise an outcome.