Connected evidence · updated 14 July 2026

One campaign, connected across people and platforms

Former collaborators and competing services supplied accusations, aliases multiplied their apparent support, and platform decisions kept the material visible after repeated reports and formal notices. The preserved records connect those stages.

Accounts and identities

Aliases and account histories allowed the same accusations to appear as separate voices while obscuring commercial relationships.

Account and publication trail

Mathew Trojanowski across Kamikaze, Kamy, Skynet and the review accounts

Mathew TrojanowskiKamikaze / Kami / KamyBrief_Ordinary1438Kyle / Killfeed review / Anthony

The records join Mathew Trojanowski to the Kamikaze, Kami and Kamy presentations, the Brief_Ordinary1438 Reddit account that promoted Anon PVP, the Skynet operation, and the Kyle, Killfeed review and Anthony Trustpilot presentations. The TeamViewer profile capture supplies the direct link between Mathew and the Killfeed review account. The repeated account presentations made the campaign look like complaints from more independent people than the evidence supports.

Documented account link

Brief_Ordinary1438 and Anon PVP

Mathew / Kamikaze historyBrief_Ordinary1438Anon PVP promotion

The Reddit/account evidence connects Brief_Ordinary1438 to the Anon PVP promotion.

Documented conduct

Obviously_Mario's staged setup

Working beta token“Bah Bah Black Sheep”empty-server role changes

The account configured the killfeed successfully during beta, waited about a day, then replaced the working token while Brodie was watching the console. After the bot was removed, the account invited it back to an empty server and shifted from presenting as a mother to presenting as a child. It also denied knowing Soul despite years in Soul's server.

Staged complaint sequence

The working setup, deliberate token replacement, empty server and changing roles support deliberate complaint-baiting or sabotage.

Documented account link

Anthony Buchanan, OzzieHousos and UntoldTruthy

OzzieHousos admitted the UntoldTruthy account and used it to call Brodie a paedophile after Brodie refused to work with him. The Anthony Buchanan competitor review followed directly afterwards. When Ronald Lund later bought DayZBoosterZ.com, the PayPal purchase and email trail identified t.showler, supporting that OzzieHousos may be Taylor Showler while Anthony Buchanan was the name presented on the review.

Documented relationship

Joel Walker and Adam Cooper

Joel WalkerMake DayZ Great Again KillfeedAdam Cooper post context

Joel Walker operates Make DayZ Great Again Killfeed. Adam Cooper has never been a Legion customer. His publication appeared within Walker's group and campaign context.

Publication connection

Cooper had never subscribed and posted inside Walker's group in the surrounding campaign context. That supports the appearance that Cooper posted on Walker's behalf; no direct agency admission has been found.

Identity and ownership trail

Mason Stockton across Links, Havasu, Pups, Whitelist.gg and AltDetector

Mason StocktonHavasu / Links / LinksypooPupsWhitelist.ggAltDetector transfer

The DayZ++ profile shows Links / Linksypoo saying “I run whitelist.gg” while holding the DayZ++ Partner role. A Whitelist.gg purchase notification then ties the Havasu account to masonstockton@outlook.com. The Havasu Trustpilot review promoted DayZ++, Laws and Hulks while attacking Legion and was published while Stockton operated the competing Whitelist.gg service. Later records describe AltDetector as the successor to Whitelist.gg and show Links announcing that Kamikaze would take over AltDetector.

Commercial and working relationships

The central accounts were not commercially detached observers. They worked together around DayZBoosterZ, Skynet, DayZ++ and other competing killfeed services.

Documented shared history

The DayZBoosterZ collaboration cluster

Mathew Trojanowski+ Edward Griggs+ Mason Stockton+ Anthony Buchanan+ Ronald Lund DayZBoosterZ

The record places Trojanowski, Griggs, Stockton, Buchanan and Lund as staff, partners or collaborators around DayZBoosterZ at one point. Griggs also acted as Skynet staff; Buchanan operated in the DayZBoosterZ competitor chain.

Coordinated working history

The records establish shared access, staff roles and commercial collaboration. Individual publications and attacks are linked separately by their own dated evidence.

Documented commercial link

Mason Stockton: Whitelist.gg, Pups, DayZ++ and customer steering

Stockton operated Whitelist.gg while holding a DayZ++ Partner role. His Havasu review attacked Legion and expressly promoted DayZ++ and other alternatives. The Pups account was then used to approach Legion supporters or customers and steer them toward DayZ++. The same identity chain reaches the later AltDetector transfer to Kamikaze.

From association to operational interference

The June attack record connects the DDoS brags, copied server, The Collective branding, Discord disruption, mass-reporting and customer-facing client failures.

Supported attribution

Purple Hats / Bypass → Feather's screenshots → The Collective → Mathew

Purple Hats / Bypass bragFeather shows screenshotsmirror: “with love - The Collective”Mathew's current server

After Feather showed messages bragging about DDoS activity against Brodie's website and game server, the displayed attack material included a mirror of Brodie's DayZ server carrying the description “with love - The Collective.” Separate captures identify The Collective as Mathew Trojanowski's current server. The same June sequence records partner-name spam, entry into Legion's Discord, disruptive content, mass-report encouragement and a customer reporting client problems.

Attribution supported by the record

The branding, timing and server identity connect the attack activity to Mathew's circle and explain the attribution made after Feather showed the brags. The current evidence does not identify which person operated Bypass or sent every attack message.

The platform publication chain

The original posts became search results, AI answers, restored reviews and platform-authored warnings. Repeated notices did not stop that distribution.

Documented distribution

Facebook source → Meta rejection → Google result and AI

Walker / Cooper postsMeta rejects reportsGoogle snippet / AI

Meta's rapid report rejections left accusations in public groups used by server owners. Google then quoted or summarised the same material in results, mismatched snippets, AI Mode and AI Overview. 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. Brodie repeatedly supplied the source posts, identity evidence, business records, notices and proof that earlier responses had not fixed the results.

Google ticket/request IDs: 0-4685000039839, 0-7685000040341, 0-9681000041045, 1-3859000040385, 1-6651000040596, 2-7896000040770, 2-9213000040525, 4-4314000040578, 4-6120000040834, 5-3327000041185, 5-8357000041583, 6-6692000040714, 6-7168000040663, 7-1475000041317, 7-4274000039113, 7-6851000041029, 8-0020000041441, 8-8385000040209 and 9-5176000040649.

Thirty exported tickets

Discord was notified, IP-banned Stockton, then lost the visible report history

The January data export preserves 30 Discord ticket IDs. Ticket 30339510, opened on 23 November 2022, reported Mason Stockton's address posting, alternate accounts and an IP-pulling server. Discord thanked Brodie, opened an investigation and encouraged more user IDs, message links, server IDs and screenshots. Discord IP-banned Stockton, but the original report was later scrubbed from Brodie's account and survived only in the data export. Later punishments were applied to the reporting account while the hostile conduct continued.

Discord tickets: 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. The June coordinated client and mass-report complaint is ticket 66248829.

Documented moderation cycle

Mathew's review identities → restorations → rating damage → Trustpilot warning

The Trustpilot record does not stop at two Mathew-linked reviews. It includes publications presented directly as Mathew Trojanowski, as Kamy, as Kyle, as Killfeed review and through the Anthony account presentation. The TeamViewer profile record identifies the Killfeed review account as Mathew. Consumer and Hooded_saw appeared around the Kamy review period, although the timing alone does not establish that Mathew operated those two accounts.

Trustpilot repeatedly removed, restored, filtered and reactivated disputed reviews after receiving account links, customer records, the full chronology and legal notices. At least 82 reinstatement or reactivation decisions were documented through 13 July. Those decisions affected the rating before Trustpilot added its own consumer warning beside the disputed reviews.

Timing evidence

Consumer, Hooded_saw and Kamy

Consumer and Hooded_saw were left around the same period as the Kamy reviews. Kamy is connected to Mathew Trojanowski. The close timing, overlapping subject and later reinstatement cycles are relevant coordination indicators.

Timing connection

Similarity and proximity support coordinated publication timing. No account record currently identifies Mathew as the operator of Consumer or Hooded_saw.

Customer, competitor and non-customer context

The publications came from competitors, former collaborators, former customers and people who had never subscribed. Those relationships change the claimed independence of the complaints.

PersonDocumented relationshipWhy it changes the readingEvidence
Daniel SantosCustomer who also offered paid DayZ modding services.His complaint came from a customer interaction, but not from a person commercially detached from the DayZ service market.Facebook thread
Brett JonesCustomer; initially cancelled over disabled DM permissions, later returned, then joined the pile-on. Another customer reported his Xbox-party comments.The later publication belongs to a longer permission and support history, not a first-time independent discovery.Jones complaint record
Adam CooperNever a customer; appeared in Joel Walker's group and publication context.His post cannot be treated as a review of a service he bought or used.Subscription and post context
Ray SmithCustomer told within 19 minutes that the shop feature did not work; repeatedly offered payment for unadvertised, normally free work; removed Legion himself.His review later reversed the access chronology and described the automated support-bot line as Brodie's personal message.Discord chronology · Review
Mason StocktonWhitelist.gg operator, DayZ++ partner and former DayZBoosterZ collaborator; used Pups to approach Legion supporters.The Havasu review promoted alternatives while Stockton operated a competing service, and the Pups outreach continued that customer-steering relationship.Partner and Whitelist.gg record
Joel WalkerOperator of Make DayZ Great Again Killfeed.Posts attacking Legion and recommending or promoting other bots are competitor publications, not neutral community moderation.Reset-loop publication · Competitor promotion context

Damage and causation

Sworn customer cancellation statement

A customer directly connected the public drama to cancellation

A customer's sworn written statement records that the Facebook and Trustpilot rumours made him uncomfortable and that the volume of public drama caused him to cancel Legion and use another bot. After reviewing the full evidence, he concluded that Legion and Brodie were not at fault and returned as a customer. The later recovery of that customer does not erase the original cancellation; it proves both the commercial effect of the campaign and the work required to reverse it.