One campaign, connected across people and platforms

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

Mathew Trojanowski used Kamikaze / Kami / Kamy, Skynet, Brief_Ordinary1438, Kyle, “Killfeed review” and Anthony across the campaign. The TeamViewer review on the “Killfeed review” profile received an official reply addressed to Mathew. Brief_Ordinary1438 published the same Anon PVP promotional copy preserved under Trojanowski's name. The July Anthony, “Killfeed review” and Kyle notices repeated the same complaint language in the same release sequence.

Those presentations were not independent customers. They were linked accounts and identities used to repeat the same accusations, inflate their apparent support and create multiple adverse review and notification records against Legion.

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

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.

The DayZBoosterZ collaboration cluster

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.

Joel Walker: group administrator, competing killfeed operator and reviewer

Walker used the Facebook group he administered to attack Legion while promoting Make DayZ Great Again Killfeed, his competing product. In April 2026 he published a one-star Trustpilot review against Legion and used his group to post or bump one-star reviews against Legion, DayZ++, DayZ Multi Tool and Jinie's bot. Trustpilot later confirmed that Walker's review had gone offline through either Walker's deletion or removal in another investigation. The attack was published from a direct competitor using his own group to damage rival services.

Facebook source → Meta rejection → Google result and 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.

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

The January data export preserves 30 Discord ticket IDs; the later complaint 66248829 raises the documented total to 31. 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.

Mathew-linked review presentations → restorations → rating damage → Trustpilot warning

Mathew Trojanowski used Kamy, Kyle, Killfeed review and Anthony alongside publications under his own name. The TeamViewer reply on the “Killfeed review” profile addresses the reviewer as Mathew, while the July Anthony, “Killfeed review” and Kyle notices repeat closely matched wording in the same release sequence. Consumer and Hooded_saw were published in the same timing and subject cluster, but remain separate unidentified accounts.

Trustpilot repeatedly removed, restored, filtered and reactivated false reviews after receiving the account links, customer records, full chronology and legal notices. The preserved record contains 608 report/email records, 168 case/thread references, 87 keep-online or reinstatement decisions and 1,038 cumulative publication days through the conservative directly-confirmed publication periods. On 1 August, case 01757662 removed a Joel Walker DayZ Multi Tool review after a defamation flag. Trustpilot had already refused complete profile removal and kept Mathew's “Killfeed review” online again in case 03085556 and published its own warning against Legion.

The account trail: repeated Mathew-linked presentations were displayed as independent reviewers. Trustpilot repeatedly restored the false publications after notice, then became the author of additional adverse material through its own consumer warning.

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.

A customer directly connected the public drama to cancellation

A customer's 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. The cancellation directly records the commercial effect of the campaign, while the later return records the additional unpaid work required to reverse it.