Introduction
Anthony Gordon Brodie (Soul) built his name in the DayZ console scene by making tools that let server owners run communities at scale without needing a developer on call. His primary creations include DayZ Multi Tool (a widely-used Discord bot) and later Legion Killfeed (a subscription-based killfeed service for DayZ console servers).
The Original Name Story: Legion's first version, created on 25 October 2020, was originally intended to be named "The Soul" - "Because it'd be the soul of every DayZ discord" was Brodie's exact explanation when asked about the name in 2021. From day one, the development philosophy prioritised security (Nitrado API tokens isolated to prevent abuse), transparency (every system action logged), and reliability (consistent updates and support).
That work put him in the middle of a niche but intensely competitive market where small groups often tried to win customers by discrediting rivals. Long before the campaign later aimed at Brodie personally, the killfeed scene already had a visible pattern: developers accusing each other of theft, baiting server owners into drama, and using Discord as the main battleground.
This document chronicles a sustained harassment campaign that escalated from business disputes into doxxing, death threats, suicide encouragement, weaponisation of children's images, and coordinated defamation across multiple platforms.
Part One: The Early Years (2020-2021)
2020: A Market Built on Intimidation
In February 2020, the pattern of competitive harassment was already clear in private messages circulating among server owners.
On 7 February 2020, one server owner described being contacted by Ronald Lund (Jarvis), who presented a killfeed as something that required a paid monthly arrangement, only for the owner to conclude it was a scam and thank Jeabers Killfeed for warning people.
By 24 June 2020, Jeabers Killfeed was messaging its own users directly about Jarvis, telling them that if Jarvis contacted them to remove Jeabers, he was "scamming you" and had "nothing to do with this bot."
For Brodie, those early warnings mattered because they showed a market where persuasion and intimidation were already being used as business tactics, and where public trust could be attacked as easily as the software itself.
2021: Rising Visibility
By 2021, Brodie had built DayZ Multi Tool into a widely used Discord bot, and his Aggro PVP community (which he had been running since 2018) had become a central hub for console DayZ players. That visibility made him harder to ignore and easier to target.
August 2021: The "Masterpiece" Handoff
In late 2021, when Brodie stepped back from a development role for one community, he did not vanish quietly, on 26 August 2021, Brodie demonstrated the ethical conduct that would later be weaponised against him. After working as a developer for the Accolade PVP servers, Brodie decided to step down. Rather than abandon the project, he personally arranged for GBSHOTSx3, a top community coder, to take over his duties.
In Discord messages, Brodie explained his requirements:
"Their list is so specific cause that is one of my coding requirements, exact and precise to guarantee the best work... Here's Accolade's files if you want to take a look at what you could end up working with, that server is one of my masterpiece, I'm sad to pass it on but I can't keep up with the work with these two jobs."
Brodie's handoff: he called the codebase his βmasterpieceβ and personally arranged a complete handoff rather than abandoning the server. That conduct directly contradicts the later accusation that he intended to damage the project.
28 August 2021: Crix uses a third party's identifying data in an intimidating exchange
The newly supplied Discord capture shows Crix Madine Jr. challenging another participant to have a friend leave a halfway house and visit him in Courtland. Crix then posts a structured personal-information record containing the first name Louie, the visible location Armagh, GB-United Kingdom, and partially obscured surname, company, email, street address, postcode, phone and IP fields. He closes with βMUST SUCK TO SUCK.β The archive preserves the intimidating use of the record without reconstructing or exposing the values that are obscured in the source image.
October 2021: Direct Threats Begin
The hostility sharpened in October 2021.
On 10 October 2021, Jarvis began attacking DayZ Multi Tool publicly, including claiming ownership of Brodie's work and accusing others of copying.
The next day, 11 October 2021, the tone shifted from petty claims to direct intimidation. A set of messages, logged as being purged by an automoderation bot, included lines aimed at Brodie such as:
- "Play games you get burnt"
- "We coming for you boy"
That same day, Brodie submitted a report to Discord identifying Jarvis's server and describing a broader pattern: admitted code theft claims, fake images used to discredit competitors, and Discord being used to take money from server owners under false pretenses.
October 12, 2021: Community Response
DayZ++ developers (Jon J/Hoks) became involved, planning to release free alternatives to counter Jarvis's fraudulent business:
Jon J: "Hey, DayzKillfeed is accusing me and my feed of hacking him as well. Because I made a website exposing him... DayZKillfeed.NET: Statement regarding Jarvis/DayZKillfeed.COM, and soon to be free Killfeed... And mass emailed it to all his clients."
Jon J: "His server costs will be more than he's making when I'm finished with him. His entire bot is about to become free on GitHub."
The response pattern: the 10β12 October sequence established what followed: exposure of misconduct was answered with threats, retaliation and attacks on the person presenting the evidence.
December 2021: The Vigilante Resolution
A third-party group of vigilante coders known as DayZ++ took matters into their own hands. Using OAuth abuse techniques, they gained unauthorized access to Jarvis's private Discord server and obtained video proof that Jarvis had cloned Brodie's DayZ Multi Tool code.
On 10 December 2021, DayZ++ staff recorded themselves using an OAuth invite flow to get into DayZKillfeed.com's Discord without being invited, framing it as "getting the evidence we wanted."
Caught red-handed with undeniable evidence, Jarvis agreed to a truce: he would cease attacks if Brodie removed his exposΓ© website. Brodie complied, wanting peace. However, Jarvis didn't truly stop - he simply went quiet.
December 2021: FTP Accusations & Exoneration
Around the same time, another incident became important for later context. Accolade PVP (a server Brodie had previously managed) had critical files deleted via FTP. Immediate suspicion fell on Mathew Trojanowski due to his access and alignment with Azzy (a former Accolade staff member).
Critical Exoneration: The server owners (GreedyPeasant and PissedOffTexan) publicly stated Brodie had protected their project and arranged proper handoff - he would have no reason to harm it.
TheGreedyPeasant explicitly told Brodie: "Never said ya did" when Brodie was accused of hacking past 2FA.
This context becomes crucial when Trojanowski later attempts to rewrite history and blame Brodie for the very FTP sabotage Trojanowski was accused of.
Part Two: 2022 - Burnout, New Alliances, and the First Doxxing
April 2022: The Pedophile Smear Tactic Emerges
Private conversations from April 2022 show Brodie discussing Mathew Trojanowski as someone he believed could stir up trouble while staying just inside the lines of what platforms would act on.
In those same discussions, there were already mentions of pedophile smears being thrown at people as a weapon in community disputes. That was not yet the sustained campaign it later became against Brodie, but it showed that the tactic existed and was circulating among the same overlapping groups.
The smear tactic: the βpedoβ accusation was already being used as a weapon in the same overlapping community before it was directed at Brodie. Its later use against him followed an established smear tactic rather than a genuine safeguarding concern.
April 2022: Jeabers Stats Crisis
On 5 April 2022, Brodie discovered stat manipulation affecting Jeabers Killfeed's global leaderboards. Cheaters were exploiting the system to claim #1 positions overnight with impossible stats (1000m shotgun kills).
Brodie publicly demanded fairness for all players:
"@Jeaber I ask again how is this dude always on top with one weapons damage that isn't a real weapon?... Going through his stats he has 1000m shot on nearly every weapon and some like a BK133 SHOTGUN with 1000m kill. Something dodgy is going on."
Jeaber's dismissive response: "I don't care nothing I can do about it... the only stats and leaderboards you should care about are the ones on the server you manage."
Brodie's character-defining response:
"As a server owner with 3x servers in the Top 15 servers for kills on your leaderboard, I will of course be questioning the integrity of your killfeed when a cheat can be #1 overnight... Some customer service/satisfaction you offer."
This incident demonstrated Brodie's consistent pattern: advocating for fair play and integrity even when it meant challenging powerful figures in the community.
June 2022: Crix's Documented Hypocrisy
On 1 June 2022, Edward "Crix" Griggs Jr. was caught displaying stunning hypocrisy. In private messages to a former friend (Famin), Crix acknowledged how traumatizing doxxing and family harassment can be:
"That's just so much trauma that I would not want to put through our daughters heads dude."
Yet this empathy was two-faced. Within a year, Crix would be actively sharing photos of Brodie's children in harassment campaigns, demonstrating he understood the harm yet chose to inflict it anyway.
July 2022: Tbag Blames Trojanowski's "TC" Brand for FTP Sabotage
On 15 July 2022, Tbag (DayZ Madness server owner) refused to help Kamikaze with a mod request, explicitly blaming Trojanowski's "The Collective" (TC) brand for destroying his server files:
"I will not help because Azzy destroyed all my work and Greedy's server out of spite under the TC name."
When Kami claimed he "had nothing to do with it," Tbag elaborated that deleted files were marked with "TC" - Trojanowski's brand. This contemporaneous accusation establishes that FTP sabotage was associated with Trojanowski's circle before he ever blamed Brodie.
August 2022: Aggro PVP Reaches Global Ranking
By 1 August 2022, Brodie's Aggro PVP servers had reached the top ranks on Jeabers Killfeed's global leaderboard, tracking 2,020,719 players across 8,276 servers:
- Aggro PVP NWAF: 3rd place globally with 821,096 total kills and 58,034 players
By 17 October 2022, Aggro PVP NWAF had climbed to #1 globally with over 1,075,506 kills.
Brodie recalls posting a screenshot of this achievement in BigFatMods Discord with the "I'm the captain now" gif. This is what seeded Edward "Crix" Griggs Jr's resentment - BigFatMods sat at #4 on the same leaderboard. The competitive jealousy that would later fuel Crix's harassment campaign began here.
August 2022: Trojanowski Blames Azzy for FTP Attacks
On 29 August 2022, Mathew Trojanowski sent unhinged messages to former associates, explicitly blaming his ex-partner "Azzy" for the FTP file deletions he would later attribute to Brodie:
"You know I never deleted a single file. If she didn't block me maybe she could have gotten the email I got about data loss on the LA network that caused the files to delete."
"You can say you have witnessed it but just so you know she slandered me deleted the files to make her look like she didn't do anything. Did you know she did the same thing to greedy and then denied it? I bet you didn't."
In the same message chain, Trojanowski made disturbing admissions:
"You do realize I already have all your files for the new Server's on the new Nitrado correct. Funny how a multi billion dollar company can miss such an old school exploit."
"I've attempted to kill myself 8 times in the last week and I have no motivation anymore."
Critical Timeline: In August 2022, Trojanowski blamed "Azzy" for FTP sabotage. One month later, in September 2022, he fabricated a screenshot to blame Brodie instead. The target changed; the accusation stayed the same.
September 2022: StockyAcrobat's Warning
On 9 September 2022, a user named StockyAcrobat sent Brodie a direct warning about Mathew Trojanowski's harassment patterns affecting other servers. The warning described Kamikaze copying Discord profiles and spamming fake links to discredit competing server communities:
"Soul I just wanted to let you know if a link to our discord channel starts spamming your channel its not us here at Skulls'N'Roses. Kami the Owner of the Collective is making up fake discords that look like our profiles and spamming other discords to try and Discredit the Skulls'N'Roses server."
"This guy is meant to be a name in the dayz community and if you are rubbing shoulders with him I suggest you distance yourself from this low life now."
Brodie, having experienced misinformation from multiple directions, chose not to act on the warning - a decision he later regretted.
October 2022: Breaking Point
By October 2022, Brodie's Aggro PVP work reached a breaking point.
In Aggro PVP Discord messages dated 19 October 2022, Brodie announced he was done, saying Aggro PVP was "officially over" and that he could not keep grinding through thousands of line-by-line changes.
Context on Brodie's situation at this time:
- He had recently quit drinking after 8 years of daily alcohol abuse
- He was working two jobs - over 42 hours a week
- He was simultaneously modifying DayZ servers, providing support for other server owners, maintaining his DayZ Multi Tool Discord bot, and moderating several Discord servers
After that step-down, Trojanowski offered to cover Aggro PVP's operating costs and handle the full map server. Brodie stayed on as administrator and continued running the deathmatch infrastructure. Trojanowski also told Brodie he would give Aggro back if Brodie asked for it.
November 2022: The First Doxxing
On 23 November 2022, Mason Lewis Stockton (Links, Havasu) doxxed Brodie by leaking footage that revealed Brodie's home address.
Soul: Hey gorgeous - What the fuck is Link's deal? Brumzy: I dont know who links is tbh I know all the other cunts not him unless its an alt of someone's Soul: Idk who it is but they have been in a party with me... he's good mates with Sife... Brumzy: Either drift balls or coastal then I would say one of the later two would be my guess probably balls... Soul: In the email there was like 93 discord links to the messages that were about me, every single account that had talked shit about me, Aggro PVP, anything at all related to them breaching discord ToS, 118 screenshots, it was a lot lol Brumzy: ππ are they looking into it then I take it, Cause thats alot of evidence
That same day, after Mason had already been block-evading and escalating into doxxing behaviour, Brodie filed a Trust and Safety report with Discord. This was the rare exception where Discord enforcement meaningfully landed.
Critically, Discord's Trust and Safety team thanked Brodie for providing screenshots and user IDs and explicitly encouraged that evidence format. The report was submitted via email with attached documentation - and it worked.
Someone in the community announced that Soul's report had resulted in Links' account being disabled and that every account associated with Mason's IP address had been disabled as well.
In the middle of years of reports, evasion, and recycled harassment, this IP-linked disablement stood out as the only clear example of Discord taking the problem seriously enough to cut off the churn of new accounts - at least temporarily.
26 November 2022: Code Scraping Behaviour
On 26 November 2022, Trojanowski casually admitted to scraping code from another developer's GitHub repository.
When Brodie noticed the killfeed code looked familiar and asked if it was from Vic's GitHub, Trojanowski's response was matter-of-fact:
"Maybe. it's okay though... I might have scraped it from github." - Kamikaze
This established early in their partnership that Trojanowski treated other developers' code as resources to take without attribution - a pattern that would continue when he later stole Brodie's own code.
Late November 2022: Trojanowski's Methods Exposed
On 27 November 2022, Trojanowski openly described:
- Piecing together a Discord bot from scraped GitHub code
- Using automation to generate negative reviews
This established a documented example of Trojanowski treating other people's code and other people's reputations as raw material to be assembled into something useful for him.
End of 2022: A Dangerous Position
By the end of 2022, Brodie was positioned in a dangerous overlap:
- He had a successful public identity tied to multiple projects
- The competitor scene was already comfortable with scams and intimidation
- His new "helper" in Trojanowski had documented comfort with scraping code and manipulating reputations
The following year would turn that overlap into a sustained campaign.
Part Three: 2023 - The SkyNet Split and Retaliation Begins
January-February 2023: New Project Begins
In late January/early February 2023, Jeabers Killfeed closed down mysteriously with no word from the developer.
This was notable because Jeabers Killfeed was the only console killfeed bot that had a global leaderboard. Brodie's servers were in the top 10 servers for kills and players, with one server being #1 with over 2 million kills and over 100,000 unique players.
This is when Brodie decided to create a new global killfeed: SkyNet Killfeed.
The collaboration began with Anthony Gordon Brodie (Soul), Mathew Trojanowski (Kami, Kamikaze420, Skynet), and Cody (Stojo25, SaltySilver). The roles were never formally defined but they were discussed - Brodie recalls that Cody avoided the discussion while Trojanowski said talking about money felt "icky."
Trojanowski tried to position himself as the operator and front-facing owner figure, but to anyone who was using the bot or in the bot's Discord, Brodie was the person people leaned on when things needed to be built, fixed, or explained.
Over the next few months, the same contradiction kept repeating. Trojanowski publicly spoke like the technical lead, but privately he kept asking Brodie for help with basic configuration and bot maintenance. That gap became more than an ego problem - it became a money and ownership problem, because the more SkyNet looked like a product, the more Trojanowski treated ownership as a given, even while relying on Brodie to keep it alive.
Context preserved from early 2023: Alongside the technical build, Brodie also preserved screenshots from adjacent competitor/community spaces that he says show early signals of the later pattern: status games, narrative positioning, and hostility that existed in parallel to the "partnership" story. These items are included here as context (not as a substitute for the later, dated platform reports and takedown attempts):
- 2023-02-06 screenshot compilation (labelled: "malicious intent masked as friendliness")
- 2023-02-11 image ("Jarvis - Community Opinion")
- 2023-02-11 taunt screenshot (Jeabers/competitor context)
- 2023-02-11 image (labelled: "Joel Walker's Obsession for Soul")
- 2023-03-26 screenshot ("passes drug tests")
- 2023-05-20 screenshot ("plans to rip off / copy another bot")
- 2023-06-09 screenshot ("username change could likely snag dayzkillfeedcom")
February 2023: Joel Walker's Early Obsession
On 18 February 2023, Joel Walker (Jack Jackalope) initiated hostile contact with Brodie over competitive rankings. Walker's servers appeared on the same leaderboard page as Aggro PVP, which triggered confrontational messages:
Jack Jackalope: "Alright then idk why I'm on the first page with you on the leaderboard with both my servers"
Jack Jackalope: "im just gonna block the drunk blabbering"
Soul: "Aggro PVP, proof that coding is so easy, a drunk can do it."
This exchange documents Walker's resentment toward Brodie began as simple competitive jealousy over rankings - the same motivation that would later fuel sustained harassment including false pedophile accusations in October 2025.
February 2023: Trojanowski's Discharge Plot
On 26 February 2023, Mathew Trojanowski showed Brodie a disturbing example of his approach to conflict resolution. Someone had sent Trojanowski threatening messages with photos of weapons and a sign reading "Kami is a cum guzzler."
Trojanowski's response wasn't to report it to authorities - it was to plot retaliation using the sender's visible military uniform:
Kamikaze: "Guy sent me hate mail and threats. Guess who's just gonna spread this along social media. Shouldn't post your uniform with name and dog tags. The military won't take this well. Fastest way to get dishonorably discharged."
This revealed Trojanowski's willingness to pursue real-world consequences for online disputes - the same approach he would later use to target Brodie's family, employment, and reputation.
April 2023: The Wedding Test
On 9 April 2023, Brodie flew interstate to attend his brother's wedding. During his absence, the bot constantly crashed. Trojanowski and Cody (SaltySilver) - who had full access as staff - couldn't keep it online.
Brodie returned and immediately had the bot working again.
This incident demonstrated that Brodie was the indispensable technical force, not an equal partner but the actual owner and developer.
20 May 2023: Pattern of Copying
On 20 May 2023, Trojanowski revealed his approach to developing features wasn't to build from scratch, but to identify existing tools and copy them.
Discussing another developer's bot, Trojanowski outlined how to replicate it:
"He's got a cool bot not gonna lie... We definitely could make these this. With this bot. It's in JS so he's gonna run into a size limit with Python we don't have that issue." - Kamikaze
When Brodie noted he'd never heard of the developer despite four years in the scene, Trojanowski dismissed this - already planning the copy.
This wasn't an isolated incident. Combined with the November 2022 admission of scraping Vic's GitHub, it established a pattern: Trojanowski's "development" meant identifying what others built and reproducing it.
12 June 2023: Warning Signs
On 12 June 2023, just days before the SkyNet split, Mathew Trojanowski shared password-cracking resources in Discord and talked openly about using them to recover a Windows password - showing comfort with the idea of breaking into locked access, right as trust was collapsing.
June 2023: The Breaking Point
By June 2023, the disagreement turned into a direct confrontation about contribution and control.
On 23 June 2023, an independent third party with 9+ years of bot development experience reviewed the contribution history and confirmed: 70.9% of the overall work was done by Brodie, with Trojanowski and Cody (SaltySilver) contributing minimally.
Brodie pushed for a simple standard: equal ownership only made sense if the work was equal. When Trojanowski refused both a formal partnership structure and a consultant-style arrangement, the relationship snapped.
24 June 2023: The Split
On 24 June 2023, Brodie:
- Pulled his source code and databases out of shared access
- Announced he would continue independently
- Wiped shared resources afterward
- Moved forward under the Legion Killfeed name
Less than a minute after Brodie left the Aggro PVP Discord:
- His independence announcement was deleted (35.8 seconds later)
- People were talking in voice chat about backups of his code
Jacob "RB SKIZZA" Stoppard overheard Cody and Trojanowski discussing "their back-up of Soul's code" in a voice channel.
Late June 2023: Evidence Preservation
On 26 June 2023, two things happened:
First, Trojanowski announced Skynet Killfeed was "back by popular demand" and claimed the code had been "completely rewritten" - an astonishing turnaround for someone who couldn't spawn the right item in-game without help.
Second, Brodie documented discovering that Trojanowski had been running Brodie's files through ChatGPT. A captured prompt showed Trojanowski's email visible as he asked the AI to generate a copyright notice for a "Discord bot called Skynet Killfeed using the Nitrado API."
Brodie's reaction was blunt:
"The guy who can't spawn the right item in game rebuilt a bot overnight... ChatGPT with my code isn't rewriting it... Even using my server's logfiles. 100% my code still."
July 2023: Customer Sabotage
On 5 July 2023, brumzzzzzy contacted Brodie in distress after discovering Mason Stockton (Links) had followed him to a PC server and obtained a trial admin position:
"He's on PC now and trial admin on server we playing like a fuckin stalker and he's got his cheating little twat mates on trolling the server."
Brodie intervened directly, presenting evidence of Links' history - including the November 2022 IP ban documentation - to the server admin.
12 July 2023: Contacting Customers with Lies
On 12 July 2023, Trojanowski began directly messaging Brodie's customers - including Lykos - trying to manipulate the narrative.
In DMs to Lykos, Trojanowski claimed:
"Soul fabricated all of this... lied, stole what I have... I've been getting death threats over this... He made a fake account to list my phone and personal info as Blackmail." - Kamikaze
The supposed "blackmail" evidence Trojanowski attached actually showed the opposite - Brodie confronting Trojanowski about stealing code:
"Stop the lies Kami, delete my goddamn code and write something yourself without stealing from everyone else... 33 channels of proof." - Soul
Trojanowski's claims of "personal info" being leaked were fabricated - the screenshot he shared contained no personal information, only evidence of Trojanowski's code theft and lies.
This is when Trojanowski revealed his September 2022: Fabricated Screenshot - using browser inspect element to fabricate a "confession" making it appear Brodie admitted to FTP sabotage he did not commit.
The fabricated message claimed Brodie said: "I only recently lost access to their FTPS, had 14 servers FTPs but I wiped my PC lost them. NWAF PVP is another one I fucked with..."
Critical Analysis:
- This "confession" was supposedly made to Mathew - the very person accused of the FTP sabotage by multiple victims
- Brodie never made any such statement to his own staff (Clover), who would have been the logical recipient of any genuine confession
- The FTP accusation against Mathew preceded this by nearly a year - including TheGreedyPeasant's December 2021 exoneration of Brodie
- Mathew previously blamed his ex-partner "Azzy" for this same FTP behavior - now conveniently redirected to Brodie
This fabricated screenshot became a key piece of "evidence" Trojanowski threatened to circulate to discredit Brodie.
July 2023: Infrastructure Attacks
On 14 and 15 July 2023, Brodie documented hostile activity tied to Nitrado.
Brodie captured an incident where:
- His Nitrado account was locked
- In-game messaging and Discord invite links had been altered to redirect players toward BigFatMods - a Discord owned by Edward Anthony Griggs Jr. (Crix)
Nitrado's Response Failure: Despite Brodie's immediate reports with screenshot evidence showing unauthorized file modifications with timestamps, Nitrado took 52 days to internally escalate and refused to conduct an adequate security investigation.
Late July 2023: Brand Confusion
By late July 2023, the fight had expanded into brand confusion.
Trojanowski's orbit was building an Aggro-themed presence that blurred the line between the community Brodie had built and the rival space that wanted his users.
August-September 2023: Pedo Smear Begins
In August and September 2023, the campaign shifted into something that looked less like a breakup dispute and more like a long-term harassment strategy.
The smear that would later dominate everything started appearing more openly during this period.
Brodie was being called a pedophile in conversation and in attacks - not as a claim tied to any evidence, but as a shortcut to disgust and mob logic.
17 September 2023: DDoS Threats
On 17 September 2023, Brodie preserved a conversation in which Trojanowski bragged about DDoS capability to a third party - a signal that the campaign was comfortable with technical attacks, not just reputational ones.
20 September 2023: Doxxing Website
On 20 September 2023, AggroPVP.com displayed:
- Brodie's residential address
- Language inviting people to "head over" to the address "for some fun"
That was not an argument about a Discord bot anymore. It was a doxxing threat presented as entertainment.
Brodie reported the domain to the registrar, Porkbun, and the domain was suspended on 21 September 2023. But days later, on 29 September 2023, Porkbun told Brodie the domain had transferred to GoDaddy, forcing Brodie back into the same loop of reporting.
8 October 2023: Technical Superiority Documented
Around this time, Brodie captured throughput data that demonstrated Legion's technical performance advantage. The comparison was stark:
- Legion: 124,665 messages processed in ~24 hours
- SkyNet: 118,000 messages processed in ~72 hours
That's approximately 3.2 times higher throughput for Legion. The data wasn't about bragging - it was evidence that when Trojanowski claimed he had "completely rewritten" the code and built something better, the numbers told a different story.
The person who couldn't spawn the right item in-game without help was now running a competitor that performed at one-third the speed of the code he'd had access to.
10 October 2023: DayZ++ Admin Warns About Jarvis Again
On 10 October 2023, hoks/Jon, who identified himself in the exchange as a DayZ++ admin and operator of DayZ Modding Bot, contacted Brodie saying Jarvis was "on copy strike again." He linked a 2021 "jarvis moment" video, said he had seen parts of Brodie's bot again and later specified that both Multi Tool and Legion or similar feed ideas were present.
Hoks supplied guild ID 1156290166911156324 and four Discord user IDs: 290048318707466250, 439466792855797760, 926252048847085628, 1131535608653807667. He sent them with the message, "Do what you wish with this info. If you wish to ban them," and labelled the list as King BHD, Saftladen, Jarvis and "some other acc." The supplied material did not independently establish that every ID on the list belonged to Jarvis or an associated account. Brodie asked which bot hoks meant and requested the guild ID rather than simply banning the entire list. Hoks said they had been locked out within about two minutes and had not managed to make a new video that time.
15 October 2023: Public Humiliation
On 15 October 2023, Brodie captured a Discord incident where Trojanowski and Griggs joined in public harassment that mixed technical intimidation with personal degradation and renewed pedophile accusations.
28 October 2023: DayZ++ Owner's History Exposed
On 28 October 2023, a conversation between Brodie and Lykos (a respected server owner from Conquest) revealed context about the DayZ++ operator that explained some of the hostility Brodie had experienced.
Lykos: "DayZ++ owner is perma-banned on Conquest because he mass-tkd back in 2021 lmao"
Lykos also noted that DayZ++ was copying Brodie's features: "One of blackout admins makes DayZ++. They're copying my features though." The pattern wasn't technical competition - it was personal antagonism wrapped in a developer veneer.
November 2023: Impersonation Spam
On 22 November 2023, Brodie documented a spamming event where an account using his Legion branding was posting across multiple unrelated Discord servers in rapid succession.
Brodie treated it as an attempt to manufacture a Terms of Service problem for him, because even if people did not believe he wrote the messages, the noise itself could get him flagged or banned.
25 November 2023: Fake Profile
On 25 November 2023, a Discord account styled as "Soul.dev" appeared with Brodie's brand attached and a degrading bio that called him a "trash" developer and pushed readers toward "legion killfeed."
The point was to make it look like Brodie was self-posting abuse or running a fake persona to smear himself.
12 December 2023: The Xanax Attack
On 12 December 2023, Carl-bot moderation logs show 100 messages being purged from a channel in a burst that included:
- Repeated reposting of an image of Brodie while sick
- Homophobic slurs
- Explicit sexual violence threats aimed at his partner and family, including threats that referenced his children
The offender, identified in the logs as Xanax, was banned minutes after joining.
Part Four: 2024 - Escalation to Family Targeting
January 2024: Death Threats & Child Targeting
On 8 January 2024, Brodie preserved:
- A message from a user threatening death
- A rape threat aimed at his partner and children
The language was graphic and deliberately cruel. It was not framed as "trash talk." It was framed as a punishment fantasy.
9 January 2024: Griggs with photos of Brodie's minor children.
On 9 January 2024, Edward Anthony Griggs Jr. (Crix) privately contacted one of Brodie's Discord moderators, known as Feather.
The exchange immediately turned into intimidation:
- Edward insulted Feather repeatedly
- Claimed he had her personal information "pulled up"
- Threatened that he would post her dox details soon
- Sent Feather images of Brodie's young children
- Taunted that "they are scared for their lives"
- Tied the children's photos into the ongoing "pedo" smear aimed at Brodie
Feather challenged the hypocrisy directly, pointing out that Edward was calling Brodie a pedophile while simultaneously keeping and sharing another man's children's photos - describing it as "a grown man saving kids that are not his in his photo album."
That exchange crystallised what made this campaign different from ordinary online hostility. It was deliberate use of a parent's children as an instrument of fear and humiliation.
14 January 2024: Nitrado API Whitelist Collaboration
While harassment continued on one front, professional recognition continued on another. On 14 January 2024, Nitrado staff (Aspirin+C) reached out directly to the Legion Killfeed team to address API rate limiting issues.
Aspirin+C: "hey there, normally i don't do DMs, so let's not make a big deal out of it, what IP are you using for your killfeed bot? how many requests over what period are you doing?"
The conversation showed Nitrado's internal team working to whitelist Legion's infrastructure, adding JayJay and other developers to their API access list. This wasn't a favour - it was recognition that Legion was a legitimate, professional operation worth supporting.
24 January 2024: Reddit Slander Post
On 24 January 2024, a user named Obviously_Mario created a post titled "Legion Kill feed, What's souls issue?" in r/DayZDiscussions.
The post accumulated 45 comments over 8 months with coordinated timing. Multiple accounts made identical accusations using similar language about "file stealing" and "FTP access."
Key Pattern: Many accounts posting accusations had no post history except for this single thread. September 2024 defence comments revealed Brief_Ordinary1438 was connected to the competing "DayZ Skynet Killfeed" service.
31 January 2024: Xanax Threats
On 31 January 2024, Xanax (Discord User ID 836723684190191656) escalated the abuse into explicit sexual violence against Brodie's family. In the public exchange he wrote, "no wonder your wife enjoyed me raping her." Other users immediately called the message messed up and fucked up, and Brodie banned him.
The wider evidence from the incident records sexual-violence threats directed at Brodie's family. The later July unban attempt therefore followed a documented sexual-threat incident, not an ordinary personality clash.
Xanax later offered an "apology" - but then admitted the apology was insincere. He had only apologised to try to get unbanned.
March 2024: Papa Blunt Incident
On 2 March 2024, during Legion's free beta period, Papa Blunt (Hot_Ad6729) opened a support ticket needing to remove Legion from one Discord.
For three days, while Brodie was dealing with a breaking change, Papa Blunt did not respond with what Brodie needed to diagnose the issue.
On 5 March 2024:
- Brodie posted a public notice about the command errors
- Papa Blunt closed the ticket saying he had "figured it out"
- Brodie reopened it immediately, frustrated
Legion Killfeed added .papa blunt (id: 1085988959701704845) to the thread. - Sat 2 Mar 2024 12:03 PM .papa blunt (id: 1085988959701704845) - Sat 2 Mar 2024 12:05 PM: Hey. I have legion on another discord and need to remove it so I can add to my new discord. Keeps saying I don't have perms to set discord? I deleted all tokens and tried to create another but still says I need to /set discord. Soul β - Sat 2 Mar 2024 4:18 PM: Can you screenshot the error? .papa blunt (id: 1085988959701704845) - Tue 5 Mar 2024 1:07 PM: I figured it out. Thanks tho. (closed the ticket) Legion Killfeed APP - Tue 5 Mar 2024 1:07 PM: @Soul β (aSoul) reopened .papablunt's ticket... Soul β - Tue 5 Mar 2024 1:08 PM: Actually, I fixed the issue while you ignored me trying to tell you at 11:14am I was fixing it β β«Έγ»beta-chatβ . I literally pinged you, twice, how can I fix it if you're gonna ignore me though? I can't fix things when I can't find the issue. If you can't help me help you, then I won't help you in the future, meaning, I will remove the bot. I was only trying to help. .papa blunt (id: 1085988959701704845) - Tue 5 Mar 2024 1:15 PM: Lol. I didn't ignore you by any means. I honestly didn't see your message until I hoped over to your discord to see if anything bug wise was going on.
Instead of de-escalating, Papa Blunt spammed the broken commands, mocked Brodie, and sent DMs calling him "a power tripping whining little girl."
Within hours, the same Reddit account Hot_Ad6729 posted in the existing "Legion kill feed, What's souls issue?" thread, calling Brodie "a total douche bag."
The Pattern: This incident demonstrates the standard playbook used against Brodie - create a support issue, ignore assistance, escalate the conflict, then immediately take it public with a one-sided narrative that strips all context. Papa Blunt's rapid pivot from support ticket to Reddit attack post shows how technical support disputes were being weaponized into reputation damage.
April 2024: Legion's Growth
By late April 2024, Brodie's systems were serving 174 servers at peak during the beta period.
26 May 2024: Kyle/Cactus Confession
On 26 May 2024, a user named Kyle (alias "cactus") openly confessed in Brodie's Discord server that he had been leaving fake negative reviews on "all the bot websites," including Trustpilot.
Kyle bragged that he went around posting bad reviews for bots he had never even used.
The Link to Competitors: "Kyle" was tied to Trojanowski's group. This confession directly linked Discord harassment to Trustpilot sabotage.
June 2024: Formal Complaint
On 5 June 2024, Brodie filed an Adult Cyber Abuse complaint with the Australian eSafety Commissioner (receipt ACA-2024-0528878).
The complaint captured the cross-platform nature of what was happening: doxxing, pedophile smears, and the involvement of his children as targets.
By mid-2024, Brodie also referenced seeking help from NSW Police in relation to earlier sustained harassment.
Mid-June 2024: Renewed Doxxing
Around 18 June 2024, Trojanowski and Griggs began pushing what they claimed was Brodie's home address into public Discord spaces again.
Two days later, on 20 June 2024, the campaign hit a new intensity:
- Messages aimed at Brodie included explicit suicide encouragement
- The same burst of abuse dragged his children into it again
20 June 2024: Kamikaze Confession
That same day, in a private Discord conversation that Jacob "RBSkizza" Stoppard later shared with Brodie, Trojanowski (kamikaze420) openly discussed coordinating attacks. This chat log contains a direct confession to DDoSing and sabotage:
KAMIKAZE: imma get his ass RBSKIZZA: GGs to ddossing me KAMIKAZE: I had it in 15 minutes of trying KAMIKAZE: Soul was easy as fuck KAMIKAZE: Lost interest time RBSKIZZA: He had your website shut then bitched when it was back up KAMIKAZE: Tried to scam me on PayPal got reported and got his account blocked KAMIKAZE: My site wasn't down... took it offline to move it... I'm not that dumb KAMIKAZE: I have my shit across 6 different servers expensive as fuck but at least my shit works KAMIKAZE: Little does he know he lost like 15 customers and they all came here KAMIKAZE: Imma leave his alts for now... now that I know imma feed him bad info KAMIKAZE: Did Salty ever go back? RBSKIZZA: Nah he didn't KAMIKAZE: Aw okay I wondered that that... He's got two I think. Thanks for this imma play like I don't know... Little slimy rat
21 June 2024: Family Contact Attempt
On 21 June 2024, Brodie tried one of the few remaining off-ramps available to him.
He contacted Trojanowski's sister directly, asking for help stopping what was happening.
The reply that came back, presented as being from Trojanowski's mother, was mocking and dismissive.
Shortly after, Trojanowski himself sent a follow-up message styled to mirror Brodie's brand - confirming Brodie had reached the correct family circle.
24 June 2024: Brodie's Response
By 24 June 2024, after days of suicide baiting, doxx attempts, and repeated "pedo" smears with no factual basis, Brodie reached a point where he stopped trying to absorb it quietly.
He confronted Trojanowski publicly with a claim grounded in a registry search, stating that Trojanowski was living at the same address as a registered child sex offender.
Brodie framed it as a line being drawn: he was done being labelled a pedophile by people who were simultaneously weaponising images of his children.
25 June 2024: The Smear Becomes an Instruction to Keep Going
The 25 June captures show Trojanowski being told by another person to move on. He answered that he had given Brodie a year, was fed up and that Brodie could now enjoy his own medicine. In a separate message Griggs wrote that people should continue to chase the pedophile.
The same evidence set records Trojanowski telling Jacob Stoppard, "Snitches get stiches," followed by Griggs addressing Stoppard by name and writing, "You're Next!" This placed the false pedophile accusation beside an explicit call to keep pursuing Brodie and direct intimidation of the staff member who had brought evidence back to him.
End of June 2024: The Predictable Loop
By the end of June 2024, the pattern had settled into a predictable loop:
- Trojanowski and Griggs kept combining doxxing pressure, suicide encouragement, and family-focused intimidation with a defamation storyline
- Reports were being filed across platforms, but enforcement was inconsistent and slow
- Even when something was taken down, the same claims resurfaced through new accounts
10 July 2024: Blacklist Report
On 10 July 2024, a community member submitted an anonymous report to The Blacklist, describing Trojanowski and Griggs as harassing people, using slurs, and pushing into doxxing territory.
This third-party report demonstrated the harassment was visible enough that uninvolved community members were formally documenting it.
11 July 2024: Xanax Unban Attempt
On 11 July 2024, Xanax (xanax1228) - who had previously made rape threats against Brodie's family - attempted to get unbanned from Legion's Discord.
When Brodie refused, Xanax responded: "See if you'd actually let me speak I'm not asking for forgiveness not once did I ask."
Discord had never actioned the original rape threats despite reports, yet the platform later penalised Brodie for responding to such threats.
13 July 2024: Customer Threatened with Lawyer
On 13 July 2024, Lady Weezus - a former SkyNet customer - shared her experience leaving the competitor's service.
After raising legitimate concerns about service quality, Trojanowski's response was to threaten her with a lawyer and close her support ticket.
"I still can't believe they threaten me with a lawyer... when I called him out he closed the ticket. So I left. Fuck em. The killfeed was awful." - Lady Weezus
She described the service issues: "Took 10 minutes to respond or anything."
This third-party testimony demonstrated SkyNet's pattern: when customers raised concerns, Trojanowski escalated to legal threats rather than resolving issues.
15-21 July 2024: IP Clustering
On 15 July 2024, Security Trails reverse IP lookup revealed multiple domains under Trojanowski's control sharing the same IP address (15.204.227.181):
- SkyNetVSLegion.com (defamation site)
- DayZSkynet.com
- AggroPVP.com (harassment site)
This proved the harassment operation was centralized - not random drama, but an organized operation run from shared infrastructure.
On 21 July 2024, a Legion supporter (ScooterPootr) confronted Trojanowski with the Security Trails proof. Trojanowski immediately deleted the conversation and denied responsibility.
1 August 2024: SkyNet Blacklisted by Community
On 1 August 2024, Lykos - a respected server owner from Conquest who had been following the harassment - shared a major development.
After SkyNet's behaviour was formally reported to The Blacklist Discord (a biased and problem causing community pretending to be a watchlist for problematic actors run by problematic actors), Griggs had a public meltdown when confronted with the evidence.
"Lmao crix not happy he got posted on blacklist too. Calling everything fake... Crix meltdown started calling her a bitch. Lmaoo." - Lykos
The screenshots showed Griggs calling the moderators "stupid bitches" when they questioned the evidence against SkyNet. When a moderator tried to help him respond, he escalated:
"You just call me a bitch? When actually I am trying to help you." - Evil (Blacklist Mod)
"Yeah. What you gonna do besides ban me?... nobody cares about your dumbass shit anyway." - Crix
Queen a DayZ++ Staff publicly discontinued their partnership with SkyNet: "I contacted kami and discontinued my partnership."
Other community members noted: "DayZ Drama. ya'll need to take inspiration from DayZ++ and just do your own thing" - Links, ironically commenting as if uninvolved despite being the primary doxxer.
Result: Trojanowski and Griggs were formally added to The Blacklist. They immediately deleted all their messages attempting to hide evidence, which community members caught: "they went back into jeabers and deleted messages lmaooooo".
Brodie replied to Lykos: "He always does, Kami deletes his too, he deleted all of our DMs the day we split... Man ran scared."
Part Five: August-December 2024 - The Review Platform War
7-9 August 2024: DayZ++ Staff and The Blacklist
On 7 August 2024, Queen, who was DayZ++ staff, posted in The Blacklist telling members to "avoid these two whenever possible." She described the dispute as "personal beef," said the original context no longer mattered and said the spillover was affecting the community. The DayZ++ material from the same period also shows hoks with an Administration role and Links/Linksypoo with a Partner role while presenting himself as the person behind whitelist.gg.
On 9 August 2024, Brodie and Queen then had a lengthy direct-message exchange that substantially changed the position between them. Queen said her issue with Brodie was how he had spoken to her, not a killfeed-competitor motive, and said she had already edited the post to remove the businesses, calling their inclusion "a bad call." Brodie went back through the earlier Jarvis/DayZKillfeed.com, Jeabers, Links and SkyNet history and explained the child-photo and DDoS context. Queen said she could see the Kami material, later said she could not believe what Kami and Crix were saying, and proposed that both existing posts be removed. Her proposed arrangement was that new conduct from Kami or Crix could be posted, genuinely toxic conduct by Brodie outside the SkyNet dispute could also be posted, and that Brodie had a right to defend himself against Kami and Crix. Queen also said she had taken down her SkyNet token, kicked the bot and terminated the partnership. Brodie agreed to the arrangement, removed the DayZ++ material from his old coding Discord and said he would update the website when he got home. Queen later said Nick did not know what was going on and that she had told him she would step down if necessary. During the same exchange Brodie said that anything posted about him meant he would have to keep explaining the dispute over and over until eSafety got it removed, capturing the repeated burden that later made his continued public explanations look excessive to people who had not seen how often the same history had to be re-established in a new place.
August 2024: Trustpilot Attacks
On 13 August 2024, a Trustpilot review about DayZ Multi Tool accused the bot of being used to wipe a server and claimed malicious code existed to delete channels and roles.
On 19 and 20 August 2024, Brodie reached out to Reddit Support over a slander thread. The emails preserved show him writing in a state of acute distress, including explicit suicide language.
24 August 2024: Child Targeting Exposed
On 24 August 2024, Edward Anthony Griggs Jr. (Crix) mocked another killfeed operator and posted an image referencing that person's children as a kind of punishment for speaking up.
The intimidation style was clear: the point was not to argue features or prices, but to make family a pressure point.
27 August 2024: SEO Warfare
By 27 August 2024, Trojanowski was tied to SkyNetVSLegion.com being positioned to appear prominently in Google results for "Legion Killfeed."
28 August 2024: Havasu Review
On 28 August 2024, Stockton posted a one-star Trustpilot review under the name "havasu."
The review falsely described Legion as exposing sensitive data, framed the service as unsafe and dishonest, called Brodie a "ChatGPT coder," and steered readers toward named competitors.
On 6 September 2024, while pressing Trustpilot to deal with the "havasu" attack, Brodie explicitly referenced an open police investigation into the harassment (reference CIRS-20240906-104).
September 2024: Buchanan Betrayal
On 31 August 2024, Brodie's DMs with Anthony Buchanan (OzzieHousos, UntoldTruthy) still carried a friendly tone.
Then on 1 September 2024, Buchanan told Brodie he had previously been given access to a private GitHub repository by Trojanowski and said "a lot of it is DZMT stuff." That was a person with repository access describing DayZ Multi Tool material inside the private code he had seen.
Buchanan then deleted parts of the conversation, left Legion, returned through the UntoldTruthy account and later renamed that account to call Brodie a pedophile using his real name. By 13 September he had also posted a negative Trustpilot review while operating a competing DayZ service. The source who had first supplied corroborating repository information had become part of the same public smear.
12 September 2024: Suspicious Bot Contact
On 12 September 2024, a developer using the handle "Tony Stark" messaged Brodie directly, saying he had used DayZ Multi Tool for years and that it inspired him to build a "companion bot."
Brodie's own logs tied that account back to an earlier Discord identity, "jailbreakdeez."
13 September 2024: Buchanan's Pivot
On 13 September 2024, Buchanan approached Brodie with a proposal asking what it would take for Brodie to implement Buchanan's "alt detection" methods into Legion.
Brodie refused outright, pointing to the trust problem Buchanan had created himself.
The tone changed instantly. Buchanan flipped from "work with me" to abuse - called Brodie a "pedo," pushed drug taunts, and escalated into "woman basher" slurs.
Soon after, Buchanan posted a negative Trustpilot review under his own name while operating as a competitor.
September 2024: "Pups" Infiltration
From 19 to 21 September 2024, Mason Lewis Stockton continued contact using the Discord account "pups" (sasha1371731).
On 18 September 2024, an account using Stockton's pups alias entered a Legion support thread raising the idea that Brodie's address and tax information could be found on his website. Brodie responded that his ABN was legally required and publicly searchable in Australia, and when pressed about the "address," he pointed out the listed location was a deliberate joke rather than a real residence. The exchange showed the same recurring behaviour: probing for personal information under the cover of "just letting you know," then keeping the target engaged on the subject of where they live.
The mask slipped on 21 September 2024. Brodie reopened the "pups" ticket publicly and posted a screenshot showing that the same account was privately messaging Legion subscribers, pushing them to switch to DayZ++.
24 September 2024: T-Bag Pattern
On 24 September 2024, Trojanowski and Griggs attacked a different killfeed developer known as T-Bag in similar fashion.
Trojanowski and Griggs circulated images of T-Bag's children and harassed him with those photos - exactly as they had done to Brodie.
Critical Proof: This demonstrated that targeting minors was a repeated tactic against any perceived competitor.
22 September 2024: Trustpilot's Technical "Error"
On 22 September 2024, Trustpilot gave an early preview of the problem Brodie would face for the next year: even when a defamatory review was removed after being reported, it could reappear anyway.
Anthony Buchanan's Trustpilot review had been taken down on 19 September 2024 after it was reported for defamatory content, but it was then mistakenly reinstated due to what Trustpilot described as a technical error. The reinstatement was corrected again on 22 September 2024 under Ticket #28652546.
For Brodie, the practical impact was simple: even when a platform agreed something should not be published, the same content could still resurface without warning, forcing him to relive the takedown process and absorb another round of exposure.
November 2024: Karl Messer Review
On 5 November 2024, Karl Messer (using the handle Moley) returned to Brodie's DMs with hostile taunts about Legion Killfeed.
Messer tried to turn it into a story that Brodie had "cancelled" his payment. Brodie pushed back with PayPal failure notices as proof.
On 6 November 2024, Messer posted a one-star Trustpilot review under his own name - despite Brodie having already flagged to Trustpilot that this exact kind of review attack was being threatened.
20 November 2024: Links' Reputation Preceded Him
On 20 November 2024, the reputational consequences of Mason Lewis Stockton's (Links, Havasu, pups) harassment campaign became visible to third parties.
In a conversation captured that day, Lykos asked whether "Links" was still involved with AltDetector. The response confirmed what server owners already knew:
"Nah, we decided to part ways with Links as it felt like his questionable reputation was holding us back." - iNTERCEPT18
When Lykos noted that "Myself and many other server owners didn't want to touch it", the new leadership agreed:
"When I first came in I was surprised at some of the stuff I saw... I didn't really know of Links or his past when I first came on, so it's been a very eye-opening experience." - iNTERCEPT18
This third-party testimony confirmed that Links' documented history of doxxing and harassment was visible enough to professional partners that they chose to distance themselves publicly. Information would later reveal iNTERCEPT18 was Stockton all along.
25 November 2024: Walker TikTok
On 25 November 2024, a TikTok post by Joel Walker (Jack Jackelope) included an on-screen prompt telling Brodie to message him, framed in a deliberately antagonistic way.
December 2024: Trustpilot Loop
On 2 December 2024, Trustpilot's Content Integrity team responded to Brodie's defamation flag on Karl Messer's review and said they had run it through an "AI-powered defamation tool."
They concluded the review was "not defamatory," reinstated it, and told Brodie to reply publicly to "tell your side of the story."
From 5 December through 19 December 2024, Brodie tried every available Trustpilot pathway to force a genuine verification check, and Trustpilot kept closing doors.
Part Six: 2025 - Multi-Platform Siege
3 January 2025: Symbolic Frustration
On 3 January 2025, Brodie's frustration with Trustpilot spilled into something symbolic - a short looped "fuck you" style video aimed at the platform.
January 2025: AltDetector Shutdown
On 28 January 2025, Mason Lewis Stockton posted a shutdown announcement for AltDetector and openly admitted he had been operating it under an alternate identity.
The message ended with explicit abuse aimed at Brodie - a confession that customers had been misled about who was running the product, wrapped in a parting shot.
7 February 2025: Nitrado Failure
Brodie sent a formal complaint to Nitrado describing being harassed and slandered by a volunteer Discord moderator while trying to get help from legitimate staff.
He also complained about prolonged service disruption during DDoS attacks and the mismatch between advertised protections and actual uptime.
13-14 February 2025: FaMiN Exchange
After a new signup appeared that made Brodie suspicious, he refunded and removed access, then contacted the user directly.
In the exchange, FaMiN_aKuTaMaY offered to prove legitimacy by providing information about Griggs, including claims about address history and employment. FaMiN described a long-running conflict including a threat to kill him.
FaMiN revealed he had first found Legion through posts accusing one side or the other of stealing code - and that seeing Griggs listed as an admin on Skynet was exactly why he chose Brodie's service instead.
March 2025: Trustpilot Continues
By March 2025, the Karl Messer one-star review had stopped feeling like an isolated customer dispute and started reading like a process trap: every time Brodie tried to flag the review, the platform's workflow pushed him into another category, another form, another wait - while the same accusations stayed public.
In early March, Brodie filed further reports arguing the review wasn't describing a genuine experience but was instead a personal-attack narrative built around false claims about payments and customer treatment.
Trustpilot's replies kept steering him back into procedure. On 6 March he was told investigations depend on the specific flagging reason selected. On 8 March, Trustpilot said Messer did not respond to a request to remove identified personal-information content - yet the review itself remained visible.
On 10 March 2025, Trustpilot's Content Integrity team closed the loop: they said they had read the review and concluded the phrases Brodie flagged "follow our guidelines," so the review would remain online. The message again encouraged him to reply publicly and "tell your side."
After that decision, Brodie wrote that the review was already costing him business, and that he would escalate beyond Trustpilot - including contacting senior staff and consumer-protection channels.
By 22 March, the tone shifted from adjudication to customer-experience bureaucracy: Trustpilot emailed a feedback survey about the interaction.
25 March 2025: AltDetector Legal Threats
Brodie posted a warning to his own community about AltDetector and the people now promoting it.
Renato Alexander Gallo GΓ³mez (DonMatraca) then DM'd Brodie directly. GΓ³mez turned to insulting Brodie's programming abilities while framing his contact around "don't drag my bot into your drama."
Brodie treated it as another attempt to intimidate him into silence and repeatedly invited the person to "send your lawyers" if they intended to escalate.
April 2025: Mason Returns
On 17 April 2025, Mason Lewis Stockton resurfaced in Brodie's Discord under the Havasu name and immediately tried to reframe an older controversy.
When Brodie responded by calling him "Links," Mason reacted like he had been caught and within minutes was kicked from the server.
May 2025: More Fake Reviews
By May 2025, the dispute had widened beyond one reviewer. Brodie was now trying to get Trustpilot to recognise a pattern he said he could see clearly from the inside: misrepresentation, coordinated pressure, and reviews being treated as "normal feedback" even when the surrounding context looked like harassment.
On 21 May 2025, Trustpilot's Content Integrity team acknowledged a formal complaint from Brodie about false misrepresentation and warned of long delays due to high volume.
On 26 May 2025, Trustpilot responded to a classification-related complaint by framing the misrepresentation as an artifact of how a reviewer searched - not as a coordinated attack.
Then, on 29 May 2025, another one-star review appeared under the name "Trevor Gonzales," accusing Brodie of abusive support. Brodie challenged it as unverified and inconsistent with his own internal records.
Trustpilot's response followed the same track as before: the review was run through an "AI-powered defamation tool," judged "not defamatory," and reinstated.
June 2025: Trustpilot "Top Mentions" AI Label
In June 2025, the Trustpilot thread took a turn that felt less like moderation and more like narrative damage: the platform's own UI began implying an "AI" theme on Brodie's profile, even as he argued the underlying reviews didn't support it.
First, the "Trevor Gonzales" review handling became internally inconsistent. On 2 June 2025, Trustpilot told Brodie the review had "already been deleted" and that it could not take further action - despite earlier communications indicating it had been reinstated and left visible.
Then, on 17 June 2025, Trustpilot's "Top Mentions" panel began surfacing artificial intelligence as a prominent theme on Brodie's business profile. Brodie challenged the label as false, noting the phrase did not appear in the published reviews and that Trustpilot's own search returned no matches.
On 19 June 2025, Trustpilot replied that "Top Mentions" are generated automatically, claiming the system linked "artificial intelligence" to the business because reviewers referred to it as a "bot" - leaving the implication in place despite the mismatch. Brodie wrote that he believed the label was being driven by Stockton's August/September 2024 review framing him as a "ChatGPT coder."
June 2025: Technical Credibility
On 21 June 2025, Brodie documented that Bohemia Interactive implemented a suggestion he had provided that reduced CPU usage across servers by roughly 40%.
That kind of profile makes attacks more attractive to competitors and trolls, because the target becomes symbolically valuable.
Part Seven: July 2025 - The Facebook Explosion
1 July 2025: Putzier Attack
On 1 July 2025, Nathan Lane Putzier (JakelOpprimere) began pushing a "billing scam" story inside Legion's own spaces.
Brodie responded by pointing out the contradiction: the subscription history showed a fresh subscription in May 2025.
2 July 2025: Facebook Post
On 2 July 2025 at 9:09 PM, Putzier escalated publicly in a DayZ Facebook group with over 33,000 members, posting a "scam" warning about Legion. The post contained multiple verifiable false claims that were immediately challenged by community members with evidence.
Nathan Lane Putzier (JakelOpprimere) - July 2nd 2025 at 9:09PM
"Everyone beware if you own a server and use legion kill feed you are getting ripped off (soul) the
'owner' is a scam artist never got what I payed for the kill feed kept cutting out or wouldn't work for
hours at a time. I cancelled my subscription in May and have still been getting charged. I asked him
what up with still getting charged and he blocks me. I would 100% never recommend Legions kill feed."
Maddi Slims replied:
"It's subscription is handled by a third party service so it's all self managed? The owner doesn't even
get close to having access to your details and your subscription started in may according to the third
party service?"
Community members then provided evidence showing:
β’ Putzier's subscription was created in May 2025, contradicting his "cancelled in May"
claim
β’ Third-party billing means Brodie has no access to cancel subscriptions
β’ No record of Putzier attempting contact through official support channels
The Documented Lies: Putzier's post contained three specific false claims that were debunked with receipts: (1) that he "cancelled" in May when records show he started in May, (2) that Brodie could manually charge him when billing is automated through a third party, and (3) that Brodie "blocked" him when no support contact existed.
July 2025: Brett Jones Incident
On 13 and 14 July 2025, Brett Jones (MrTechN9ne) told others in a Discord chat he was replacing Legion because he had "found out the owner of legion is a pedophile."
Brodie revoked Jones's access to Legion services immediately.
On 17 and 18 July 2025, Jones attempted to turn the conflict into financial pressure through PayPal. After PayPal decided the case in Legion's favour, a second person entered Brodie's support channel and explicitly relayed that "Tech says hi" - tying the contact back to Jones.
Late July 2025: Daniel Santos Post
On 19 and 20 July 2025, Daniel Santos (dani23COVID) opened a paid-support ticket that became a template for the next phase: take a conflict inside a ticket, strip context, and repost it publicly as "proof" the developer is abusive.
In late July 2025, Santos carried that internal ticket conflict out to Facebook. What followed showed how quickly this turned into coordinated pressure:
- Danny Hayes (XDannyModzzzX) argued that "never would a seller speak to a consumer like this"
- He explicitly pushed escalation tactics, including "EVERYONE REPORT LEGION"
- He posted proof of a negative Trustpilot review being left from that thread
- One participant added "#TeamKami," tying the pile-on language back to Trojanowski's orbit
- Brett Jones appeared in the comments reinforcing the smear
Not everyone followed the mob. Several community members pushed back publicly:
- Codi-lee Brooke Dale defended Brodie directly: "He makes everything simple for everyone so there's no need for stupid questions. If you just simply READ you'll find what you're looking for" - and told Santos to "pull your head out your ass" when his attacks escalated
- Maddyn Mills called out Santos' behaviour: "Look how pathetic you are, attacking anyone that opposes you, no wonder Soul pointed out how daft you are"
- KaLee Whitmore challenged Santos' victim narrative: "but idiots can disrespect him?" - pointing out the double standard
These defenders were met with hostility - Danny Hayes' response to Madelyn Mills was "2 can play that game," demonstrating how quickly defence of Brodie was treated as provocation.
Part Eight: August 2025 - The Review Bomb
1 August 2025: Coordinated Attack
On 1 August 2025, Danny Hayes received pushback from Madelyn Mills and immediately framed it as retaliation, writing "2 can play that game."
He then published a one-star Trustpilot review aimed at Legion Killfeed, telling readers to "REPORT ONLY" and singling Mills out by name.
At the same time, Brett Jones and people around his Discord were circulating Brodie's older Facebook remarks about his children being targeted, then turning it into sexually explicit mockery.
2 August 2025: Trustpilot Failure
Even with a review flagged as harmful or illegal - using an obscene slur as its username - Trustpilot's decision was to put it back online and take no further action.
That contradiction signalled to attackers that even the most obvious bad-faith content could be restored.
4 August 2025: Legal Escalation
Brodie formalised escalation with a demand letter to Trustpilot Legal. He characterised the posts as false, harassing, and part of a coordinated campaign originating on Facebook.
The same day, he sent a complaint letter to Meta's legal channels about the Facebook post.
4-7 August 2025: eSafety Complaint
Brodie filed comprehensive complaint to the Australian eSafety Commissioner (Reference CYR-0672200) documenting:
- Daniel Santos July 28 Facebook incitement
- Cross-platform coordination (5+ individuals UK/USA/Canada)
- Danny Hayes orchestrating mass-reports, review floods, and chargeback fraud
- Commercial competitors coordinating to eliminate Legion Killfeed
External Reports Filed:
- Canadian Anti-Fraud Centre: Reference 2025-67881
- Thames Valley Police (UK): Reference 43250388789
6 August 2025: Meta's Position
After Brodie reported the Facebook post and comments, Meta's replies stated it would not remove the reported material and suggested that he block or unfollow the posters.
Mid-August 2025: ABN Contradiction
On 15 August 2025, Trustpilot Content Integrity replied that Trustpilot did not operate under an Australian Business Number.
Three days later, on 18 August 2025, Trustpilot reversed that position, stating that Trustpilot's legal entity in Australia was Trpilot Pty Limited and supplying an Australian ABN (37 605 147 260).
Brodie highlighted that the two statements could not both be true.
18 August 2025: Partial Victory
On 18 August 2025, Trustpilot's Content Integrity team reversed course on at least one review. The "Robert McDonovan" review was being taken offline on the basis that it was not a genuine experience.
27-28 August 2025: Trustpilot Status
Trustpilot Legal issued a consolidated status letter listing review-by-review outcomes:
- "Z Doneskies" taken offline as "not based on a genuine experience"
- "Robert McDonovan" taken offline on the same basis
- Danny Hayes and WARZONE taken offline
- Karl Messer review blurred pending documentation
Even with the blur in place, the negative review still affected Legion's star rating.
Part Nine: September-October 2025 - Aggropvp.com Returns
1 September 2025: The Loop Continues
On 1 September 2025, Trustpilot's Content Integrity team reinstated the WARZONE review anyway and told Brodie it would not take further action.
24 September 2025: Direct Provocation
On 24 September 2025, Trojanowski directly messaged Brodie on Facebook and pointed him to https://aggropvp.com, framing it as "here you go" after "wanting my attention."
It was a taunt and a delivery mechanism in one: a direct nudge toward a site built to defame and threaten Brodie and his family.
26-27 September 2025: Alt-Account Pattern
On 26-27 September 2025, Brodie documented another example of the alt-account pattern around these circles.
A newly created Discord account approached him while advertising server and modding services, then admitted it was an alternative account. In isolation it looked like spam or opportunism.
But the account name was "SANTOS" - which matches Daniel Santos, the poster of the July 20th Facebook post. With this context, it matched the pattern of a competitor fabricating drama and further demonstrated the broader technique Brodie had been living with: new accounts appear, probe for access or attention, and then either deny identity or casually confirm they are operating under multiple names.
29 September 2025: Doxxing Returns
By 29 September 2025, aggropvp.com had become the sharpest edge of the story again.
The site published:
- The same address they believed to be Brodie's residential address
- Prior statements republished for ridicule
- A direct threat against Brodie's partner, displayed alongside her Discord profile details
Brodie treated that page as the point where the campaign moved beyond reputational sabotage into explicit intimidation.
October 2025: Brodie's Legal Escalation
1 October 2025: Brodie sent Reddit a formal cease and desist (Ticket #14802881) naming the r/DayZDiscussions post used to circulate false statements. He quoted the exact claims that he "collects and sells your files," that he had deleted other communities' server files, and that Legion's code had "malicious intent" - attached exports and screenshots tying the narrative to competitor Mathew Trojanowski, and put Reddit on explicit notice:
"I am placing Reddit on formal notice. A coordinated competitor campaign is using r/DayZDiscussions to publish false statements of fact about me and my business and to drive off-platform harassment. You now have explicit notice of the URLs, the exact words, and the linkage to a direct competitor. If Reddit refuses to remove the notified content, I will add Reddit as a publisher in defamation proceedings."
2 October 2025: Reddit Legal responded with deflection - acknowledging receipt but refusing to address the specific URLs, instead instructing Brodie to use the public report form. They treated a formal legal notice like a standard user complaint.
4 October 2025: Brodie sent a second notice reaffirming his position:
"Your internal policies and routing guidelines do not supersede the law. You are now on actual notice of unlawful content. Continued publication after notice can create liability, regardless of your forms or workflows."
5-10 October 2025: Brodie sent Trustpilot Legal a compensation demand and settlement undertakings with a Calderbank offer (settlement offer per Australian civil procedure) and a deadline of 10 October 2025 at 5:00 PM AEST. He argued that Trustpilot's back-and-forth moderation - removing reviews, then reinstating them - constituted republication after notice, creating multiple defamation counts. The demand included over 1,075 exhibits documenting the pattern.
Trustpilot's response: Automated acknowledgments only. "Experiencing high volumes... aim to reply within 10 working days." Zero substantive response by deadline.
7 October 2025: Brodie submitted a formal appeal to Facebook's Oversight Board (Case ID: FB-FS9LDNQ3), documenting that 18 personal reports plus 15 from others had all received "no violation" determinations despite coordinated defamation with false criminal accusations.
10 October 2025: Settlement deadline passed with no response from Trustpilot. Brodie sent a final notice:
"As of this writing, approximately 1.5 hours remain until the 5:00 PM AEST, 10 October 2025 deadline I set in my letter of 5 October 2025. I have received no response or compliance regarding the demanded compensation and remedial actions. This silence is unacceptable and further evidence of bad-faith on Trustpilot's part."
Late October 2025: Legion's Scale as a Target
Around this time, Brodie assembled uptime and scale metrics for Legion, including a month where the bot processed over five million Discord messages. He also gathered proof showing SkyNet's public leaderboards contained mathematically impossible stats under DayZ physics.
Those points were not "tech bragging" inside the timeline - they were part of the harassment logic: Legion's scale made it a larger prize, and competitor narratives leaned on undermining Brodie's credibility when they could not compete on performance.
25 October 2025: Joel Walker's Edited Post
On 25 October 2025, Joel Walker (Jack Jackelope) edited an existing high-engagement Facebook post in Make DayZ Great Again (a group with over 33,000 members) to insert the false statement "Soul from legion a pedo."
The post already had a large number of likes and comments before the accusation was added - meaning the edit tactic made old likes look like support for the new claim.
The comment thread that followed contained:
- Explicit calls for violence against "pedos"
- Statements implying that anyone defending the target should also be treated as guilty
Walker also posted that anyone "pointing the finger" at him for "calling out pedos" must be a pedo - while continuing to attach the label to Brodie and Legion.
Historical Context on Joel Walker: Community members surfaced documentation of Walker's pattern of false accusations and aggression:
- Nicholls Kurt (former high-ranking member of Walker's Discord): "I used to be higher up in his discord and could see channels no one else could and some of the shit he would say, post, and do with some of these (kids) would have him on a watch list. I did report a lot of it to discord back then with the proof."
- KaLee Whitmore (Walker's former partner) posted evidence of a restraining order for domestic violence involving herself and Walker.
These revelations demonstrated Walker's pattern of accusing others of the very behaviours he had been formally documented engaging in - a tactic known as DARVO (Deny, Attack, Reverse Victim and Offender).
Historical Context on Joel Walker (Employer Statement): A character statement letter dated 10 January 2021 from Walker's former employer provides relevant background:
"Joel initially struck me as a man with a troubled past who was doing everything he could, trying to get his life back on the correct path... We had our first incident with Joel getting angry about two months in, Joel got into a screaming match with his supervisor and nearly got physical with him. When I asked about the situation, Joel stated he was not going to be talked to like he was a punk. This type of behavior happened a few other times with other employees, and Joel always had the same response, that he felt like he needed to use aggression to assert dominance... I then noticed Joel start to try and make everyone out to be a bad worker, in order to get them fired or disciplined... Joel's termination came after he was coached about behavior in Late December 2020, he got in my face like he was going to hit me... Joel proceeded to call HR and falsify claims that I was threatening him with a firearm, being racist toward him, and harassing him. All these claims were found to be false."
This pattern - false accusations to authorities, aggression to assert dominance, and attempts to get others punished - directly mirrors Walker's behaviour in the 2025 Facebook defamation campaign.
27 October 2025: Violence Invited
On 27 October 2025, the situation widened into real-world danger.
Once a false "pedo" label is unleashed in a large community space, it invites threats from strangers who feel righteous. The surrounding discussion included people asking for addresses.
Feather shared a restraining order connected to Walker, describing the respondent as a credible threat to physical safety.
Part Ten: November-December 2025 - Notice and enforcement records
Early November 2025: Direct Family Contact
On 2 November 2025, Brodie wrote to Edward Anthony Griggs Jr.'s father, identifying Griggs by name and describing a three-year pattern that included suicide encouragement, repeated "pedophile" smears, and a grown man storing and sharing images of Brodie's young children.
3-6 November 2025: Meta Support Loop
From 3 to 6 November 2025, Meta support continued to behave like the conversation was an inconvenience rather than an emergency.
The Nine-Hour Runaround (3 November 2025, Reference ID 1332648995224789):
- 7:30 PM: Agent Adi joined chat, Brodie explained Walker's October 25 post calling him a pedophile
- 8:03 PM: Adi promised to "pause the chat for the time being and investigate on this from my end with my team"
- 8:06 PM: Adi left
- 8:35 PM: Adi left again (65 minutes since start, no action)
- 10:08 PM: Brodie wrote: "This bad faith behaviour is on the record, I'll be contacting the ACCC"
- 10:55 PM: Adi returned (over 2 hours after leaving)
- 11:19 PM: Adi left again (4 hours since chat started, zero action taken)
- Next Day 4:55 AM: Agent Michael joined, provided form directions, left after 10 minutes
- Next Day 7:35 PM: Adi returned (over 20 hours after initial contact), admitted: "we are unable to directly take actions on this, so we require a report from your end again"
Brodie's response:
"YOU SAID YOU WOULD DO IT. THAT SPECIFIC ADI CUNT SAID HE WOULD DO IT... I HAVE BEEN WAITING TWO FUCKING DAYS"
On 5 November 2025, the tone hardened. Brodie accused a Meta support rep of not reading his messages at all, and the rep's only response was a blunt instruction not to reply further because the case had already been "investigated."
On 6 November the support escalation moved to a phone call. The Meta representative was a woman. She repeatedly tried to troubleshoot Brodie's account and asked for screen sharing even though he kept explaining that the problem was the public pedophile accusation on Meta, not his browser, computer or account. After the complaint had already been explained in writing, she asked whether the issue was impersonation. Brodie demanded a supervisor and the call degenerated into an argument about his language while he was still trying to get the post itself addressed.
4 November 2025: Discord Strikes the Target
Discord added its own twist on 4 November 2025. In a normal support conversation about Legion features, Brodie mentioned he was about to send an email that could get Walker's Facebook account and group removed and pasted a link to his public documentation page.
Discord treated that single message as harassment and bullying and issued an account strike.
The strike notice focused on Brodie's defensive link - not the weeks of false criminal accusations being spread against him.
6 November 2025: Discord Second Strike Against Victim
On 6 November 2025, Brodie submitted Discord ticket #61771050 titled "Discord Staff Retaliation & Knowingly Penalizing Harassment Victim - Legal Escalation Imminent."
His submission laid out the timeline:
- October 25: Joel Walker publicly accused Brodie of being a pedophile on Facebook (evidence provided in previous ticket)
- October 25-November 4: Discord had Facebook evidence for 4+ days
- November 4: Discord applied harassment strike to Brodie's account for defending against false accusations
Brodie's statement: "Discord's action demonstrated either: Willful disregard for context and victim safety, actual complicity in the harassment campaign, or gross negligence in your review process."
The Psychological Collapse (October-November 2025)
The cumulative effect of three years of harassment and institutional betrayal became visible in Brodie's Discord tickets during this period.
23 October 2025 (Ticket #61465755):
"Fucking should just end my life, then you fucks might actually be forced to fucking look at this shit. I AM BEING MARKED FOR REPLYING TO A MESSAGE, WHEN THEY ARE THE ONES FUCKING HARASSING ME CUNT!"
17 November 2025 (same ticket):
"Great to know discord gives that few fucks about the people on their platform they'll straight up close and not reply to a suicide threat after being told to kill myself for three years on discord by these cunts. I'm done, ya'll are fuckheads, I hope you all lose your fucking jobs when I end my life. Fuck, if I've gotta kill myself to get this fucking shit reformed I'll go through with it."
9 November 2025: Continued Attacks
On 9 November 2025, Walker posted a fresh jab in a DayZ Facebook group telling people to "keep defending the kiddy ticklers" at Legion.
That same day, Trojanowski sent Brodie a new Facebook contact attempt with an insulting message attacking Brodie personally - continuing the pattern of using direct contact as harassment.
10 November 2025: Direct Death Threat
On 10 November 2025, a Discord user named "Paggaslaan" sent Brodie a message ending with "Hope they do get your family" - a blunt, personal threat.
Mid-November 2025: Measurable Business Impact
A returning customer later put the business effect in writing. Royal_Russ311 / LEoUR_ said he had been a high-tier Legion subscriber from 27 October 2024 until 8 August 2025 and cancelled because the rumours circulating on Facebook and Trustpilot during July and August made him uncomfortable and he wanted to use a bot service that was not associated with the ongoing drama. After reviewing the broader history, he returned to Legion.
That is direct evidence of the publications changing a customer decision. The harm was not being inferred from views or hostile comments: a paying subscriber identified the rumours and platform material as the reason he left.
14 November 2025: Discord's Evidence Problem
On 14 November 2025, Discord's data-export language confirmed that manually deleted messages are not stored and do not appear in a user's data package.
In the context of this campaign, that matters because one common tactic is to send threats or vile claims, then delete them - leaving the target trying to prove what happened with only whatever they preserved at the time.
17 November 2025: Trustpilot Flags Brodie for "Misuse"
On 17 November 2025, Trustpilot's Content Integrity team emailed Brodie to say it had detected "misuse" of his flagging tool and referenced multiple internal ticket numbers. The message argued that genuinely fake reviews would be removed automatically by Trustpilot's fraud engines, while also conceding that some could "go unnoticed". In plain terms, the platform reframed Brodie's repeated, evidence-backed reports of obviously false reviews as the problem, even as the same reviews and themes kept resurfacing.
21 November 2025: Reddit and Discord Close the Door
On 21 November 2025, Brodie escalated to Reddit Support in writing and tied the harassment campaign to prior formal reports, including his eSafety receipt (ACA-2024-0528878) and a police reference (CYR 0672200). On the same date, a captured screenshot shows a suicide-related report being closed within minutes without any substantive reply, mirroring the pattern he had already experienced on Discord: acknowledgement and closure, without action against the people doing the targeting.
Between 17 and 21 November 2025, Brodie filed appeals and complaints to Discord over the harassment strike and over Discord's evidence handling, repeatedly asking for a human review. He tied the appeal back to a long list of prior Trust and Safety tickets and described being mass-reported across platforms. His correspondence explicitly told Discord that the way platforms were closing tickets and refusing to consider supporting material was pushing him into despair. One follow-up complaint captured the core frustration: he raised the seriousness of the situation in a ticket, and it was closed quickly without any meaningful response - reinforcing the feeling that the system was designed to end conversations, not stop harassment.
30 November 2025: Mental Health Trustpilot Attack
On 30 November 2025, a new Trustpilot review appeared: "Rude, unwilling to help, Soul needs profession help" (1-star rating). This review represented a particularly insidious form of attack - weaponising mental health stigma as business criticism. The statement "needs professional help" imputes mental illness, which under Australian law constitutes defamation.
The same day, a Discord ticket export documented 21 tickets spanning 2022-2025 where Discord had systematically:
- Closed reports without meaningful action
- Applied enforcement against the victim instead of perpetrators
- Created a pattern where the target was penalised for responding to harassment
The Discord Contradiction: The ticket history also revealed a stark institutional contradiction. In 2022, Discord's Trust and Safety team had thanked Brodie for providing screenshots and user IDs, explicitly encouraging that evidence format - and that approach had led directly to the IP ban on Mason Stockton. By 2025, with the same harasser (Stockton) still involved in the ongoing campaign, Discord now refused to accept screenshots as evidence and redirected all reports to in-app mechanisms.
Even more damning: Discord had scrubbed the original 2022 report from Brodie's account records. The report that resulted in Stockton's IP ban - the one clear example of Discord taking the problem seriously - was only recovered through a formal data subject access request. The platform had erased its own evidence that email-based reporting with screenshots had worked.
1-4 December 2025: Disability Discrimination Act Refusal
Brodie formally invoked the Disability Discrimination Act 1992 (Australian law), cited ADHD, and explained how the prolonged harassment campaign was exacerbating disability impacts. He requested reasonable adjustments in Trustpilot's investigation process.
Trustpilot's Response (4 December 2025): Explicit refusal. "We are unfortunately unable to accommodate a phone call." They offered only a 1-month subscription to a mental health service ("Plumm") as an alternative.
Legal Significance: Refusal to provide reasonable adjustments for a documented disability constitutes discrimination under Australian law.
Psychological Impact Visible: Brodie's correspondence with Trustpilot had shifted from professional legal briefing (October) to profanity-laden desperation (December). Four months of institutional indifference had broken the victim's composure.
2 December 2025: Joel Walker's Meth Accusation
On 2 December 2025, customer JackOByte reported Joel Walker's new Facebook post to Brodie: "Legions killfeed is spamming evidence he smokes meth on the regular."
This false accusation of methamphetamine use represented a new escalation - moving from "pedo" smears to drug-related defamation. Meta refused to remove the post despite formal complaints.
5 December 2025: More Fake Reviews
By 5 December 2025, the dispute shifted from "is this review fair" to "is this person even real."
A one-star review under the name "Hooded_Saw" claimed Brodie refused support, ignored a ticket, and then created a separate channel to call the reviewer names.
Brodie's own customer search screenshots show no matching customer record for the "hooded_saw" name or the email attached to the review.
8 December 2025: Discord Thread Spam Campaign
On 8 December 2025, a Discord-linked defamation flare-up became visible in a space with no moderations so there is nobody to police it. A user account named "jeff_is_boss" appeared in a mutual server, Jeaber's Killfeed Support, a discord server with the most console dayz server owners and no moderators - with a thread list dominated by attack framing.
The thread titles were not ambiguous criticism. They included variations like:
- "Legion (AKA Soul is a Pedo)"
- "Legion scam"
- "Soul be scamming"
- Repeated promotions of "aggropvp.com"
The point of those threads was not to resolve a support issue. It was to attach a criminal label to Brodie's name and to funnel readers toward a hostile website, using Discord's thread system to keep the smear visible and refreshed.
9 December 2025: Meta AI Training Concerns
On 9 December 2025, Brodie pushed the Facebook side into a more formal posture. His correspondence to Meta's privacy operations included a large attachment bundle tied to the Joel Walker Facebook accusations and the ongoing refusal to remove them.
He also raised a second, related harm: that Meta's AI training and "public internet" ingestion processes were sweeping up personal information and republishing it through automated summaries, even while Brodie was actively objecting to the underlying defamatory source material.
10 December 2025: Kamy Review Returns
On 10 December 2025, a review posted under the name "Kamy" reappeared describing Legion as "really bad." Brodie's reply stated that Trustpilot had already removed it once because it was left by a competitor, and he framed its return as the platform allowing the same competitor material to be published again.
15-16 December 2025: Discord Enforcement
On 15 December 2025, Brodie received a generic Discord enforcement notice saying his recent activity broke Discord's rules - without specifying what content triggered it.
On 16 December 2025, more Discord violation emails followed, including a removal notice.
16 December 2025: Trustpilot Evidence Manipulation
Brodie discovered Trustpilot had altered flagging history on multiple reviews. Reviews Brodie had flagged showed zero flagging history in the backend, contradicting his email records proving multiple reports filed.
The platform had rewritten its own records to avoid a liability trail.
15-19 December 2025: TikTok - Edward Griggs Continues Harassment
December 15, 2025: Brodie posted a TikTok video explaining the Legion Killfeed story with a song: "building Legion Killfeed from scratch, surviving smear campaigns, Trustpilot chaos, and still keeping the servers running. Proof beats noise. Every time."
December 19, 2025: Edward Griggs (Crix Madine Jr) appeared in the comments: "Because this clown is so focused on Skynet and can't figure out new features for his killfeed."
Brodie's Response with Evidence: Brodie replied with screenshot evidence showing Griggs' previous suicide encouragement:
Eddie Griggs - Today at 12:06 AM: "@aSoul | LEGION KILLFEED You really should just do your kids a favor and just kill yourself. their lives would be better."
Soul | LEGION KILLFEED - Today at 12:06 AM: "Probs will eventually Crix."
Eddie Griggs - Today at 12:07 AM: "As far as your slut wife, who gives a fuck."
Eddie Griggs - Today at 12:09 AM: "Look who touches their own kids."
Eddie Griggs - Today at 12:09 AM: "Idk Ask your kids. you are the one that raped them. Sick fuck"
Brodie's reply: "Eddie you know how stupid you look when you lie don't you? Like c'mon Griggsy, you know better by now."
Community Support: Other commenters rallied:
- George: "I remember the day the work logs went public. 'but we've been doing all the work'. Barley logged on compared to your logs."
- ROOSTER: "Man you helped me when I was a struggling console owner, I'll always speak good on your character and attitude. Keep going friend you got this!"
This demonstrated harassers were active across multiple platforms (Discord, Facebook, TikTok) with a consistent pattern: false accusations about children, suicide encouragement, and targeting family members.
22 December 2025: Fraudulent DMCA and Search Amplification
On 22 December 2025, Brodie preserved a fraudulent DMCA-style mirror on aggropvp.com alongside the surrounding Discord and video record. The problem was not merely that a fake takedown page existed. The page could be made public long enough for Brodie to capture or share it and then reverted, allowing the later live URL to be used to claim that his screenshot was fabricated. The archive therefore preserves the page captures and surrounding material together rather than relying on what the URL displayed later.
22 December 2025: AI Laundering
By 22 December 2025, a Google AI-style summary about Legion Killfeed circulated repeating a bundle of community accusations as if they were a neutral overview:
- Claims about "server sabotage"
- "Rude or unprofessional" support
- Token handling
- Arbitrary bans
- Rivalry with Skynet
The shift here was important: once a false claim becomes "the controversy," AI summaries can launder it into something that reads like established background, even when the underlying source is a harassment post.
23 December 2025: eSafety Complaint Renewed
On 23 December 2025, Brodie filed a renewed complaint to the Australian eSafety Commissioner's cyber abuse team (receipt ACA-2025-0729927), explicitly challenging a closure decision that treated the matter as "purely reputational harm."
That same day, Brodie also preserved paperwork relating to a Lumen defamation complaint routed to Google and a Google takedown request reference (7-4274000039113), tying the harassment story to search visibility. The point was not that Google authored the accusations, but that search and automated summaries were amplifying them as if they were neutral background, which is how a smear escapes the original platform and becomes ambient reputational damage.
eSafety Commissioner's Response: Referred Brodie to counseling services. The government regulator tasked with addressing cyber-abuse refused investigation and provided a mental health referral instead.
The complaint had documented:
- Coordinated cross-platform harassment (5+ individuals, 3 countries)
- Commercial competitor orchestration (Danny Hayes/DayZ Skynet UK, Mathew Trojanowski/DayZ Skynet, Edward Griggs/BigFatMods, Joel Walker/competing server)
- Doxxing website (AggroPVP.com with residential address)
- Platform republication after notice (documented repeated instances)
- Mass brigading (33,000-member group)
- False reporting campaigns
eSafety's Response: "We know this has been a difficult time for you."
Brodie referenced an earlier 2024 complaint where eSafety had treated the situation as serious targeted abuse. His argument was simple: the conduct continued, escalated, and spread across platforms. The "reputational harm only" framing did not match the reality of doxxing, child-image targeting, and coordinated intimidation.
Late December 2025: External Reporting Channels
By 27 December 2025, the month ended in the same loop that had defined the entire second half of 2025: platforms acknowledging the complaint without acting, while Brodie kept sending escalating documentation.
In the same period, Brodie lodged a Scamwatch report about aggropvp.com that was assigned a reference number, pushing the harassment websites into yet another external reporting channel.
December closed with the campaign still active across Discord, Trustpilot, Meta, Reddit, hostile websites, and now automated search summaries - and with the burden still sitting on the target to keep proving, again and again, that the same recycled accusations were not "controversy," but a deliberate pattern.
December 2025 public video record
Part Eleven: January 2026 - The Coordinated Attack Keeps Moving
January did not begin a new dispute. The same code-theft conflict, competitor accounts, suicide and child targeting, Trustpilot review cycles, hostile domains and reporting abuse moved into new posts, search results and enforcement systems. The events below show the connections that the platforms kept splitting into isolated tickets.
Cause and effect: Griggs renewed the Skynet-linked attack with the earlier suicide encouragement, comments about Brodie's children, partner attacks and paedophilia smears still forming its context. Purple Hats contacts obtained Brodie's details, a mass-report or lag-switch file was then spread through Legion's Discord, and reports produced restrictions against Legion. Discord later removed some violations, but only after support was interrupted; Meta, Google and Trustpilot separately retained or redistributed related publications. Treating each event as a new ticket concealed the shared people, language and commercial target.
1-3 January 2026: Trustpilot cases continue and Purple Hats obtains details
Trustpilot case 00843340 continued on 1 and 2 January through a support follow-up and the same unresolved thread about edited content, re-flagging lockouts and the Hooded_saw review. On 3 January, messages record a Purple Hats contact asking a friend for Brodie's details, receiving them and passing them on. Those messages matter in light of the later June impersonation, partner-name spam and entry into Legion's Discord.
5 January 2026: Griggs reopens the suicide and child-targeting record
Edward Anthony Griggs Jr., using the Crix Madine Jr. identity, entered Legion's TikTok comments with the same Skynet-versus-Legion attack. Brodie answered with the earlier Discord exchange in which Griggs told him to kill himself, referred to his children, attacked his partner and used child-sex-abuse smears. The new comment deliberately pulled that conduct into another public feed; it was not a standalone product disagreement.
5 January: Paper Crown, Paper KingsGriggs, Skynet and the preserved suicide and child-targeting context.6 January 2026: Trustpilot refusals, shared infrastructure and hostile domains
Trustpilot cases 00780964 and 00843340 refused to resolve the edited-review and reporting-lockout problem. On the same date, DNS, support-chat and website captures for aggropvp.com, dayzskynet.com and skynetvslegion.com preserved the shared infrastructure trail. Skynet pages advertised features that were unavailable, while its own support material connected the sites and hosting. Brodie also sent the ACCC the contradictory ABN record, the retaliatory-edit workflow and the disappearing flag-history issue.
6 January: Same IP Same GameShared infrastructure and hostile-domain connections.7-8 January 2026: Legal notice reframed and copied tools preserved
Joel Walker circulated or discussed a Bohemia Interactive cease-and-desist notice as persecution, repeating the tactic of turning formal accountability into a sympathy narrative. On 8 January, ACCC correspondence returned Brodie to general pathways that did not stop the conduct. Dated captures also show Kamikaze planning or reproducing Legion's search, compare, wiki and teleport-tool ideas. A Google removal record in case 7-4274000039113 connects that competitor history to the search-distribution problem.
9-11 January 2026: The evidence reaches customers and TikTok
A subscriber originally asking about DDoS defence was shown why code provenance, review attacks, doxxing, family threats and platform refusals had become part of Legion's daily support burden. TikTok posts then presented the code history and preserved receipts publicly. On 10 January, a Promote campaign was approved and then removed after Griggs engaged with the content and was blocked. Brodie preserved the approval, analytics, removal notices, ticket replies and later restoration rather than treating the lost promotion as an unexplained moderation event.
12-13 January 2026: Mass-report and lag-switch tooling produces enforcement
A Discord account posted a file described as mass-report and lag-switch tooling across several Legion channels and encouraged users to report the server. The preserved account name, user ID, channel spread, file link and messages linking Feather to the Bypass account show the tactic and the people around it. Discord restrictions and account-standing notices followed. Later violation-removal notices reversed some of the punishment, but only after Legion's business account had been interrupted. A 13 January Lumen record added another public search surface to the same dispute.
14-17 January 2026: Google refuses removal while Griggs repeats the attack on Facebook
Google records on 14 January said complained-about material could not be found or would not be removed even though the result and source captures had been supplied. On 17 January, Griggs repeated the same taunt under current and older Legion Facebook posts about Trustpilot, the ACCC, TikTok and Project Jackelope. Brodie posted the preserved suicide-incitement context on the Crix Madine Jr. page. KaLee Whitmore's reply that photographs of Brodie's children had been shared connected the fresh Facebook comments to the established family-targeting campaign.
19-24 January 2026: Griggs reviews cycle and a former Kamikaze administrator supplies context
Griggs-related Trustpilot reviews were posted, flagged, edited, taken offline, updated and appealed through several case records. Each change renewed the purchase-stage damage and required another screenshot or appeal. During the same period, former Kamikaze administrator MWFJunkie69, contacted through the iDieBoo Xbox account, supplied context about FTP access, Azzy, Anon PVP, the harassment and the code-theft history. His account directly contradicts the later effort to rewrite the original business split as Brodie attacking an unrelated competitor.
31 January 2026: Meta exports, Oversight Board filing and bulk-report connection
Meta support-inbox exports from three accounts preserve reports involving Daniel Santos, Joel Walker, Brett Jones, Griggs and related Facebook posts. Santos and Jones were customers, but Santos also sold paid DayZ modding services and Jones later joined the pile-on after a direct-message-permission dispute. Adam Cooper was never a customer; he published third-party amplification inside the Facebook group and campaign chain operated by Joel Walker of Make DayZ Great Again Killfeed. The Oversight Board submission records the escalation after ordinary reports failed. A separate capture of discussion about the Skynet bulk-report group links the month's closing platform filings back to the mass-report tooling and account restrictions from 12 January.
Part Twelve: February 2026 - Review Restoration, Facebook Publication and Google AI
February shows the attack moving between review accounts, Facebook posts, Reddit moderation, Google search and generated answers. Trustpilot's dashboard, case email and public page repeatedly described different states for the same review, while Meta and Google distributed the underlying Facebook accusations beyond their original threads.
Cause and effect: review accounts posted in a shared period, Trustpilot repeatedly changed their visibility, and its interface prevented an effective repeat flag after edits. Meta left the source Facebook claims in circulation; Google then surfaced those claims in snippets and generated answers. Customers consequently encountered the same accusation as a review, a social post, a search result and an automated trust signal, while each platform assessed only its own copy.
2-10 February 2026: Trustpilot closes every reporting route without ending publication
Cases 01086918, 01067484, 01067477 and 00780964 cover Consumer/Hooded_saw, Kamy and Kyle. Consumer and Hooded_saw were posted around the same period as the Kamy reviews; that timing is part of the coordination evidence, not proof that every profile had the same operator. Trustpilot variously called the records filtered, deleted, restored, online, removed or already flagged. Brodie was repeatedly directed back to category-specific reporting even though the interface prevented the same category from being used again after a material edit. The 4 February Hooded_saw screen, dashboard captures and case emails preserve the contradictions between what Trustpilot said and what the public and business interfaces displayed.
Kamy was not an ordinary independent reviewer. Kamy is Mathew Trojanowski, the competing operator behind the code-theft dispute. The review state changes therefore kept a competitor's publication at the point where prospective customers assessed Legion.
4 February: Report Button RouletteThe circular reporting routes and contradictory review states.11-13 February 2026: The flag history proves repeated reinstatement and Kyle returns
Two recordings preserve Trustpilot's flagging activity, including three reinstatements for one review and an eleven-removal history across Havasu, Karl Messer, Anthony Buchanan, Mathew Trojanowski and Hooded_saw. The visible history is significant because later support replies treated each appeal as a fresh category dispute instead of the continuation of a known competitor attack.
Separate Skynet captures show six weekly kills alongside a public rank and 1.5 million figure, while the status page showed an hour delay and 73 servers. On 12 and 13 February, Kyle moved through a formal letter, appeal, reinstatement, later offline correspondence and Reddit moderation screenshots. Kyle is another Mathew Trojanowski account. The review restoration and the competing service's public performance claims were therefore part of the same commercial credibility contest.
12 February: Built like a VerdictThe evidence chain and formal response while the reviews were restored.15-16 February 2026: Meta rejects the reports and Google repeats the Facebook accusations
Meta's report history records three rapid rejections beside the underlying Joel Walker and Adam Cooper posts. The source posts said Legion caused reset loops, urged communities using Legion to be banned, promoted competing services, attacked Brodie personally and repeated child-sex-abuse smears. These publications sat inside DayZ groups used by server owners to choose tools. One preserved Walker post said, "Keep defending the kiddy ticklers Legions Killfeed." Another post announced bans for communities using Legion and several other services. The same accusations were therefore being used both as a personal child-sex-abuse smear and as a reason to tell server communities to exclude the product.
Google search, AI Mode and AI Overview then quoted or summarised the DayZ Editors and Facebook material. One result used the neutral title "Setting up legion killfeed on discord?" while its snippet carried the reset-loop accusation, making a hostile Facebook claim appear to be an ordinary setup warning. On 16 February, a DayZ Editors administrator refused to remove a competing-bot recommendation from the same thread, and Brodie issued a formal seven-day notice.
19-21 February 2026: Review status, domain reputation and search trust signals converge
Trustpilot confirmed that the Consumer review had been flagged for defamation while it remained visible, refused an appeal and later confirmed that another false review had moved offline. At the same time, Gridinsoft and Bfore.Ai material marked killfeed.co with a warning. A customer could therefore encounter a one-star review, a generated Google summary and an automated domain warning before ever speaking to Legion. The attack had expanded from direct accusations into third-party trust signals presented as independent.
Part Thirteen: March 2026 - Discord Punishes Legion After Context Is Removed
March contains a concentrated example of the wider method: hostile accounts remove the history that caused a moderation decision, publish the remaining screenshot as proof that Brodie acted improperly, and use the resulting reports to trigger enforcement against Legion's business account.
Cause and effect: alternate accounts and paedophilia insults caused bans; screenshots of the bans were detached from that cause; the shortened version generated reports; Discord then restricted Legion for hateful conduct. Its later reversal confirmed that the first enforcement was not a reliable finding, but it could not undo the customer-visible account restriction or the work lost rebuilding the deleted context.
2-4 March 2026: Mr Glizzy and Silly account history is stripped from the public retelling
The 2 March capture records why the Mr Glizzy and Silly accounts were banned. The 4 March sequence preserves the alternate-account connections, kicks, bans, deleted background and paedophile insults that preceded the enforcement. Once those facts were removed, the remaining ban screenshot was used to portray Brodie as an abusive moderator rather than the person responding to repeated hostile accounts. The preserved sequence includes the paedophile insults themselves, not just the later moderation screenshots, so the reason for the bans remains visible even when the hostile accounts or their messages are later removed.
The same technique appears throughout the campaign. A formal notice becomes persecution, a ban becomes proof of abuse, a business reply becomes an attack, and the threats or false accounts that caused the response disappear from the version shown to the audience.
2 March: Monopoly ModeThe competitive control behind the stripped-context public narrative.5 March 2026: Discord limits the business account and later removes violations
Discord limited Legion's account and issued a hateful-conduct strike after receiving the context-free version. Later notices removed violations and reversed part of the enforcement. The reversal did not restore the hours spent reconstructing deleted context, the interrupted support work, the account standing visible during the restriction or the trust lost when customers saw the business account punished.
This happened after years of documented notice. The January data export retains 30 Discord ticket IDs. Ticket 30339510, opened on 23 November 2022, reported Mason Stockton posting Brodie's address, using alternate accounts and operating an IP-pulling server. Discord thanked Brodie, opened an investigation, encouraged screenshots and further IDs, and IP-banned Stockton. The original report was later scrubbed from Brodie's account but survived in the data export. Discord's later enforcement against the reporting account therefore followed a record in which the platform had already acted on the same aggressor and asked Brodie to preserve the material.
Discord ticket IDs retained in the export
17624761, 18064826, 20701184, 30339510, 30414871, 39629296, 39648357, 39683754, 42296956, 42297180, 42297244, 47695614, 56784327, 58942905, 61451054, 61451498, 61451749, 61465755, 61691061, 61770202, 61771050, 61771054, 61942766, 61943102, 61943467, 61973127, 61977122, 62150638, 62421836 and 62422711.
12-23 March 2026: Public response after Discord's enforcement
The later March posts followed the account strike and partial reversal. They show Brodie continuing the public record after Discord had punished the reporting account and left him to reconstruct the deleted context.
Part Fourteen: April 2026 - Search Publication, Legal Removal and Regulator Escalation
April records how the coordinated attack became search information. Google did not only surface Mathew Trojanowski's Reddit post. It carried Facebook posts, hostile DayZ pages, Trustpilot material and the skynetvslegion.com and AggroPVP.com domain trail through ordinary results, mismatched snippets, AI Mode and AI Overview. Brodie's legal notices therefore addressed the whole publication chain.
Cause and effect: competitors and associated accounts published accusations on Reddit, Facebook, Trustpilot and hostile domains; Google selected, ranked and summarised that material for Legion searches; legal-removal staff repeatedly broke the connected record back into URLs and requested details already supplied. The result was a larger audience and an appearance of independent confirmation: several search features repeated one underlying campaign.
5 April 2026: Mathew review edit preserved
Two browser captures preserve Mathew Trojanowski's Google-facing review and its edit state. One records the publication before the change and the other preserves what Google displayed afterward. That pair prevents a later current-page view from erasing the wording that customers previously saw and ties the review to the same competitor account history already documented on Trustpilot, Reddit and Skynet.
5 April: The Legion Killfeed Setup FlowA working product demonstration answering the sabotage and reliability claims.14-19 April 2026: Google case 1-3859000040385 and Joel Walker material
The legal-removal thread for 1-3859000040385 records Google asking again for exact text, screenshots, URLs, applicable law and an explanation of harm while the result remained discoverable. Brodie supplied the Reddit publication, Facebook source posts, snippets and account connections. The 18 and 19 April records add Joel Walker's Trustpilot publication, promotion of competing bots, meth and children-related insults, Legion, DayZ++ and DayZ Multi Tool posts, a Lumen record and repeated removal demands.
A separate 14 April capture shows the practical form the older FTP/data allegation had taken: a community message said Legion would not return because its owner was supposedly known to get information from servers and sell it to other servers. That allegation presents installing Legion as a security risk to a server owner, so it had a direct ability to affect whether communities would use the service while the Google and Reddit removal process was still ongoing.
Google's handling forced the coordinated attack back into isolated URLs even though the search results displayed the same names, services and accusations. The same Facebook claim could appear beneath a neutral search heading, a hostile domain could rank beside Legion, and a later AI answer could restate both as if Google had independently verified them.
20-24 April 2026: Page-one results, AI output and selective moderation
A 20 April capture shows hostile material on page one. The following records preserve Google's refusal, Reddit moderator conduct, the connection between Brief_Ordinary1438 and Mathew's Anon PVP promotion, Facebook posts promoting competing services, and AI Mode output. A neutral-looking result titled "Setting up legion killfeed on discord?" carried a Facebook-derived reset-loop accusation in the snippet. Other captures show skynetvslegion.com, AggroPVP.com and competing-bot material in the same search environment.
The 24 April source-and-result pairs preserve the Facebook post, the wording Google selected and the generated summary together. They show publication, not an abstract concern about ranking: Google lifted hostile wording from the coordinated campaign and placed it in front of users searching for Legion help.
22 April: How to do a No Name DayZ ServerA working Legion feature published while hostile Google results attacked product reliability.25-28 April 2026: eSafety, Ombudsman and Reddit Legal
On 25 April, Brodie compiled complete publication packets concerning Joel Walker and Mathew Trojanowski, challenged eSafety's treatment of doxxing, family targeting and coordinated abuse as a reputation-only dispute, and escalated the handling to the Commonwealth Ombudsman. The packets joined source posts, account identity, report history, search results and harm rather than submitting another bare URL.
On 28 April, direct Reddit Legal correspondence and a preservation demand recorded that ordinary moderation had failed. Reddit had the January 2024 thread, its comments, the report and ticket history, the banned Legion profile, the account-link evidence and the later Google results. The demand required the publication and decision trail to be retained for legal proceedings.
30 April 2026: Repeat Google demand and Boosterz dispute
Another Google demand sought human review of the source pages, snippets and generated answers that remained visible after repeated submissions. On the same date, the Jarvis, Sauce and OzzieHousos DayZBoosterZ transaction was preserved through payment messages, competing-service discussion, missing context, deleted-message patterns and a screen recording. Ronald Lund's PayPal purchase of DayZBoosterZ.com and the related email trail identify t.showler. That supports OzzieHousos being Taylor Showler. The Anthony Buchanan name appeared on the competitor review immediately after OzzieHousos used UntoldTruthy to call Brodie a paedophile when Brodie refused to work with him.
Part Fifteen: May 2026 - Concerns Notice, Search Refusals, Partner Targeting and Ray Smith
May combines formal legal notice with continuing public escalation. Reddit blocked or removed rebuttal material while keeping the hostile publication available, Google continued distributing Facebook and hostile-site material, Joel Walker used Brodie's partner in the public dispute, and Ray Smith converted a support argument into a one-star publication that contradicted the preserved Discord chronology.
Cause and effect: Reddit suppressed rebuttal material but retained the accusation; Google continued to surface it alongside Facebook and hostile-domain claims; Walker's known reference to Brodie's partner moved from social posts into search. Separately, Ray Smith was told within 19 minutes of subscribing that the shop feature did not work, removed Legion himself, and later published the opposite access chronology. Platform publication converted both disputes into customer-facing reputation damage.
2-5 May 2026: Selective Reddit moderation and evidence packets
Reddit screenshots show Brodie's rebuttal material blocked or removed while Mathew Trojanowski's hostile thread remained available. The sequence preserves two distinct account chains: Obviously_Mario's staged beta setup and token sabotage, and Brief_Ordinary1438's connection to the Anon PVP promotion. The packet also preserves DayZ Multi Tool and competitor posts, contradictions, the banned-account view, direct Reddit correspondence, Lumen notices, Google complaints and grouped source packets. Reddit left the accusation searchable while denying the affected business an equal ability to keep the rebuttal visible.
The evidence packets joined the original publication, the account links, moderation decisions, report receipts, Google results and business harm. They were necessary because both Reddit and Google repeatedly reduced the connected record to one URL or one report category and then said the supplied information was insufficient.
6 May 2026: Concerns Notice and multi-case Google bundle
The formal Concerns Notice under the Defamation Act 2005 identifies the publications, false imputations, recipients, account connections, serious harm and required correction. The accompanying Google bundle ties the Reddit thread to the Facebook posts, skynetvslegion.com, AggroPVP.com, search snippets, generated answers and multiple removal case numbers. It put the connected campaign and search-distribution chain on formal notice.
The correspondence was not a handful of emails. The current Google scorecard records 220 counted handling entries, 71 evidence rows, 71 ticket references, 77 reported or reviewed URL entries and 19 unique ticket/request IDs. Google was repeatedly sent the publications, screenshots, account links, business records, search captures and legal explanation, then asked Brodie to resupply details already present in earlier cases.
6 May: Oops (I dropped the proof again)The Reddit ban, formal notice and suppressed rebuttal record.7-10 May 2026: Partner references, edit history and search indexing
A 7 May capture proves Joel Walker knew about Brodie's fiancΓ©e's heart condition. The 9 May sequence preserves Walker's direct messages, his reference to Brodie's partner, the Facebook post before editing, the group-share context, the later edit and screenshots contradicting his explanation. By 10 May, Google indexed the same material and language. The partner reference therefore travelled with the business accusations into search; it was not confined to a private exchange.
16-20 May 2026: Purple Hats connection and repeated Google refusal
Feather's 16 May message records the breakdown involving Rage and Purple Hats and supplies context for the accounts that later entered Legion's Discord. Google refusals on 18 and 20 May again treated the source pages and search features in isolation. Brodie had already supplied Facebook posts, hostile domains, screenshots and legal explanation, yet the same campaign remained visible through results and snippets.
16 May: Gossip Hotline (I would too)Joel Walker's edits, partner reference and missing context.24-25 May 2026: Meta report and another Google refusal
On 24 May, Brodie preserved a Meta defamation report concerning Aaron Hafer and the source publication it addressed. On 25 May, another Google response continued the refusal chain. These were not unrelated platform tickets: the Meta publication supplied material that Google could index, and the Google result expanded the audience beyond the original Facebook group.
25-28 May 2026: Ray Smith removes Legion himself, then reverses the chronology in a review
Within 19 minutes of subscribing, Ray Smith was told that Legion's shop or trader feature did not work. Legion's Discord had fewer than 50 members. Ray asked whether Legion could run alongside DayZ++ so he could use DayZ++'s shop, and repeatedly offered to pay for work Legion did not advertise or charge for. Brodie explained that Legion itself remained operational, that the one trader function was unfinished and that Legion would not operate with DayZ++. Ray said he would remove Legion and return when the issue was fixed, then removed the bot himself before the argument continued. The small server, rapid disclosure and attempts to purchase unoffered work show that Smith manufactured complaint bait. The record attributes that conduct to Smith himself and does not invent a second operator.
During the argument, Ray treated a Legion Support Manager bot line, generated in reply to Brodie's own message, as if Brodie had personally sent it. The full screenshot identifies the automated account and shows Brodie immediately explaining the source. Ray's later Trustpilot review said Legion revoked his access with paid time remaining, treated the bot's "crayons" response as Brodie's direct insult and described the whole service as down. Each point is contradicted by the preserved Discord sequence.
On 27 May, Trustpilot rating captures show the review's effect on Legion and DayZ Multi Tool. On 28 May, the review, profile, reply, alternate-account trail and Google refusal were preserved together. Ray was a genuine former customer, but his review republished false facts and later became two visible reviews with materially worse accusations.
Part Sixteen: June 2026 - Rating Damage, Coordinated Discord Interference and Search Refusals
June links the search, review and Discord branches of the attack. Google continued demanding proof already supplied, false reviews visibly reduced Legion's ratings, Meta retained the Facebook report history, and the Purple Hats or Bypass account chain moved from collecting details in January to entering Legion's Discord and causing a customer-facing client problem.
Cause and effect: Purple Hats or Bypass moved from obtaining personal details to impersonation, partner-name spam and disruptive content inside Legion. A customer then experienced the client problem created by that interference. Feather's screenshots show the attack brag and a mirror server labelled βwith love - The Collectiveβ; separate records identify The Collective as Mathew Trojanowski's current server. That chain connects the attack to Mathew's circle, while the operator of the attacking account remains unidentified.
1-2 June 2026: Google case 7-1475000041317 receives proof and still does not resolve the search attack
The 1 June case record and 2 June follow-up preserve Google's demand for proof that the domain owner had been contacted. Brodie supplied that proof and again identified the source material and legal problem. The response still did not remove or correct the connected Facebook posts, hostile domains, snippets and generated search answers. A second 2 June record documents the contradiction between Google's stated handling and the material that remained available.
3-5 June 2026: Trustpilot rating damage, Meta reports and Google case 6-6692000040714
On 3 June, side-by-side Trustpilot captures show the disputed one-star reviews reducing the public ratings of both Legion Killfeed and DayZ Multi Tool. The damage was therefore visible on the business profiles, not a theoretical concern about future publication. On 4 June, Brodie preserved the Meta report history tied to the Facebook accusations. On 5 June, Google case 6-6692000040714 continued without resolving the hostile results.
13-14 June 2026: Purple Hats spam, impersonation, client lag and mass reporting
The 13 June sequence identifies the Purple Hats or Bypass account attacking Keta, using Brodie's fiancΓ©e's name in spam, adding Brodie, entering Legion's Discord and bragging about the attack in messages shown by Feather. The brag included a mirror of Brodie's DayZ server described as βwith love - The Collective.β Separate captures identify The Collective as Mathew Trojanowski's current server. Together they connect the attack toward Mathew's circle without establishing who personally operated the Purple Hats account. The preserved evidence includes the account identity, the links between participants, the exact spam sent into Legion and the warning placed in the business Discord.
The injected content was designed to create client lag, trigger repeated processing and encourage mass reports. On 14 June, Brodie consolidated the account, message and technical sequence into a coordinated client and mass-report abuse report under Discord ticket 66248829. A customer then reported that the client was having problems. The customer-facing failure is the operational endpoint of the attack: hostile accounts entered the platform used to deliver Legion and interfered with the service in front of its users.
16 June 2026: Formal Trustpilot removal demand
The removal demand identifies the false review, its false factual content, the competitor and campaign context, the prior moderation history and the continuing damage. Trustpilot was required to remove the publication and preserve its moderation and account records. The later July restorations and consumer warning occurred after this formal notice.
20-22 June 2026: Google refuses again while Joel Walker and Skynet remain visible
On 20 June, Google correspondence in case 6-6692000040714 and a result capture show that the complaint remained unresolved. On 22 June, Joel Walker's publication was still visible and Skynet still appeared in search. These captures connect the source Facebook attack, the competing service and Google's public result on the same date.
30 June 2026: Search comparison immediately before the July review burst
The 30 June set records Google results for DayZ++, Law's, Legion and Skynet under the same search conditions. It shows how Google presented the competing services and hostile material immediately before Kyle and Killfeed review appeared four minutes apart on Trustpilot. The search comparison preserves the market effect of ranking and snippet choices, not merely the presence of one Reddit link.
Part Seventeen: 1-25 July 2026 - Review Burst, Privacy Escalation and Further Enforcement
July is the point where Trustpilot moved beyond repeatedly restoring third-party attacks and made its own adverse publication. Kyle, Killfeed review, Anthony and Ray Smith appeared or changed while Google continued distributing the older campaign. Trustpilot read the legal notices, reversed Brodie's profile wording, copied Revenue Technology, threatened Legion over its own website and published a consumer warning.
Cause and effect: the Trustpilot campaign had already appeared directly as Mathew, as Kamy, through Kyle, through Killfeed review and through the Anthony account presentation. Two of the July reviews appeared four minutes apart. Trustpilot restored false reviews after receiving the identity, chronology and legal notices, then objected to customer comments displayed on Legion's own site and placed its own warning on Legion's profile. Google continued surfacing the older accusations at the same time. Third-party reviews, a platform-authored warning and search distribution confronted prospective customers together.
1 July 2026: Google comparison records the market immediately before the review burst
Google results for DayZ++, Law's, Legion and Skynet were captured under the same conditions. The comparison preserves how Legion and its competitors appeared after months of complaints about Facebook posts, Reddit, skynetvslegion.com, AggroPVP.com and AI-generated summaries. The next morning, two Mathew Trojanowski accounts posted one-star reviews four minutes apart.
2-3 July 2026: Kyle, Killfeed review and Anthony are Mathew Trojanowski
On 2 July, Kyle posted a one-star review at 8:16 AM and Killfeed review posted another at 8:20 AM. Both followed the same sequence of generic complaints about access or navigation, mobile display, colour and readability, and distracting design. The Killfeed review profile contains a 1 July 2023 TeamViewer review in which TeamViewer replied to the account as "Mathew". The account history, matching structure and campaign chronology identify both Kyle and Killfeed review as Mathew Trojanowski.
On 3 July, Trustpilot sent a further one-star notification under the name Anthony. That Anthony review account is also Mathew Trojanowski using Anthony Brodie's name presentation. The source set preserves Trustpilot's notification and the linked legal notice. No public profile capture currently fixes the length of time that version was visible.
3-5 July 2026: Trustpilot threatens Legion over customers' words on Legion's own website
Trustpilot accused Legion of scraping, demanded removal within seven days, directed the business to widgets in the "Share & promote" area of the Trustpilot Business account and threatened a warning or consumer alert. Legion displayed selected positive customer comments on its own business website as ordinary text about its own product and service. It used no Trustpilot logo, star graphic, TrustScore, rating, TrustBox, widget, API, screenshot, page design or other Trustpilot material. The initial heading "Trustpilot Reviews" was changed to "Product & Service Reviews", removing Trustpilot's name.
Trustpilot has no ownership right over customers' words about Legion and identified no exclusive copyright, trade mark, database right or contract giving it control of those words. Trustpilot used a legal threat, a profile-warning threat and access to its paid subscription and display products to force Legion into a paid Trustpilot relationship. That is criminal commercial coercion and attempted extortion.
6-8 July 2026: Trustpilot restores the attack after receiving the legal notices
On 6 July, Trustpilot put false reviews back online and sent decisions concerning Ray Smith and the Mathew accounts while appeal 02950802 was open. On 7 July, Trustpilot continued ignoring the connected legal demand in that appeal. On 8 July, another Ray Smith decision again treated the review as an isolated flag rather than the next publication in the preserved support and review chronology.
The reinstatement audit records 76 decisions through 5 July 2026. Six later decisions occurred on 6, 9 and 13 July: Ray Smith and Kyle on 6 July; Kyle case 02961099 and Ray Smith case 02649286 on 9 July; and Ray Smith cases 02953866 and 03012716 on 13 July. The minimum through 13 July was 82 reinstatements or reactivations. Four further express keep-online decisions on 16, 17 and 20 July raise the minimum to 87 through 25 July.
9 July 2026: Google continues the search attack and Trustpilot confirms more reactivations
Google case 6-6692000040714 again demanded country and legal details already supplied. Screen recordings and result captures show the complained-about Reddit material still displayed, while global-sales records show that Legion served customers outside Australia and the search damage was not confined to one country. The same date preserves Skynet server and player-stat displays and the source captures used to test them.
Trustpilot confirmed reactivations in 02961099 and 02649286. Those decisions returned Kyle and Ray Smith material to publication while the account links, Discord chronology, legal demands and four-minute review pair were already in Trustpilot's possession.
10 July 2026: A second Ray Smith review rewrites the Discord exchange
Trustpilot notified Legion of another Ray Smith one-star publication. It said Brodie revoked access with sixteen paid days remaining and personally sent the "crayons" line. The preserved Discord exchange proves that Ray removed Legion himself before the argument and that the Legion Support Manager bot generated the line in reply to Brodie's message. The review also invoked Reddit material and called identification of Ray as a UK user location tracking.
10 July 2026: Skynet's public boast fails its own arithmetic
Skynet Killfeed replied to a Legion TikTok with "Our killfeed is still better". Brodie's response tested Skynet's displayed statistics instead of accepting the boast. On a server leaderboard, every PvP kill is another player's PvP death, so the combined server kill-to-death ratio must equal 1.00. Skynet's displayed totals did not reconcile. Its second-ranked global player was shown with about 5,000 kills in 57 minutes, which would require more than one kill every second for nearly an hour. The damage per kill, headshot rates, playtime, totals and scores also fail basic consistency checks. The displayed figures therefore cannot represent genuine gameplay statistics as presented.
Better at what, Mathew?The calculator-led breakdown of Skynet's impossible leaderboard and server totals.11 July 2026: Profile reversal, Revenue Technology and consumer warning
Brodie changed the business profile wording to state that Trustpilot was on legal notice. Trustpilot saw the wording, removed it and sent a profile-misuse email. The enforcement messages copied revenuetechnology+ceur@trustpilot.com. Trustpilot again demanded removal from Legion's own website, directed Legion to its paid subscription and widgets, threatened a cease-and-desist notice and said a consumer warning would be applied.
Trustpilot then published the consumer warning on Legion's profile, telling prospective customers that Legion had displayed Trustpilot content incorrectly. The warning is Trustpilot's own publication. It implies review misuse and manipulation by the business while Trustpilot continued publishing the competitor reviews that triggered the legal notices. Trustpilot committed criminal commercial coercion and attempted extortion by combining legal threats, reputation damage and paid-product direction to force a commercial relationship Legion rejected.
Google also refused the removal case again on 11 July without engaging with the Facebook posts, hostile domains, snippets and generated answers supplied with the complaint.
12 July 2026: The misinformation redirects blame onto the target
A response to the Skynet statistics video asked why the parties were "always competing and fighting" and called it cringe. That framing treated Brodie's evidence-based response as mutual rivalry, omitting the years of suicide encouragement, child targeting, false reviews, doxxing, account attacks and platform inaction that caused the response. It shows a direct reputational effect of the campaign: viewers blame the person documenting the harassment for the public conflict created by the harassers.
13 July 2026: Ray Smith substitutes criminal and regulatory accusations
Ray Smith replaced the review again. The new version falsely described Legion's location and governing business context even though it is operated by an Australian sole trader under ABN 28 387 377 607. It accused Brodie and Legion of deceptive practices, knowingly false competitor claims, report-system manipulation, intentional review suppression, unfair trade practices and lying to bury poor ratings. Trustpilot's claim that the edit addressed the complaint is false; Ray substituted more serious dishonesty and business-misconduct accusations for the disproved access chronology.
A screen recording shows that Trustpilot's interface did not provide an effective way to report the materially edited publication. Trustpilot reinstated the first Ray Smith review in case 02953866 and put the second Ray Smith review back online in case 03012716, treated the edit as resolution, again removed the legal-notice profile wording and copied Revenue Technology. The day preserves Ray's new publication, Trustpilot's own warning, the reporting lockout and Trustpilot's decisions after formal notice.
Recorded profile status on 14 July 2026: four disputed one-star publications are visible: two Ray Smith reviews, Kyle and Killfeed review. Trustpilot's consumer warning is also visible. Kyle and Killfeed review are Mathew Trojanowski; Ray Smith is the separate former customer whose two visible reviews contradict the preserved support record.
14 July 2026: Trustpilot accuses Legion of flagging misuse without identifying a report
Trustpilot's Content Integrity team sent a flagging-misuse accusation. The message listed generic examples of conduct that could amount to misuse, but it did not identify the review, report, date, flag category or statement said to be improper. Without those particulars, the warning could not be checked against a specific report or answered on its facts.
Brodie's reply rejected Trustpilot's misuse charge and explained that the disputed reports concerned false factual claims, criminal accusations, materially edited reviews, duplicate timing and account links. It requested seventeen categories of particulars, including every affected review and report, the exact rule relied on, the evidence considered, the decision-maker and the reason Revenue Technology had been copied into the preceding enforcement correspondence. The PDF preserves Trustpilot's 13 July warning and the complete 14 July response in one thread.
15 July 2026: Open Letter of Claim served on Ray Smith
The nine-page letter expressly accepts that Ray Smith was a customer; customer status is not the dispute. It compares his original review with the materially rewritten publication and sets out the preserved chronology: the shop limitation was disclosed within nineteen minutes, Ray cancelled and removed the bot himself, the later termination occurred under the service terms, and the "crayons" response came from the automated Legion Support Manager account rather than a personal message written by Brodie.
The notice also records that Legion is operated in Australia and that no United States Federal Trade Commission finding against Legion is identified. It demands cessation, correction and evidence preservation, requests an initial response within 48 hours and a substantive response within 14 days, and preserves the accusations and supporting chronology as at service. A separate 51-page PDF captures the public site's pre-notice state so later edits can be distinguished from the version served with the letter.
16-25 July 2026: Profile refusal, continued publication and ignored deletion demand
16 July: Trustpilot's 2:23 AM message said a profile is created when someone searches for a website, that profiles and reviews remain even if a business account is deleted, and that deletion merely returns the page to an unclaimed state. It listed four review states: one under investigation, one kept online through ticket 02997338, one offline, and Ray Smith kept online through case 03012716. Brodie's 4:08 AM rejection copied OAIC matters WEB-CP-26-08655 and CP26/03054 and the Danish Data Protection Agency. It demanded restriction, erasure, correction, the complete profile and review history, automated-decision records, and disconnection of the linked Google account.
Trustpilot's wrong-company decision concerning Kyle is internally dated 16 July at 7:31 PM, although the supplied filename begins 17 July. The message kept Kyle online because Trustpilot found nothing showing the review concerned another business. At 9:39 PM, Trustpilot separately acknowledged that it received Brodie's subject access request on 11 July and said it would respond within one calendar month. The same evidence period preserves the 35-page damages analysis; extending its calculation through 20 July produces a 1,127-day campaign period, 506 evidence dates, 4,048-8,096 mitigation hours, and the updated replacement-labour and developer-cost models.
17 July: at 5:09 PM, case 03058920 kept Killfeed review online; at 5:10 PM, case 03058922 kept Ray Smith online. Both decisions say Trustpilot checked harmful or illegal content, personal information, and advertising or promotional content. The 03058920 filename says Ray Smith, but the body names Killfeed review. That internal text controls. By 25 July, the retained correspondence had reached 607 report/email records, 167 case/thread references and 87 keep-online or reinstatement decisions. Trustpilot's incomplete dashboard is excluded.
19 July: Trustpilot's 3:41 AM notice confirms that Ray Smith did not answer the 15 July correct-domain request by the 18 July deadline, while reproducing the rewritten review's false US-business description and its accusations of deception, lying, review suppression, and US federal-law violations. At 6:04 PM, Trustpilot sent a final cease-and-desist. It called Legion's independent display of customer comments βdisplaying reviews from Trustpilot without our approvalβ, labelled that βcommonly known as scrapingβ, and demanded immediate removal. It threatened, if the display remained after seven days, a minimum six-month consumer warning, a hidden TrustScore, account limits, loss of Trustpilot display rights, stopped search-engine distribution, and possible legal action.
Trustpilot used threatened business harm to force control over authorised customer statements on Legion's own website. That was criminal commercial coercion and attempted extortion. Trustpilot's warning was already public on the captured profile by 20 July while its 19 July notice threatened further account, search and legal penalties.
20 July, 9:29 AM: Brodie's SAR clarification-not a Trustpilot reply-states that every new adverse action forms part of the request already received on 11 July and does not restart the acknowledged 11 August deadline. It demands the internal records behind the Ray Smith publication, blocked defamation reporting, profile reversal, misuse classifications, consumer warning, monitoring of killfeed.co, scraping accusation, cease-and-desist, Revenue Technology involvement, automated classifications, and threatened search and account penalties.
20 July, 9:47 AM: Legion's five-page response rejects the cease-and-desist. It records that killfeed.co used no Trustpilot logo, rating, TrustScore, stars, TrustBox, widget, API, application, scraper, crawler, copied database, or live feed. It identifies the already-published warning as retaliatory adverse action and attempted commercial coercion, rejects forced participation, and demands complete disassociation, withdrawal of the accusations and warning, disclosure of the decision record, and preservation of every relevant record.
Trustpilot continued the abuse that evening. At 6:03 PM, thread NXy4Mr_ddYCh9SeaTrTcG2A again refused complete removal of Legion's profile and reviews, offering only deletion of the Business account while leaving the public profile intact. At 6:41 PM, case 03085556 kept Mathew Trojanowski's Killfeed review online again after checking the same three categories. Brodie's replies at 6:39 PM and 6:44 PM record an immediate suicide and self-harm crisis caused by another pair of template refusals after a year in the same reporting loop.
The killfeed.co capture shows the public result: Trustpilot reversed the legal-notice profile wording, included Revenue Technology in enforcement correspondence, threatened Legion over authorised customer statements and tried to force those statements into Trustpilot-controlled products while its own warning and the false reviews remained attached to Legion's profile.
23 July, 2:17 AM and 2:25 AM: Trustpilot sent two separate notices for the same Ray Smith edit eight minutes apart. Smith expressly withdrew the false FTC and American-policy premise and corrected Legion from a US business to an Australian business. He retained the accusation that Legion lies, suppresses reviews, manipulates feedback, engages in deceptive practices and cannot be trusted. Trustpilot continued publishing that accusation while the restriction, erasure and legal demands remained unresolved.
25 July: thread dOI9wKZuetuDXeNcmgy5KmA preserves Trustpilot's 21 July keep-online decision and Brodie's 25 July reply. Trustpilot relied on the review's intentionally ambiguous wording, stating that a non-specific review does not need to name the business, refused action and redirected Legion to engagement, information requests or another appeal. It ignored the repeated formal deletion demand under GDPR and local law while its forced profile, false warning and the false accusation remained public. This continued the retaliatory adverse action and attempted commercial extortion already underway after notice. Trustpilot had previously misrepresented its ABN position, refused to answer the legal substance and then treated Brodie's anger at its illegal conduct as the problem.
Mathew's child-name account and AltDetector's paid account index
The 16 July composite Discord capture directly shows Soul banning the Xbox name R BRODIE through Legion, with service ID 15770527. In the same dated record, Brodie states that planerylan_s joined after that ban, that its profile displayed Robert Brooks, that the associated-name result included KidKreeperBuddy, and that the shared-server history led through PVP Island, Anarchy++, Purple Hats and The Collective. On that identifier and behaviour chain-not on a similar display name-Brodie identifies Mathew as the person behind the child-name account. This was not competition. It was Mathew extending the campaign to Soul's ten-year-old child.
The AltDetector composite joins two separately dated records. Its upper section is the 20 July 2026 page: $5, $10 and $25 monthly tiers, 494,822 indexed accounts, and 123 protected servers. Its lower section is Kamikaze's 6 June 2023 Discord statement: βEither you pay for a product or you're the product.β The capture compares the later paid account-index service with the earlier statement; it is not presented as one same-day conversation. Soul's two public statements reject the attempt to rebrand code theft, stalking, child targeting, review bombing and platform abuse as ordinary competition and identify the services backing AltDetector.
27-31 July 2026: warning, SAR response and renewed Discord and Xbox targeting
On 27 July, Soul replied to Trustpilot's profile-misuse warning and explicitly recorded the severe psychological harm caused by the forced association, the green-star branding and the threat of further enforcement. The preserved two-page thread includes Trustpilot's warning that profile editing was blocked for 30 days and that continued alleged misuse could lead to a cease-and-desist and further business consequences.
On 30 July at 9:13 PM, Trustpilot said Legion had failed to comply with its cease-and-desist. It restricted the account to replying to and flagging reviews, withdrew permission to use brand marks and TrustBoxes, disabled review invitations and announced a Consumer Warning that would hide the TrustScore. At 11:43 PM, Trustpilot acknowledged that it processed Anthony Brodie's personal data and delivered its subject-access package. The package contains the response email, a four-page document guide, a 184-page communications export, an A-files usage and profiling ZIP, a two-page preference and administration capture and a 21-page business-enforcement export. Those SAR files are stored under /archive/sensi/.
On 31 July, the Consumer Warning was visible publicly on the killfeed.co profile with the rating unavailable and a red misleading-content allegation. A Purple Hats "Bypass" Discord profile screenshot sent to Soul displayed the status "Soul at Legion KillFeed Smokes Meth & Scams." While working on code, Soul also noticed and banned eleven harassment-themed Xbox accounts: urserversuxx886, CryPus e, MajinSoul1823, YrJustBad, BabeChillOut, Diptwich, Lf is tuff, DrunkBlock93, Your to slow302, MrStreetSweepa and TheDenialssd. Their Xbox gamertags appeared to reference Legion, direct insults, wording Mathew had used, Ipswich where Soul grew up, Soul's former alcoholism and 1993 birth year, and his former street-sweeper work. The evidence note records those associations without claiming that the gamertags alone prove who controlled the accounts.
1-5 August 2026: review removal, Discord escalation and OAIC update
1 August: Trustpilot case 01757662 states that a Joel Walker review was flagged as defamatory, the reviewer was asked to edit or delete it, and Trustpilot removed it after the reviewer did not do so. The decision is recorded as a removal but is not used to inflate the conservative 1,038-day publication total without a continuous visibility record.
3 August: a Discord question about SkyNet, Soul's reply and an eye-roll reaction triggered a much longer explanation. The retained thread includes Soul's child-targeting and partner-community allegations, mixed support and pushback, objections to the @everyone ping, and discussion of prior attempts to report the conduct. New Xbox and Legion captures directly corroborate the existence and activity of the R BRODIE gamertag and its visible Robert Brooks profile presentation. Those captures do not by themselves establish who controlled the account. A separate public-record/portfolio composite is preserved as material Soul relied on, but it does not independently prove the asserted family or household relationship.
The same discussion includes Discord Account Standing showing five active violations after the thread. Participants describe the outcome as report-driven enforcement; the screenshot establishes the visible violations and limitations, not the identity or coordination of whoever reported the content.
4 August: the third response capture continues into the next day with more account-standing screenshots and discussion of reporting outcomes, including a participant saying some violations were removed and another saying a report-tool check found an account in good standing.
5 August: OAIC acknowledged a further update to privacy complaint CP26/03054. Brodie says Trustpilot's 30 July SAR response and later conduct left rectification, erasure, restriction and objection requests unresolved and omitted categories of data he had requested. OAIC receipt is documented as intake, not a finding on the merits.
Joined-video note: 2024-06-12-live-recorded-abuse-joined-too-far.mp4 is the joined continuous presentation of 2024-06-12-live-recorded-abuse-1.mp4, -2.mp4 and -3.mp4. It is indexed as a derivative presentation, not a separate fourth event.
Conclusion
This was not a single review, argument or failed support ticket. It was a several-year coordinated campaign following the June 2023 business split, built from stolen code, linked accounts, repeated criminal and business smears, family and child targeting, explicit suicide encouragement, hostile websites, review bombing, false reports and measurable interference with Legion's customer trust.
The connected people reused the same code dispute, aliases and smears across every surface
Stole Legion's code, ran Skynet, used Reddit and multiple Trustpilot presentations, connected to The Collective and used an account carrying Brodieβs childβs name.
Joined Skynet, encouraged suicide, targeted Brodieβs partner and children and repeated the attack through public posts and reviews.
Published Brodieβs address, used Links/Havasu/Pups, posted a competitor review and steered users toward competitors before the AltDetector transfer.
Walker spread paedophilia, meth and sabotage smears; Hayes, Santos and Jones expanded the review/report wave; Ray Smith rewrote a support dispute into false deception and regulatory accusations.
Every major platform received notice; each preserved or amplified a different part of the attack
Trustpilot: 608 report/email records, 168 case/thread references, 87 keep-online or reinstatement decisions and a conservative 1,038 confirmed publication days; forced profile, false warning and legal threats. Meta: 176 reports, 14 tracked posts, eight still visible and 2,342 publication days. Reddit: 52 reports, nine tickets, four admin messages and 883 days. Discord: thirty exported tickets plus 66248829, punishment of the reporting account and lost visible history. Google: 220 handling entries, 71 evidence rows, 71 ticket references, 77 URL entries and 19 request IDs that continued feeding snippets and generated answers.
Referrals and acknowledgements did not stop the publications
eSafety and the ACCC accepted or routed complaints without compelling the platforms to end the publication. Scamwatch recorded the hostile-site complaint without stopping the sites. OAIC matters WEB-CP-26-08655 and CP26/03054 and the Danish Data Protection Agency escalation were active while Trustpilot refused disassociation, continued the reviews, published its warning and threatened further business harm.
People and conduct
Mathew Trojanowski and Edward Anthony Griggs Jr. remain central through the code-theft dispute, hostile sites, account networks, child-targeting and repeated cross-platform accusations. Joel Walker, Mason Stockton, Anthony Buchanan and others are documented in distinct evidence chains. Ray Smith enters later as a genuine former customer whose repeatedly edited review contradicts the preserved support chronology and ultimately publishes new dishonesty, regulatory and unlawful-conduct accusations.
- Doxxing and family targeting: home-address publication, partner references, use of children's images and threats to expand the targeting.
- Suicide encouragement: explicit messages telling Brodie to kill himself and platform tickets showing the psychological consequences.
- False criminal accusations: repeated child-sex-abuse and rape smears used because they trigger public hostility and threats.
- Business interference: competitor reviews, search indexing, hostile sites, copied tools, report abuse and customer-facing service disruption.
- Evidence suppression: removed rebuttals, deleted messages, inconsistent review states, repeated flag loops and enforcement against the reporting account.
Platform response record
Meta repeatedly rejected reports or sent the business back through forms it had already used. Reddit banned one of Brodie's profiles while leaving the hostile thread online and ignored repeated legal notices. Google claimed material was fixed or unavailable, then continued distributing it across 19 unique ticket/request IDs, 71 ticket references and 77 reported or reviewed URL entries. Discord's record reached 31 tickets, including the 2022 report that led to Stockton's IP ban, yet Discord later punished the reporting account and restored only part of its standing. Trustpilot's preserved correspondence contains 608 report/email records, 168 case/thread references and at least 87 keep-online or reinstatement decisions. It restricted reporting, refused complete removal, kept Kyle, βKillfeed reviewβ and Ray Smith material online, published its own consumer warning and threatened a hidden TrustScore, account restrictions, removal from search distribution and legal action.
Damage is directly recorded
A customer's written statement says the Facebook and Trustpilot rumours made him uncomfortable and the volume of public drama caused him to cancel Legion and use another bot. After Brodie showed him the complete evidence, he concluded that Legion was not at fault and returned. The cancellation records the campaign changing a customer's purchasing decision; the later return records the additional unpaid work required to reverse it. Rating changes, interrupted support, customer client problems, lost promotion, repeated report preparation and time diverted from development record the wider commercial damage.
Every reversal consumed more working time. Every restoration reopened the reputation damage. Every template refusal forced Brodie to research, draft, fact-check and send another evidence packet while operating Legion alone. The attack remained active through the four visible Trustpilot reviews, Trustpilot's own warning, Facebook publications, the Reddit thread, hostile domains, Discord interference and Google's continuing distribution.
The quantified replacement-labour valuation is A$1,402,584 to A$2,629,674, with a moderate figure of A$1,967,223; the alternative developer-rate model is A$1,524,024 to A$3,398,794, with a moderate figure of A$2,331,543. The required outcome is complete removal and access prevention, public correction and vindication, preservation and disclosure of the platform and account records, compensation for the full economic and aggravated harm, interest, and costs reflecting the rejected A$1,007,000 Calderbank offer. The coordinated attack and the platform decisions that kept it alive remained active in the preserved record through 5 August 2026.