Events & Developments

致相关各方：

以下内容构成一份非机密外国情报评估报告，编号ISS-EXT-2026-009，涉及代号PATHOS III之内部安全服务机构（以下简称“ISS”）的组织架构、运作规模及其所属社区对公开披露行为的集体应激反应。本报告以中华人民共和国官方语言撰写。原因将在后续章节阐明。

本文不是比喻。不是行为艺术。不是讽刺。ISS使用了“Operations Officer”、“Director of Intelligence”、“Department Overseer”等职衔。他们执行了代号行动——Harlequin、Muscovy、Idegem、Gimbsheimer——每个代号对应一次完整的多阶段渗透或反情报作战。他们维护了一套四级威胁评估体系（AR-1至AR-4）、一个五级分级保密架构（SC1至SC5）、以及一条全自动审查流水线。他们在一个乐高游戏的Discord服务器上做了这一切。

所以——如果他们可以在Roblox上运行一个仿照真实国家安全局构建的情报部门，那么一个外部分析员完全有权用外国情报简报的格式来记录它。掩耳盗铃的人不配决定铃铛响不响。

第一章 — 为什么是中文

先回答你脑子里的第一个问题。

用英文写，他们说“AI generated”，然后关掉标签页。用英文写，他们扫一眼标题，打一句“i aint reading allat”，然后继续在Discord里发表皮肤。用英文写，他们甚至不需要思考就能否认——因为否认英文内容的肌肉记忆已经刻在这个社区的DNA里了。

用中文写，游戏规则就变了。

你要么打开翻译器，要么关掉页面。没有中间地带。没有“I skimmed it”的借口。你要么投入三十秒把它粘贴到Google Translate里然后真正地阅读，要么你承认你连这三十秒都不愿意花——然后你的“I read all of them”就变成了一个可验证的谎言。

中文是一道过滤器。ISS的审查系统设计的核心理念是最低阅读门槛、最大信息收集量——/intel check一键完成，一份完整的个人档案在三秒内生成。本文的设计理念恰好相反：最高阅读门槛、最小否认空间。你要先理解，才能反驳。你要先翻译，才能判断。

这不是装腔作势。这是方法论。

第二章 — 解剖一头大象

在我们讨论否认之前，先搞清楚他们到底在否认什么。

ISS档案馆不是一篇博客帖子。不是一个吐槽贴。不是一个“前成员爆料”的Reddit帖子。它是一整套机构运作痕迹的系统性整理——从一个73个文件、58MB的原始数据转储中提取、清洗、索引、归档、上线的。八个分类目录。一百一十七个频道。五万七千条消息。全文可搜索。暗色主题。侧边栏导航。

让我把这头大象拆开来给你看：

调查档案（inquiries/）——70个文件，细分为三类。案件文件（case-）共19份：命令滥用调查、账号共享环渗透、医疗部门腐败审计、泄密源追踪、多阶段反情报行动。组织评估文件（goi-）共27份：Global Occult Coalition、Nebulith、Atlas X、Mayflower Compact、Lobotomy Superconductor、The Orange Crew、Project Prophet、SD Legends——十几个外部群组被逐一拆解分析，每份报告包含组织架构图、关键人物标注、威胁等级评定。个人档案（poi-）共24份：每份都是一个独立的人物调查卷宗——用户画像、Roblox群组成员历史全量导出、跨平台行为分析、信任等级评估、威胁评级标注。24个人。24份档案。每一份都是一个真实的人被当成情报目标处理的完整记录。

但这只是调查档案。

档案馆还包含：21个档案室频道（archives/），其中包括替代账号追踪系统、11个独立的反情报卷宗（CI-001至CI-011，每个都是一次完整的内鬼猎杀行动）。5个通讯频道（comms/），包括一个精选频道——ISS内部成员自己挑选的“名场面”集锦。3个融合中心频道（fusion-centre/），用于跨部门情报整合。9份面谈记录（interviews/），逐字转录——审讯式的一问一答，每份都附有ISS分析员的评估笔记。一个完整的审查系统（vetting/），包含审查大厅和操作手册。一个威胁检测流水线（threat-detections），自动化标记可疑行为。一个主体报告汇总频道（subject-reports），190多份独立的主体评估报告——每一份都是一个被ISS认定为“值得关注”的人。

101个被识别人员。190多份主体报告。数百次/intel check自动化查询。每一次查询都生成一份完整的个人情报摘要：用户ID、账户创建日期、徽章数量、群组成员列表、账户估值、组织归属标注。

这就是他们说“不值一提”的东西。

掩耳盗铃。

第三章 — 否认者的标本采集

2026年2月28日。ISS档案馆在Pathos Leaks服务器的讨论中再次被提及。以下是标本采集结果——原文照录，未经修改：

“i aint reading allat”。“this rblx drama not that srs.” “none of them were really all that interesting.” “Id say the reaction of the pathos administration is more important than the words of a random which was banned and pissy on the server.”

注意模式。不是一个人在否认——是一个生态系统在否认。每一句否认都遵循同样的三拍节奏：声称读过→表示不屑→拒绝提供细节。当Mike——实际参与建设网站的人——指出网站上有七篇文章时，一位用户声称全部读过且“不感兴趣”。Mike要求他说出第七篇文章的第七个单词。对方沉默了一分钟。

Mike的回应：“bro js checked.”

此人即为自欺欺人的教科书案例。声称读过七篇文章。无法提供任何一篇的任何细节。然后继续声称这些文章“不重要”。这不是观点——这是行为模式。同一个Pathos Leaks服务器中，有人的Roblox群组列表曾在ISS的审查系统中被全量导出，有人的用户ID被/intel check命令查询过数次，有人直接出现在POI卷宗里——编了号、归了档、标了威胁等级。然后这些人回过头来说：“not that serious.”

你自己的名字在档案里，你说档案不重要。这不叫“观点”。这叫利益相关方的自我保护性否认。

第四章 — 时间不能漂白体系

第二种否认形态：“这些都是旧资料了。”

ISS于2025年11月被泄露。档案馆于2026年2月上线。间隔不到三个月。但即便我们接受“过时”这个前提——它依然是一个荒谬的辩护。因为档案馆记录的不是事件，而是体系。

事件会过时。体系不会。

CI-001到CI-011的反情报卷宗不会因为三个月的时间间隔就失效——它们记录的是ISS如何猎杀内鬼的方法论。Operation Harlequin和Operation Muscovy的行动报告不会过期——它们记录的是ISS如何策划渗透的完整流程。24份POI个人卷宗不会因为日历翻了一页就消失——它们记录的是ISS如何将真实的人当成情报目标处理的系统性做法。审查流水线的操作手册不会过时——因为流水线本身就是设计来持续运行的。

说一个情报机构的操作手册“过时了”就像说一本刑法教科书“过时了”——方法论不会因为你停止使用它就不再存在。它只会从“进行中”变成“已记录在案”。ISS的体系现在是后者。每一个频道、每一份报告、每一次/intel check查询都被永久保存在一个可搜索的在线档案馆中。

时间不能漂白体系。只有阳光可以。

第五章 — “AI生成”：最后一道防线

当你无法在内容上反驳一个论点的时候，你攻击它的来源。当你无法攻击来源的时候，你攻击它的存在方式。

在Pathos Leaks的讨论中，有用户给出了终极否认：“their entire accusations base is AI generated.” 在另一次对话中，Mike遇到了同样的指控——他以讽刺回应：“ai generated bro. doesnt take much.”

这是一个自我封闭的逻辑闭环，精妙得令人叹服。观察它的运作方式：如果文章写得太好→一定是AI。如果网站太整洁→一定是机器做的。如果有人愿意花时间整理70份调查文件和9份逐字面谈记录→那他们一定不是真人，因为“真正的人类”不会花这么多时间在一个Roblox社区上。这个逻辑的终点是：任何有效的批评都可以被归类为“非人类生成”。任何组织化的记录都可以被归类为“机器输出”。任何让你不舒服的事实都可以被归类为“人工智能的幻觉”。

妙啊。一夫当关，万夫莫开。只要你坚持说一切都是AI写的，你就永远不需要面对内容本身。

但这里有一个小问题：ISS自己花了好几年的时间来执行这一切。他们自己建立了一个带有分级保密系统、跨部门协调机制、自动化情报收集流水线的完整官僚体系。他们自己对24个真实的人建立了独立的调查卷宗。他们自己运行了代号行动。如果ISS的行为值得花好几年的时间去执行——那它至少值得花十分钟的时间去阅读。

而你正在阅读的这篇文章是中文的。试试看用“AI generated”来解释这个。

第六章 — 结语

让我把话说清楚。

这份报告不关心你是否同意它的结论。它关心的是你是否阅读了原始材料。档案馆就在那里。117个频道。全文可搜索。每一份调查文件都有原始的Discord消息作为证据链。每一份POI卷宗都可以追溯到具体的/intel check查询输出。每一份面谈记录都是逐字转录。你可以自己验证每一个字。

如果你验证了然后得出结论说这不重要——那是你的权利。但如果你没有验证就说这不重要——那你只是在重复一个你从别人那里继承来的观点，而那个“别人”在被要求说出第七篇文章第七个单词的时候沉默了整整一分钟。

这就是“不值一提”的真实含义。不是“它不重要”。而是“我不想面对它可能重要的事实”。

At 5:42 PM on February 26th, someone posted a link in general chat. Within three minutes there were forty messages. Within ten there were two hundred. By midnight the channel had logged over a thousand new messages about a single website that most of them had never seen before but all of them had opinions about. Some of them were in it.

The link was titaniteaccords.com. The ISS Archive. 117 channels. 57,000 messages. Vetting records, intelligence reports, surveillance screenshots, case files on minors, cross-platform tracking logs — the entire back end of PATHOS III’s Internal Security Service, laid out in searchable HTML with a dark theme and a sidebar. RCR and the Titanites had gotten to it first. Pathos Leaks — the server literally named for leaking Pathos material — had been beaten to the punch on their own story. cassianor_, who apparently had the data sitting on his hard drive, put it simply: “W for me i dont have to upload the server now. I can go back to my laziness now.” Five hundred gigabytes of data on his computer. Someone else did the work. He went back to bed.

I. The Drop

The first wave was disbelief. cev0x asked “howd rcr leak it first” and then, four seconds later: “LOL.” notabot258347 started posting screenshots — the landing page, the channel list, the analysis page, the articles — one after another, every thirty seconds, back to back. ccoovert_88457 looked at the site and said “this is like the 2nd plane hitting the towers.” For a Roblox leak website. batblox called it “the pathos version of the stein files.” cev0x scrolled through and landed on the articles page. “who the fuck is writing news blogs,” he said, which was a fair question. rokuw saw the byline: “PATHOS STABBER. #7.” Nobody knew who that was. Nobody had seen that name before. The site had appeared fully formed with a byline attached to it and nobody behind it that anyone recognized.

Within minutes, notabot258347 was linking the site to anyone who asked and several people who didn’t. He posted the embed six separate times. He answered questions. He vouched for the PII handling. “I also think they reviewed everything manually,” he said. Then: “website wasnt vibecoded either.” He was doing PR for a website nobody had asked him to promote, and he was going hard. Three minutes in and notabot258347 had already picked a side.

II. Reading Your Own File

Then people started finding themselves. agentgblackhawk clicked through the channel list and went quiet for a moment. “Yo they got an entire channel on my discord server,” he said. Then: “ts is peak.” He wasn’t angry. He was impressed. ISS had dedicated a channel to monitoring his Discord server, and he thought that was funny.

mnoq found something worse. “I just found an embed link with my full desktop screenshot saved to the iss chat,” he said. A screenshot of his desktop. Saved to an intelligence channel. From 2022. He scrolled further. “Oh hey its when i got dev access to the game,” he said, scrolling through his own surveillance file like he was catching up on old posts. Two messages later he was correcting the record — “i was never affiliated with subby” — arguing with an intelligence report that had been sitting in a locked channel for three years. okzyrox backed him up: “i am NOT associated with subby bro. this is slander.” They were filing appeals against a dead server. ISS doesn’t exist anymore. The people who wrote those reports moved on or got fired. But the reports were still there, still wrong, and people were still getting mad about them at 7 PM on a Wednesday.

III. Is It AI?

An hour in, the cope arrived. codenamethetruth showed up and announced: “the new website is generated by AI.” Then: “their entire accusations base is AI generated.” Then: “What’d you guys use for it, chatGPT?”

michaelinvicta took the bait and ran with it in the wrong direction on purpose. “Nope. Super secret ai model. Its cia level bro we are cia agents.” codenamethetruth tried to recover: “right... claude... mb chat.” michaelinvicta kept going: “nah. even more secret. we used copilot ai bro. microsoft edge ai.” rolo2410 added: “pathosstabber7 used microsoft word to code this.” Nobody denied it. They just kept one-upping him with dumber explanations until he stopped asking. codenamethetruth tried one more time: “no but i expected them to not copy and paste gpt’s response to what it found into their accusations.” rolo2410 didn’t blink: “honestly did you expect them to manually sparse 60k messages or something. Or is the ux too clean.” Then, separately: “firstly no one uses chatgpt its dogshit.”

feaarrr, who had been lurking, shut it down in four messages: “who made the ui for this website. Its lowkey. Goated.” The answer came from rolo2410: “pathosstabber7 (secret).” Nobody elaborated. codenamethetruth said “but yeah, the website is just larp,” and the conversation moved on. The AI accusation didn’t stick. Two hours later people were still browsing the site.

IV. The PR Lesson

At 9:22 PM, Toximay showed up. He had read the article. He posted a screenshot of the Divorce Papers analysis with the caption: “Lol RCR decided to flame my contract ♥” — which was a generous way to describe a piece that spent 2,400 words taking apart every clause he wrote. Then he quoted the editorial directly into general chat: “The funniest part is that it’s competent. This is not a joke document. Whoever drafted it understood contract law, or at least understood it well enough to produce something a court might actually look at before laughing.” He followed it with: “Lol.”

Then he started engaging. “They are trying to compliment and rage bait,” he said. “They’re making fun of the fact I wrote an actual contract.” He doubled down: “A contract is a contract. Especially because it’s between two companies. That’s what a lot of people don’t get.” notabot258347 was waiting for him. “The fact that u guys make contracts for legos… is… comical,” he said, each word in a separate message, each one getting a “😭” reaction. “I dont care your lego nda means absolutely nothing. If i breach it and you take me to court you will be laughed out.” Toximay held his ground: “A judge would believe it or not.”

lunapedia. had been watching. He gave Toximay the only useful advice he got all night: “Youre gonna have to learn to ignore and not respond to a lot of things. Youre getting baited so hard. Ur a lego administrator. Like dude.” luxxe agreed: “ts website is js engagement farm.” Toximay’s own people were telling him to stop. He kept going. He asked if pathosstabber7 was a real person. “Bro is that a real person 😭,” he said. rolo2410 offered to forward him a response. “Hes in the chop shop rn,” he said. cev0x posted a meme of a man receiving a phone call with the caption: “pathosstaber7 is writing an article on you.” It got two reactions. One of them was Toximay’s. He was laughing at his own coverage. That’s generally not how you win a PR fight.

V. The Arrival

At 11:25 PM, pathosstabber7 joined the chat and posted a single emoji: 🤖. rokuw saw it first. “OH NAW,” he said. Then: “PATHOSSTABBER.” Then: “Bro Im scared.” The robot emoji sat there. No follow-up. No explanation. Just 🤖. The guy half the server had spent six hours arguing about was real, and his entire contribution to the conversation was a robot face. The chat kept going.

They wrote a legal separation agreement. A real one. Eighteen sections, subsections labeled with Roman numerals, governing law clauses, a dispute resolution framework, signature blocks at the bottom. For a Roblox group. Someone sat down, probably in a Google Doc, and typed the words "SEPARATION & MUTUAL RELEASE AGREEMENT" at the top of a document about who gets to keep the fake SCP containment facility. Then they kept typing for 315 more lines. Nobody stopped them. Nobody closed the laptop. Nobody said the words "we are arguing about a children's game" out loud. They just kept going.

The full title is "UNNAMED.GAMES & PATHOS-III SEPARATION & MUTUAL RELEASE AGREEMENT." It runs 315 lines. It defines the Parties. It references principal addresses. It has a severability clause. It has an assignment restriction clause. It has a clause about clauses. If you printed it and handed it to a first-year law student, they would read six pages before realizing it was about a children's game on Roblox. If you handed it to a second-year law student, they would realize immediately, because the word "Robux" appears next to the phrase "commercially reasonable period."

I. The Parties

On one side: Krescent, acting on behalf of PATHOS-III, which the agreement helpfully defines as "the Roblox community currently known as [SCPF - Special Containment Procedures Foundation] together with its associated Roblox game(s), branding, lore, original in-game assets, official community platforms (including Discord servers), media, and related intellectual property." That is one sentence. It has nine commas. It defines a Roblox group with the same specificity you would use to define a multinational holding company. On the other side: unnamed.games, referred to throughout as "ungms" because even the legal abbreviation sounds like someone having a stroke mid-deposition. The agreement refers to them individually as a "Party" and collectively as "the Parties." Like a real contract. Because it is one. For a Roblox group.

Section 11 contains the best clause in the entire document. Both parties "acknowledge that they have had the opportunity to review this Agreement, to seek independent legal advice if desired." Independent legal advice. Picture that phone call. "Hello, is this the law office? I need counsel. It's about my Roblox group." Picture the silence on the other end. Picture the lawyer Googling "Roblox" while putting the client on hold. Picture the billable hours.

II. The Intellectual Property Inventory

Section 1.4 contains an itemized list of PATHOS-III's intellectual property. It includes: logos, marks, visual identity elements, and branding materials. Roblox place files and game instances. 3D models, meshes, props, and environmental design. Textures, materials, decals, and graphic elements. Animations, rigs, and character movement assets. Sound effects, music, voice lines. User interface designs, HUD elements, menus, and visual overlays. Maps, builds, game designs, and structural layouts. They inventoried everything. Every mesh. Every decal. Every menu overlay. Someone went through a Roblox game and catalogued its assets with the same rigor you would use for a corporate merger. Eight subcategories. Lettered and numbered. Sub-lettered and sub-numbered. For lego bricks.

unnamed.games gets to keep its "proprietary development frameworks, backend systems, server architecture, reusable code libraries, tooling, deployment systems, administrative systems, and any generic or multi-project infrastructure." DevSparkle walked away with the code. Pathos kept the lore about fake SCPs. Both sides inventoried their holdings, divided the assets, and split custody of the virtual containment facility like two parents who can't agree on who gets the dining room table except the dining room table is a 3D mesh of a fake nuclear reactor and neither parent is over twenty-five.

III. The Transition Period

Section 2 establishes a sixty-day transition period during which unnamed.games must continue hosting the backend infrastructure. Sixty days. Two months of mandated continued service for a Roblox game, with clauses specifying that ungms "shall not intentionally disable, degrade, restrict, or interfere with infrastructure supporting Pathos-III." They wrote a kill-switch prevention clause. For a Roblox game. Because devSparkle threatening to pull the plug was a documented pattern that required contractual restraint. This is not subtext. This is a legally-worded acknowledgment that a grown man might turn off the servers for a children's roleplaying game out of spite, and they needed a piece of paper to stop him. That clause has a story behind it. Nobody writes "shall not intentionally disable" unless somebody already did, or credibly threatened to, and both sides agreed they needed it in writing before it happened again.

Section 3.2 adds that Krescent "shall not copy, reproduce, distribute, sublicense, reverse engineer, or reuse ungms proprietary backend systems." Reverse engineer. A Roblox bot. The word "sublicense" appears in a document about a Discord server. Section 3.4 goes further: "Neither Party shall intentionally disrupt, disable, sabotage, or otherwise interfere with the other Party's intellectual property." The word "sabotage" appears in a legal contract about a Roblox group. They needed an anti-sabotage clause. For virtual containment chambers. Let that sit for a moment.

IV. The Severance Package

Section 4. Severance compensation. unnamed.games receives "ten percent (10%) of the net Robux revenue generated by Pathos-III for a period of twelve (12) months." Twelve months of Robux royalties. A revenue participation agreement. For Robux. Let's do the math they didn't. The current DevEx exchange rate is roughly $0.0035 per Robux. A Roblox SCP group of this size might generate anywhere from 200,000 to 500,000 Robux per month on a good run. That's $700 to $1,750 a month. devSparkle's 10% cut: $70 to $175 monthly. They wrote a twelve-month severance compensation framework with monthly accounting cycles and payment terms for what might amount to the cost of a gym membership. Per month. For a year.

Section 4.2 specifies that payments are "calculated on a monthly basis and remitted within a commercially reasonable period following the close of each monthly accounting cycle." Monthly accounting cycles. For Robux. Someone is doing books. Someone is maintaining a spreadsheet. Someone is sitting down at the end of every month, opening a Google Sheet, tabulating the total Robux earned by teenagers roleplaying as SCP guards, computing ten percent, converting it into a payment, and remitting it within a "commercially reasonable period." This is someone's job now. They created a job. The contract created a recurring monthly finance task that someone has to do twelve times. For Robux.

Section 4.3 hastens to clarify that this severance "shall not be construed as creating or preserving any ownership interest, equity stake, governance authority, administrative control, or continuing partnership." They had to explicitly write that paying someone Robux does not make them a co-owner. This clause exists because without it, someone would have argued it did. And they would have argued it on Discord. At 2 AM. In a general chat with 400 spectators.

V. The Restraining Order

Section 5.3, quietly buried between financial clauses, is the best paragraph in the document that nobody will ever talk about: "ungms shall relinquish and shall not seek restoration of administrative or technical access to Pathos-III Roblox group assets, game instances, Discord servers, or any systems not owned exclusively by ungms." Read that again. "Shall not seek restoration." That's a restraining order. For a Discord server. They wrote a legally-binding clause preventing someone from asking for their Roblox admin back. This is the contractual equivalent of changing the locks and putting it in writing that the ex is not allowed to come back for their stuff. Except the stuff is moderator permissions in a fake SCP facility. And the locks are Discord role settings.

Section 5.2 hammers it home: "ungms shall retain no ownership interest, equity stake, governance authority, administrative privileges, or claim of any kind." No claim of any kind. Total legal excommunication from a Roblox group. This is what a clean break looks like when the relationship being severed exists entirely on servers owned by a publicly traded children's gaming company.

VI. The Non-Disparagement Clause

Section 7.1: "Each Party agrees that it shall not make, publish, communicate, or otherwise disseminate any false, misleading, or defamatory statements about the other Party." The restriction "applies to public statements made on Discord, Roblox, social media platforms, community forums, or any other public or semi-public communication channels." A non-disparagement clause that specifically lists Discord as a covered platform. Section 7.2 goes further: neither party shall "encourage, direct, or solicit third parties to engage in harassment, reputational harm, or platform-based action against the other Party." They wrote an anti-brigading clause into a legal contract. For a Roblox group.

But the real gem is Section 7.3: "Permitted Statements." They had to write an exception clause. For telling the truth. "Nothing in this section shall prohibit truthful statements required by law; good-faith factual disclosures." They needed a carve-out that explicitly permits people to say things that are true. The implication being that without this clause, the non-disparagement section would technically prohibit honest statements about what happened. They had to write, in a legal document, that facts are still allowed. The truth needed its own subsection.

VII. The Blank Jurisdiction

Section 12. Governing law. "This Agreement shall be governed by and construed in accordance with the laws of the ___." It's blank. The jurisdiction is blank. They wrote 315 lines of contract, eighteen meticulously formatted sections, Roman numerals, defined terms, cross-references to other clauses — and then got to the part where you write which state's laws govern the agreement and left it empty. The line reads: "any legal action... shall be brought in a court of competent jurisdiction located in ___." Also blank. Two blanks. In the entire 315-line document, the only fields left unfilled are the ones that would make it actually enforceable. They built the entire car and forgot to put in the engine.

The notice addresses in Section 17 are also blank. Both of them. "For Krescent: ___. For ungms: ___." Nobody filled them in. The agreement specifically states that "Discord messages, direct messages, server posts, or other platform communications shall not constitute official notice" — but the official notice addresses are empty. So you can't serve notice through Discord, but you also can't serve it through the official channels because there are no official channels. They closed every door and forgot to build a window. The only way to formally contact the other party under this contract is through addresses that don't exist in the contract.

VIII. The Settlement

Section 10. No admission of liability. "This Agreement is entered into as a compromise and settlement of disputed matters." They called it a settlement. A settlement. The word "settlement" implies a dispute serious enough to require formal resolution. This is the same word used when corporations pay nine-figure fines to the SEC. Here it refers to an argument about who owns the admin panel to a Roblox SCP game. The section continues: this agreement "shall not be used as evidence of such liability or wrongdoing in any proceeding." In any proceeding. What proceeding? In what courtroom, in what jurisdiction (which, as established, they couldn't identify), would someone introduce this document as evidence? The existence of this clause implies someone on at least one side was worried about future litigation. Over Roblox.

Section 16 adds that "Neither Party may assign, transfer, delegate, or otherwise convey its rights or obligations under this Agreement." You cannot sell your half of the Roblox divorce. You cannot transfer your Robux severance obligations to a third party. If you signed this contract, you are personally locked in for twelve months of monthly Robux accounting. No escape. No delegation. No subcontracting your way out of calculating ten percent of what teenagers spent on virtual containment breach gamepasses.

IX. The Signature Block

The document ends with two signature blocks. "IN WITNESS WHEREOF, the parties hereto have executed this Agreement as of the date first above written." Signature. Name. Title. Date. For both KRESCENT and UNNAMED.GAMES. Two people were supposed to sign this. With titles. For a Roblox group that started because some teenagers wanted to pretend to work at a fake containment facility. The title field is blank. Nobody wrote "Roblox Group Owner" or "Lead Developer of Virtual SCP Game" because even they couldn't bring themselves to put that next to the word "Title" on a legal document. The agreement has everything a real separation contract has. Severance. IP division. Transition services. Kill-switch prevention. Anti-sabotage. Anti-disparagement. Dispute resolution. Confidentiality. Governing law (sort of). A truth exemption. A Discord restraining order. Everything except self-awareness, jurisdiction, and a title anyone would voluntarily write down.

Twenty-four thousand seven hundred and four messages. The Pathos Leaks general chat produced that many between February 9 and February 24. On opening day it averaged one message every six seconds for eight hours. By February 13 the whole day hit 184. By the 21st, twenty-seven. Everyone showed up, went feral, got bored, and left. Then on February 23 the Toximay news dropped and five thousand of them came right back.

This is not an event article. There is no timeline here, no resignations, no founder stepping down at 11 PM. This one is about the other 24,000 people in the room. The spectators, the hecklers, the ones who saw it coming two weeks early and the ones who just wanted popcorn. A few of them were genuinely sharp. The rest were there for the show. The logs have all of it.

I. It's a Lego Game

nicholasio_0 at 8:38 PM on opening night: "remember when we played a lego game to have fun and not doxx children." Then: "me neither." Then: "this genre has always been fucked." Three messages. Six seconds. That was the whole thing, really. hawkalex had seven words for it: "The larp was too serious for a lego game." postputrid couldn't even spell through the disbelief: "signign an nda for a lego group / be so fr." mitchyz pointed out that ISS's vetting process took longer than most real job interviews. The lego game was running background checks.

It kept going. enchanted_fawn compared the org chart to the Nepalese government. maxaot looked at the debate channel and went: "The heck does it mean 'Live commentary' it's a lego game debate." Someone dug up committee guidelines telling members to "maintain an air of mystery and authority in their conduct." _keystone. called it "one of the funniest things to come out of this genre." A Roblox group wrote "maintain proper aura" into its bylaws. Somebody typed that, read it back, and hit save.

II. The Watch Party

Half an hour in, the general chat was a sports bar. devSparkle joined the VC, the debate channel opened, and it was over. crvddy had the self-awareness for everyone. First: "i feel like such a fat fucking chud eating snacks in my seat while I say 'boo' or 'yay' at whatever points ark or dev make." An hour later: "dude i feel like one of those fat fucking chuds who go on red rooms and vote 'yes or no' on someones life when i react to these messages in debate." Then: "ok who wants popcorn we're watching the debate live." Six users dropped popcorn emojis within the same minute. keyaan_ wanted someone to "put subway surfers in the background of the debate im getting tired." samg10018: "peak cinema rn."

Then someone named Charlie Kirk joined the VC. totallynotmoo: "my man devSparkle you have pissed the community so bad CHARLIE KIRK has revived." People were calling it a UFC fight, a rap battle, a courtroom, a reality show, a South Park episode, and a zoo. All at once, somehow. maxaot put all of them together: "Bro imagine if every court there was a loud person coming into the room with picture repeating exactly what the man said and who screamed 'THIS IS TRUE'."

III. The Ones Who Called It

ac130originalryplayz was yelling "DO NOT LET DEVSPARKLE GET THE POWERS" nine minutes into the server's life. Nobody cared. Two weeks later devSparkle got the powers, and ac130 came back to collect. yourmotherisill called the puppet admin thing days early. Twice. First time, ignored. Second time, also ignored, but he got his "told you so" on February 23. arkzockt read devSparkle correctly: if he can't have power, he'd rather kill it than watch someone else run it. winterselection put it more bluntly: the collapse was "inevitable as soon as they made their entire infrastructure beholden to one developer."

And culbc, watching Toximay get appointed on February 23: "give it 5 months and and some more allegations finna show up." He wasn't asking.

IV. The Sharp Ones

Buried under eight thousand shitposts and popcorn emojis, a handful of people were actually paying attention. cassianor_ took apart devSparkle's ownership plan live: "So not only does dax partially own the IP, and fully own the group, now you are trying to make it so the next administrator owns neither and is a puppet." One sentence. Whole problem. devSparkle didn't have a good answer and the chat noticed. grydor went after MaD directly: "the more they keep trying to act 'on behalf of the community' the worst it is getting." Seven reactions on that one. _ellaaa_ mapped out the developer power creep from the beginning: minor gameplay disruptions, then devs giving themselves RPGs, then MaD-funded riots, then pushing out O5 members. mizi305 tried to point out that the ISS intel channels were "90% OSINT, so publicly available information." Too nuanced. Got ignored.

V. The Pattern

Most of the general chat had been through this before. Third, fourth, fifth version of the same collapse. They knew every beat. violvz: "SCPF GENRE TRY NOT TO REPEAT HISTORY CHALLENGE DIFFICULTY: IMPOSSIBLE." yourmotherisill: "ITS LEGIT THE SAME SHIT BRO." exerminos wrote multiple paragraphs about how the PSIA training system was the same overcomplicated mess that tanked previous groups. Nobody was surprised. These are teenagers rebuilding the same institutions, watching them blow up, and doing it again six months later with a new name and half the same people.

Nobody talked about the obvious part. The server was supposed to expose a surveillance operation that built files on minors. Within minutes of going live, someone reposted a doxx. _beyond_1: "Are people genuinely braindead they come in this server to complain about ISS' actions and then proceed to dox people." MaD informants were reportedly in the chat. Mods had to step in on racism and threats. A server built to expose overreach reproduced it on day one. The peanut gallery had commentary on everything except that.

On February 23, hours after the ownership transfer was finalized, two internal documents surfaced in Pathos Leaks that reveal the full scope of failed negotiations between Pathos-III's new leadership and unnamed.games. A statement addressed to the Manufacturing Department and a formal eighteen-section separation agreement paint a picture of a deal that came remarkably close to completion, then collapsed entirely.

According to the MaD statement, authored by Toximay, three candidates were put forward for the administrator role in succession. Luxxe was the first. His candidacy was blocked by devSparkle within twenty-four hours, followed by his suspension from unnamed.games. Daxrentha then narrowed the field to two people he would accept: Toximay and Mario, both of whom had been involved in Pathos since its inception. The two came to a mutual agreement, with Daxrentha's support, that Toximay would become Administrator and Mario would serve as Chairman of the Council.

devSparkle initially signed off on the arrangement, but only under conditions that would preserve what Toximay described as "overextended control" over Pathos. Two sticking points emerged. Toximay refused to allow Pathos to operate as a sub-studio of unnamed.games, and he refused to let the group's intellectual property be owned by anyone other than Pathos's own governing body. A middle-ground partnership agreement was proposed. Then silence: from February 12 to February 17, devSparkle went completely radio silent despite daily outreach from Toximay and Mario.

The Separation and Mutual Release Agreement, a formal legal document between Krescent (representing Pathos-III) and unnamed.games, laid out the proposed terms in detail. Pathos-III would retain all branding, Roblox group assets, Discord servers, game-specific code, and creative intellectual property. unnamed.games would keep its proprietary backend frameworks, server architecture, and reusable code libraries. A sixty-day transition period would keep existing infrastructure running while Pathos migrated away from unnamed.games systems. In exchange, unnamed.games would receive ten percent of net Robux revenue for twelve months, after which all financial ties, operational access, and governance rights would terminate permanently.

The agreement was never signed. According to Toximay, devSparkle refused to engage productively during the silence period, spread false narratives claiming that Toximay and Mario were motivated solely by Pathos's revenue, and told Daxrentha he would shut the group down entirely if either candidate became Administrator. Following the promotion and access revocation on February 23, both the partnership agreement and the severance agreement were sent directly to devSparkle's email. He denied both.

With no deal reached, the game was taken down for a full evaluation. The mutual release clauses, covering non-disparagement, non-interference, and formal dispute resolution, never took effect. The MaD statement closed with a direct address: Toximay wrote that he had spent hours planning a successful transfer, days drafting contracts, and nearly every day reaching out to devSparkle. He condemned the resulting situation as one that put "dozens and dozens" of developers in an unfair position and called devSparkle's actions "completely unprofessional, immature, and way below the standards of what creators at this level should be doing."

Daxrentha officially resigned as founder and administrator of PATHOS III on February 23, 2026. In a server-wide announcement tagged @everyone, he wrote: "After 8 long years in the SCP Genre, and servicing 6 of those years to Pathos, I'm finally handing in my final notice to the Foundation and genre as a whole."

Dax — Official Notice of Resignation, 23 Feb 2026 at 2:14 AM

In the resignation, Daxrentha confirmed the handover to Toximay, calling him a long-time friend and associate. He noted that Toximay previously served as his Council Chairman in an older group. Dax attached "My Way.mp3" alongside the announcement.

Toximay, Council, OOTC — Transition announcements, 23 Feb 2026

The O5 Council endorsed the transition. A council member stated they had "spoken to him on several occasions and have already had prolonged discussions regarding the group and its future," expressing faith in Toximay's ability as group owner. The OOTC also thanked Daxrentha for his years of service, noting that "without him pathos would literally not be here."

Just thirteen minutes after Daxrentha's announcement, at 2:27 AM, devSparkle forwarded an @everyone message in Pathos Leaks declaring that "following the unauthorized transfer of the group, unnamed.games is beginning the process of shutting down Pathos operations." He asked members to leave, calling membership in both MaD and unnamed.games "incompatible." Hours later, at 6:06 AM, he posted a final farewell in the official Pathos server: "Well, people — it's been great to have been a small part of creating this community we all love. I could stay here answering questions all day, but there's nothing left for me to create here." He then left every PATHOS-related Discord server. By 11:39 AM, Toximay confirmed the departure: "Well dev has left all Pathos related discord servers." That same morning, Curbalas published a Manufacturing Department document detailing devSparkle's misconduct, followed by a related contract that afternoon.

In the general chat, the community processed the fallout in real time. metaclasscat, the Lead Developer, confirmed the immediate damage: "all of dev's assets are gone." curbalas pushed back against the narrative that the game was finished: "MaD is not ungms" and "developers are developers, not assets of ungms." postputrid summarized the entire sequence of events with surgical sarcasm: "unauthorized owner detected, initiating firestorm, all unnamed resources pulled 🤖."

Toximay released a companion document titled "The New Pathos," laying out his vision for the organization under new leadership. In his server announcement at 10:24 AM, he wrote: "Today marks a crucial moment in our history." He also opened a #toximay-qna channel for community questions.

Toximay — "The New Pathos" announcement, 23 Feb 2026 at 10:24 AM

Toximay — "WE ARE SO BACK" graphic, 23 Feb 2026 at 12:39 PM

Within a day of Daxrentha agreeing to step down, a second crisis opened. devSparkle, the head of unnamed.games and PATHOS III's lead developer, moved to consolidate control. Through unnamed.games, he operated the group's game infrastructure, Discord bots, and hosting, and held a contract that gave the studio "ultimate control over safety matters, anything that may breach ToS or involve legal matters." Toximay had already been chosen as successor, but devSparkle's grip on the game's technical infrastructure meant he could hold the group hostage, threatening to take the game private, pull unnamed.games scripts, and shut down operations entirely if the transfer proceeded without his approval.

On February 8, Pathos Leaks pivoted from its original focus on ISS to a new target. According to an account by Cassin2, devSparkle and MaD leadership, together with Daxrentha, had "attempted to forcefully place members of MaD management within the Council, without any vote." The accusation was direct: "Since Daxrentha has to listen to devSparkle or else he cuts the support for the group (which he has threatened to do multiple times), he has been basically holding the group hostage for ages now."

In the weeks that followed, devSparkle systematically blocked candidates that both the O5 Council and Daxrentha wanted to succeed him. Mario, Luxxe, and Toximay, all trusted figures with long histories in the group, were each rejected. devSparkle's stated reason for maintaining control was code security: because Roblox development was his full-time income, he argued that trusting anyone else with the codebase was an unacceptable risk. But critics saw it differently. Cassian framed the contradiction clearly: "If you can't trust the administrator you're appointing with the codebase — something you trusted Dax with — I think there's an issue."

Cassian — @everyone post in Pathos Leaks, 23 Feb 2026 at 11:26 AM

The community drew its own conclusions in real time. In the Pathos Leaks general chat, the word puppet became the defining framing. 0ni0n. asked bluntly: "why is it up to you and why wont you install a puppet." Cassianor_ drove it home: "So not only does dax partially own the IP, and fully own the group, now you are trying to make it so the next administrator owns neither and is a puppet." _keystone. went further: "Development shouldn't have more of a say in administration than other departments lmao, what you're proposing is packing the council with MaD to push your own agenda at everyone else's expense." When devSparkle insisted he would never install a puppet, weeks of subsequent events suggested otherwise. User yourmotherisill summarized the community's skepticism during the Q&A: "we gonna have some dude limited so hard he's just gonna be dev's puppet." Meanwhile, ccoovert_88457 kept hammering a question that never got a straight answer: "why hasn't ungms pulled out," asked five separate times over the course of the afternoon.

A detailed postmortem by Goxuan laid out the financial dimension. devSparkle had reportedly collected "at least $1,000 to $2,000 a year if not more" in hosting costs. Goxuan, himself a website host, estimated actual costs at "no more than $10 a month for a simple discord bot and in-game integrations," rising to at most $20 per month with a large database. The gap between claimed and likely costs became a recurring point of skepticism.

The February 9 debate between devSparkle and Arkzockt further eroded his position. Community polls, with over 100 voters, sided against him on every question. His criticisms were rated "partially valid but overstated" by 72% of respondents. Toximay, the fact-checker who would ultimately become the new owner, was widely credited with running a fair process.

By mid-February, Cassian described "complete radio silence for days" on the ownership transition. Behind the scenes, devSparkle continued to stall. Then, on February 23, Daxrentha bypassed the impasse entirely and transferred ownership to Toximay.

devSparkle responded just thirteen minutes later, at 2:27 AM, by forwarding an @everyone message in Pathos Leaks declaring that "following the unauthorized transfer of the group, unnamed.games is beginning the process of shutting down Pathos operations." He asked members to leave, calling the transfer a leak of unnamed.games content to "an unauthorized party" and declaring that "membership in both MaD and unnamed.games is incompatible." He closed the forwarded message with: "It's been an absolute delight to work with every single one of you. Godspeed."

devSparkle — Forwarded shutdown message in Pathos Leaks, 23 Feb 2026 at 2:27 AM

Hours later, at 6:06 AM, devSparkle posted a final farewell in the official Pathos server: "Well, people — it's been great to have been a small part of creating this community we all love. I could stay here answering questions all day, but there's nothing left for me to create here." He then left every PATHOS-related Discord server. By 11:39 AM, Toximay confirmed the departure with a single sentence in Pathos Leaks: "Well dev has left all Pathos related discord servers."

That same morning, at 11:11 AM, two internal documents were published in Pathos Leaks: a statement from Toximay to the Manufacturing Department detailing the failed negotiations, and an eighteen-section separation agreement that had been offered to devSparkle and rejected. For a detailed breakdown, see The Rejected Deal.

On February 9, two days after the ISS leak triggered mass resignations, Pathos Leaks hosted a live text debate between devSparkle, the head of unnamed.games and PATHOS III's lead developer, and Arkzockt, a former O5 Councilor. The debate was moderated by Cassian (cassianor_), the Pathos Leaks operator, with Toximay serving as a neutral fact-checker verifying claims in real time. The session ran for approximately three hours.

Cassian structured audience participation through reaction emojis on key statements (fire for agreement, other reactions for disagreement or uncertainty), allowing the community to weigh in as the discussion unfolded. Over 100 members participated in the subsequent polls.

In the general chat running alongside the debate, the energy was equally chaotic. When devSparkle argued that leaked code would affect his family and livelihood, user rokuw copy-pasted the line sixteen times in a row, turning it into an instant copypasta. totallynotmoo offered a broader assessment: "you might genuinely be on the mount rushmore of the scpf genre, and i dont mean that in a good way." maxaot struggled to take it seriously at all: "The heck does it mean 'Live commentary' it's a lego game debate." And as the emoji reactions piled up on every message, _.exa made a meta observation that briefly stopped the chat: "These emojis are killing independent thinking."

devSparkle opened with pointed criticism of the O5 Council. He called O5 members "just department SC4s with more power, and less responsibility," and maintained this position throughout the evening. He argued that unnamed.games' control over the codebase was a matter of personal livelihood, stating "if that code is leaked, it actually affects me and my family" since Roblox development was his full-time employment. He accused Arkzockt of leaking internal MaD management messages, though the evidence was never conclusive. Toximay rated the claim as "not incriminating but strongly suggests." A community vote on this specific point went 50 to 2 against devSparkle's characterization.

devSparkle also directed attention toward the ISS controversy, arguing that Arkzockt and other councilors who had access to the ISS Discord bore responsibility for not reporting what was happening inside it. "Isn't it funny how everyone's reply is always 'I didn't see anything, I didn't hear anything'?" he said. "So if no one saw or heard anything, who did all the bad things?" This line received 62 fire reactions, his strongest moment. But he followed it with a garbage dump analogy. "If I drive to a garbage dump, I may not know every piece of garbage, but I sure as hell know I'm in the middle of a damn garbage dump." That received 41 disagreement reactions against just 5 in support.

Arkzockt countered that he had been excluded from a key group chat where his own removal was being discussed, without evidence and without being told. "Y'all literally discussed my removal in there and now after that shitshow you're saying I might be innocent," he said. He acknowledged minor admin abuse but characterized it as trivial: "I never said I didn't abuse admin and honestly I found it funny. But they never suspended my admin perms because it wasn't that bad." He pressed repeatedly on "innocent until proven guilty," pointing out that devSparkle continued to make public claims without presenting evidence.

The remaining O5 Councilor, amplelyric1327, pushed back against the suggestion that all councilors were complicit in ISS abuses. "This is a stupid point. Put bluntly. I am not omnipotent. And I have a life," he said. "To undermine all of my and Turn's work in the SCPF because we don't have the sixth sense is absurd."

One of the debate's most scrutinized moments came when Toximay fact-checked devSparkle's claim of having "resigned from head" of MaD. Toximay's ruling: "The verbiage 'I resigned from head' is deceptive." Cassian added bluntly: "So dev lied, he resigned from MaD... Not 'from head.'" devSparkle responded that his statement "wasn't false, it was wrong. There's a difference," a line that received 30 disagreement reactions.

Luxxe, a former Lead Developer, delivered a closing statement: "I have felt pretty offended by not only dev's actions the last few days regarding me but also by his assumptions about my character. Instead of figuring out my perspective, I was immediately suspended after my 2 years of service to the group."

After a 24-hour deliberation period called by Toximay, formal polls opened on February 15. Over 100 community members voted on six questions. Arkzockt won every poll decisively.

On the morning of February 7, 2026, Pathos Leaks, a separate organization led by cassianor_, published its first release: a server archive from PATHOS III's Internal Security Service (ISS). The stated objective of the leak operation was direct. "One of the fundamental pillars to resolving the current issues is to remove Daxrentha," Cassian wrote in the site's launch announcement the day prior.

The ISS data revealed intelligence-gathering activities, internal communications, and most critically, that the service had been collecting personally identifiable information (PII) on community members. Among the findings, Pathos Leaks alleged that ISS member MapleNoodle had stored a suspected image of a minor in the server. Cassian called for the ISS to be disbanded immediately, and external groups began issuing their own condemnations. cubvul invoked the ISS's own tactics against it: "The Internal Security Service initiated a blacklist onto UNKNOWN and the entirety of their Foundation. Now it is time for them to face the same punishment."

The general chat's reaction was immediate and blunt. sirvmp set the tone within minutes of the first leak: "dudes really doxxing over a lego game." The sentiment echoed for hours as the scope of the PII collection became clear. nicholasio_0 put it most memorably: "remember when we played a lego game to have fun and not doxx children." anoobisdead pointed out the escalation that most people had tried to ignore: "some ppl thought i was taking ts too serious yet they ignore the mfs sending ppl bomb threats over a lego game." hawkalex summed up the evening with a line that stuck: "The larp was too serious for a lego game."

Within hours, the ISS was abolished by direct order from Daxrentha and the O5 Council. ryan977 confirmed the dissolution at 10:09 PM: "Yes, as of a few minutes ago, ISS has been disbanded. No, MaD Command did not decide to do this." He separately called it "the most disgusting thing I've ever seen in this group."

What followed was an extraordinary chain of resignations, all compressed into a single evening. At 7:40 PM, .samington stepped down: "It's been a good 5 years, Pathos." At 8:13 PM, Whaleclam, the recently elected Chairman of the Council and former ISS Overseer, resigned. He admitted to negligence, stating the ISS server "contained some personal information" that was "unbeknownst" to him, and that "none of said personal information has ever been used for any purposes." At 8:16 PM, owenlma0 resigned all positions.

By late evening, only two O5 Councilors remained: Turntapp and amplelyric1327. Turntapp issued a statement at 10:16 PM calling for Daxrentha to relinquish ownership. It was raw: "This group has lost so much fucking potential due to absolute stupid ass fucking decision making at the top it should shutdown rather than spend another day without a fresh head." He added: "Anyone who has committed any sort of doxxing or engaged in acts that harm community members especially children you are a fucking insufferable stain on this world and I wish you the worst."

Just over an hour later, at 11:21 PM, Turntapp confirmed: Daxrentha had agreed to step down. The crisis had escalated from the first data drop to the founder's commitment to leave in roughly fourteen hours.

In the middle of the turmoil, mrmediocre3 posted what became the evening's most shared aside: "Hey guys fyi this is a Roblox roleplay game, lets chill out a little please jesus."