Before SkyNet and before Legion, I was already well established in console DayZ.[CID: 1] Aggro PVP grew to six servers at its peak, with several of them sitting high on the Jeabers global leaderboards. By October 2022 Aggro NWAF was #1 globally with more than a million kills and Aggro Kamy was #7. I was building servers, fixing XML, working with Nitrado, writing Discord automation and running DayZ Multi Tool, and I had already spent years being the person other server owners were sent to when they needed help getting something working. A lot of the older disputes now get folded into the same story as if I spent my time hunting for arguments. I did not. I usually got involved because somebody asked me for help, showed me something that was happening to them, or because work I had built was pulled into it. I already had successful servers, tools people used and a reputation in the community long before SkyNet existed.
Some of this is sourced from the old Discord where I was coding SkyNet as I vigorously tested absolutely everything before treating it as ready for production. When his malicious behaviour started being aimed at me after the split, I went back and gathered some of the 2022-2023 evidence, which is still there today. After a few months working with him, I observed his technical skills were severely lacking compared with the image he liked to project, so I treated a lot of his toxicity as harmless all-bark-no-bite bravado. I had not personally seen him successfully do anything malicious, so I stupidly ignored the petty squabbling as background noise that I did not have time for. Only after the split and the malicious shit that followed did I actually see the horrible behaviour for what it was.
One of the first big examples was DayZKillfeed.com. [CID: 2] [CID: 3] Jeabers had already warned its own users about Ronald "Jarvis" Lund contacting server owners in a way that made people think he controlled or represented access to Jeabers when he did not, and Edin Law, who ran Laws Killfeed, had his own history with Jarvis. By the time I became directly involved, other developers were already dealing with copied work and I was stepping into an existing problem rather than inventing a rivalry. Jarvis then made the copying unusually easy to document. DayZKillfeed.com publicly announced that it had "re-created Laws Killfeed and Jeabers Killfeed from old SRC codes" and was implementing Trader Bot and Multi Tool functionality. In a preserved conversation about what to work on next, Jarvis said that if he did not want to "crush those guys so bad" he would not be coding it. In another exchange with me, after DayZ Multi Tool had been dragged into it, he told me: "Don't forgot Nitrado and Multitool. Make sure you add those because they will be free as well."
I responded by creating officialdayzkillfeed.com, an information site where I put the screenshots and material in front of the community. [CID: 4] [CID: 5] I told Jarvis directly that I owned and ran it, and in the same exchange told him that more than 80 server communities had seen it after I released it publicly. His response included telling me I could make "100 websites" and would never hurt them. The argument escalated from there, and Carl-bot caught threats from one of Jarvis' accounts, including "Play games you get burnt" and "We coming for you boy," and automatically banned it from my Discord.
Then I did something stupid myself. After those threats I ordered a pile of takeaway to Jarvis' house on cash on delivery. [CID: 6] One pizza order was roughly $400, with about $300 worth of toppings stacked onto two pizzas, and I posted a screenshot because I was laughing at how ridiculous the order looked. His address was visible in the screenshot. I was not trying to publish his private information and, at the time, I did not even know what people meant by "doxxing," but I exposed it anyway. My original Discord account was later banned over that, in late 2021 or early 2022.
That old account being gone is also part of how so much early evidence survived in a scattered way. [CID: 7] I had taken screenshots while things were happening and sent many of them into separate staff channels so my volunteer admins could see what I was dealing with. Other screenshots were taken later by going back through Discords where the full conversations still existed. Losing my own account did not erase messages sitting in other communities, and screenshots that had already been copied elsewhere survived even when somebody later deleted or unsent the original message.
Jeabers was different because I actually liked the service and had supported it for years.[CID: 8] By April 2022 I had three Aggro servers in the Top 15 for kills, my players were competing seriously for global positions, and I had been paying for Jeabers for close to three years. I was not complaining because Aggro could not compete. We were already winning. Then I was shown the leaderboard cheating itself. EnemyVic's statistics included obviously impossible results, including 1,000 metre kills with weapons such as a BK-133 shotgun. I already understood how the data path worked and how manipulated Nitrado log data could be fed through the API before Jeabers pulled it into the global statistics. Other people could see the impossible numbers and people around Blackout knew what was happening, but I was the one who kept pushing Jeaber to actually rectify it instead of letting the leaderboard continue as if those positions were legitimate.
Jeaber's first response was "i dont care." [CID: 9] He told people they should only care about the statistics on servers they personally managed, which was a ridiculous position from the person operating the global leaderboard everybody had been encouraged to compete on. Players had spent months grinding those positions. Some of my own players had built a huge part of their DayZ experience around where they sat globally. At the time I was still on a grandfathered subscription of about $5 USD a month for unlimited servers and slots. That plan was gone from sale and I knew that if I cancelled it I could never simply buy it back, but after Jeaber refused to deal properly with the cheating I cancelled anyway and opened a PayPal dispute. His reply through PayPal was:
"Hello this is jeaber paypal customer service center dispute and resolution team for individuals with tiny wieners and fragile egos. [CID: 10] How may we assist you today?"
Once the issue was forced, EnemyVic was blacklisted and the wider Blackout manipulation became impossible to leave alone. [CID: 11] LordeJadus later acknowledged that Vic had put himself at the top and Shadow then put himself at number one, and Blackout's access had to be frozen. Legitimate player history was caught in that cleanup too. One of my own players argued directly with Jeaber because he had genuinely grinded his rank and lost it through no fault of his own. A significant number of the players who had been sitting in the global Top 10 quit DayZ over the leaderboard mess. They had spent months chasing something that suddenly looked pointless. When Jeabers disappeared in early 2023, a lot of the players who still remained in the Top 50 also stopped playing and never returned. I eventually resubscribed after the original dispute was resolved, but the grandfathered deal was gone. I went from roughly $5 USD for unlimited servers and slots to around $27 USD for only about 150 to 200 slots. During the dispute Jeaber had even joked about charging affected players $10 to get their statistics back.
Mathew did not enter my life with SkyNet.[CID: 12] [CID: 13] Before we became close, other people had already shown me problems around him. In April 2022 Feather showed me conversations from her own dispute where Mathew and Azzy were calling her a pedophile, and she believed her server was being attacked. I saw what she showed me and I did not treat her like she was making it up, but at that stage it was still somebody else's conflict and Mathew had never personally done anything wrong to me. The late-August messages between Mathew and MWFJunkie are dated 2022, but I did not see them in 2022. I only saw those old screenshots after the Reddit allegations appeared and Tbag and others started giving me material they had retained. Those screenshots show Mathew talking about already having files for new Nitrado servers, referring to an old exploit a major company had supposedly missed, and making the point that although he had not done anything, he could. They belong in the 2022 chronology because that is when Mathew sent them, but they were not part of what I knew when I chose to keep working with him.
On 9 September StockyAcrobat from Skulls'N'Roses contacted me directly because fake Discord profiles were being made to look like members of their staff and then used to spam the Skulls'N'Roses invite into other communities. [CID: 14] It made the real server look like it was aggressively stealing members. Stocky showed me the real and fake profiles and warned me about Mathew. I had recently stopped drinking after years of being drunk every day, and for the first time in a long time I was trying to make this kind of judgment with a sober head. DayZ was full of people who hated each other, screenshots without context and old feuds that became everybody else's business. As far as I knew, Mathew had never actually done anything wrong to me, so I made the decision to judge him by how he treated me and gave him a second chance. I did not forget the warnings. I decided they were not enough, by themselves, for me to condemn somebody I had not personally had a problem with.
When I went back to MWFJunkie in January 2026, years after all of this had unfolded, he gave me additional detail about the older FTP dispute involving Azzy. [CID: 15] He said the file corruption stopped after Azzy's FTP credentials were changed, described files being handed over to ALL CAR after a rework and also told me about Mathew sending flowers to Azzy's workplace after their split. I did not have that fuller account in 2022. At the time I was making the decision with what I knew then.
By October 2022 Aggro had become a monster to keep running.[CID: 16] I had as many as six servers, I was working two jobs, and I was still doing XML, DayZ Multi Tool, support, Discord work and whatever else broke. The 1.19 update finally flattened me. On 18 October I had already done a 12-hour work shift and was staring at another enormous server rebuild, including damage configuration across 1,555 items. In the early hours of 19 October I told everyone Aggro was finished and said, plainly, "I finally broke." Mathew had recently added runtime before I even knew his real name. The donation came through Nitrado under matttroj, and it was only after I publicly thanked the "anonymous" donor that he messaged claiming it was him. That is how he started worming his way in, so when I finally burnt out he offered to take the day-to-day ownership pressure off me. I accepted it because I was exhausted, not because he had suddenly become the technical origin of Aggro. The conversations from the same period still have him coming to me for coding, XML, bot and other technical help. Taking some of the server-running burden away gave me room to stop grinding on Aggro every waking hour.
Links arrived almost immediately after that. [CID: 17] In November he was discovered jumping roughly 20,000 positions on Jeabers in a matter of hours and boosting himself into around the top 2,000. I had no idea who he was. Kamikaze told me he was connected to DayZKillfeed.com as a staff member. I banned him and people around him from Aggro. What I did not know at the time, and only discovered much later, was that on 3 November 2022 Links had privately asked Mathew for an invite to my Discord and Mathew gave it to him. I cannot now remember exactly when or how I recovered that old conversation, but the preserved DM is legitimate. At the time I was dealing with Links over the leaderboard manipulation and his links to people who had been hostile toward me without knowing Mathew had privately opened the door for him.
What followed went well beyond the original cheating issue. [CID: 18] Links kept contacting me after being told to stop, moved through alternate accounts, evaded blocks and server bans, used racist account names aimed at me and circulated what he believed was my home address. By 23 November I had sent Discord Trust and Safety 93 direct-message links and 118 screenshots. Discord eventually disabled his account and accounts associated with his IP for the repeated block and ban evasion and unwanted contact. At that point Discord actually looked at the pattern instead of treating every message as a separate little incident.
When I asked about reverse-looking up an email address, it was only to get Mason's name to provide to the authorities after he left a comment on the WordPress site I had made and WordPress exposed his email address to me. Mathew suggested an IP-grabbing link and I changed the topic to a Nitrado ticket. During the Links mess he was also talking about getting behind Cloudflare to identify a website's origin IP. [CID: 21]
By late November and December I was also seeing more of Mathew's technical behaviour directly. He scraped code from Vic's GitHub because he wanted functionality he could not write himself. [CID: 19] [CID: 20] His real job involved preparing aircraft-refuelling schedules at Los Angeles International Airport for Swissport, and he tried to outsource that work through Fiverr. When the Fiverr worker reported him for trying to move the conversation off Fiverr and onto Discord, Mathew responded by trying to use ChatGPT through his own Discord bot, Bot Ross, to automate negative Fiverr reviews against him. The prompt described a program that would generate negative reviews from the worker's username, service type and rating. This was not a vague conversation about reviews. I watched him try to build retaliation against a worker who had reported him.
On Christmas Day 2022, when JayJay asked how I was getting on with Kami, I told him he had not done anything wrong by me because, at the time, I was foolishly believing he had good intentions.
My killfeed development did not begin with SkyNet.[CID: 22] The first code went back to 25 October 2020, when I had called the idea "The Soul" because I wanted it to become the soul of a DayZ Discord. Aggro always came first, so the project spent long stretches sitting behind the server work while I built other tools and kept the communities running. After the October burnout and the Links mess I finally had room to dig that old code back out. Coding also became somewhere useful to put the time and concentration I was no longer putting into drinking. I could disappear into a problem for hours, chase a bug until morning and realise I had spent the whole night thinking about code instead of alcohol.
Then Jeabers disappeared. [CID: 23] The killfeed service was gone, but its support Discord was still sitting there with more than 5,000 members, mainly DayZ server owners who had joined because they used or needed a killfeed. Jeaber was in prison and there was no active owner properly running or moderating the community, but the audience remained. Thousands of server owners were suddenly looking for something to replace the service they had been using.
I started the bot, put the team together and created the Discord.[CID: 24] Mathew was involved because by then I trusted him through Aggro. Cody was brought in because there was one major piece neither Mathew nor I knew how to do yet: the database. I thought we needed him for that, but I ended up working the database out myself before Cody even got around to attempting one. From 12 February to 23 June 2023, excluding merge commits and bot accounts, my Git account recorded 457 commits, 53,813 additions and 33,785 deletions. Mathew recorded 97 commits, 12,148 additions and 5,425 deletions, and Cody recorded 36 commits, 15,966 additions and 14,057 deletions. We were still talking about a three-way partnership and equal ownership while those were the numbers being produced by the live beta.
Mathew's account held ownership of the SkyNet Discord while we were testing Discord's built-in subscription system because Australians were not eligible to use that feature at the time. [CID: 25] Cody and I were both Australian, so Mathew's account was the practical one to use while subscriptions were being tested. We had not formalised a company or agreed that the owner badge on a Discord server gave Mathew ownership of the bot, the code or the business. When partnership paperwork entered the discussion, Australia was the obvious jurisdiction because two of the three proposed partners were Australian. Cody then became difficult to reach, while Mathew said talking about money felt "icky."
The strain had been building throughout the live beta. SkyNet had bugs because it was being actively developed, support tickets were coming in, and I was handling almost all of the coding and fixes while still working two jobs. The final straw came when I woke up and found tickets sitting ignored. [CID: 26] In Staff Chat, Cody then asked Mathew about the Call Of Duty stats bot Mathew was making, with the way Cody referred to it indicating he had seen it through the shared ChatGPT account. I was waking up to unresolved bugs and ignored customers in our live DayZ beta while the other proposed owners were discussing another bot Mathew had started.
I spent several days trying to get Mathew to sit down and discuss the workload, the ignored support and how equal ownership was supposed to work. On 23 June I was still waiting for him to call. [CID: 27] Before making a final decision, I asked a leading developer in the same niche to assess the contribution history. He ran a competing killfeed and had more than 13 years of development experience. His review put me at roughly five times Mathew's workload, around 70.9 percent of the commits being examined and roughly 35,000 more additions and deletions.
When I put the issue to the group the next day, it was not a sudden argument about wanting more money. It followed months of carrying a live beta, working two jobs, fixing the bugs, answering support, waking to ignored tickets, trying for several days to speak with Mathew and then having the workload independently assessed. Mathew said he did not care if he ever made money from it and that if I was in it for the money, he was out. [CID: 28] He made the choice to leave the proposed partnership. I told him I could not keep building a commercial service every day for free and would register as a sole trader and continue my work myself. I only secured my source code and databases after he said he was out.
The public version of the split was distorted almost immediately.[CID: 29] Mathew presented me as unstable and abusive, as though I had randomly started a fight and deleted the bot to be spiteful. I then left both public Discord spaces where the people who knew me were used to contacting me: Aggro and the SkyNet beta server. Mathew retained the beta Discord. To the people who remained there, I looked like the guilty one because I had disappeared while he was still standing in the original project server. Anyone who had actually used SkyNet between February and June knew who was constantly developing and supporting it, but the people arriving after the split saw Mathew holding the Discord and me absent from both of my usual public spaces.
Immediately after I left Aggro, my announcement was deleted. Jacob Stoppard was in voice chat at the time and told me he heard Mathew and Cody discussing the backup they had of my code. [CID: 30] I returned and took control of Aggro again because I was not going to leave my servers, community and infrastructure sitting there while they were discussing a retained copy of my source.
I also saw what was happening through Mathew's ChatGPT account. During development
he had insisted I use his account for bot work because he had alpha access, so I had legitimate access to
that history. After the split I could see my files being run through the same account, including
killfeed-embeds.py, heatmap.py, database_config.py and
bot.py. [CID: 31] My
check_logfile function was supplied with instructions to turn it into a FastAPI/database
component and an Aggro logfile was uploaded with the code. Less than 24 hours after the split Mathew
announced that SkyNet was back and said the code had been completely rewritten, then said it was JavaScript.
Two days after the separation the running bot was still producing Python/nextcord errors with the same
command structure. Meanwhile the social story was not about the several days I had spent trying to discuss
workload, the independent review or Mathew explicitly saying he was out. It became the easier story that
Soul had another abusive meltdown and spitefully deleted something Mathew owned.
That is when the Git history, messages, workload assessment, partnership discussion, ChatGPT history, file uploads and backup discussion stopped being ordinary development records and became the only way I could show the sequence that had actually happened. [CID: 32]
At first the retaliation still looked connected to the bot and the servers.[CID: 33] [CID: 34] Mathew contacted people around my
services and customers and pushed his account of the breakup. Then, on 15 July, I found that my Nitrado
account had been accessed at 4:26 in the morning and Aggro's in-game messaging had been changed from my
community link to discord.gg/bigfatmods, Edward Griggs' community. I was suddenly dealing with
access, messages and links inside infrastructure I had been responsible for while players were being sent
somewhere else. An Aggro clone appeared as well, with SkyNet inside it, which made the branding mess worse.
I was trying to secure access and keep my actual servers recognisable while a competing Aggro identity
existed beside them. A player seeing an invite or server message did not know who had changed it or why.
They just saw two versions of the same community and an owner who looked like he had lost control of his own
links.
Later, during the period when the technical attacks and harassment were escalating, Jacob Stoppard, known as RB SKIZZA, was one of my staff and we had a brief disagreement. I removed his staff roles. Within about ten minutes Kamikaze contacted him and tried to recruit him for information about me. Jacob talked shit about me, which I expected after the disagreement and did not care about, but he then let me know what Mathew was doing and recorded the conversation so I could see it for myself. In that conversation Jacob said, "GG on the DDOS," and Mathew replied, "Soul was easy as fuck." [CID: 35] Mathew went on to brag about having his infrastructure spread across six servers, meaning machines he could use remotely rather than six DayZ communities, and talked about leaving accounts in place so he could feed me false information.
The attacks then moved further into my personal identity. [CID: 36] On 20 September AggroPVP.com published what it represented as my residential address and invited people to head there "for some fun." That was my home, where my partner and children lived. Porkbun suspended the domain in its system, then days later told me it had transferred to GoDaddy, which meant I had to begin the reporting process again with another company.
On 10 October, DayZ++ staff came to me directly. hoks, also known as Jon, told me
he ran DayZ Modding Bot and was an admin in DayZ++. He said Jarvis was "on copy strike again," linked me
back to a 2021 "jarvis moment" video and said he had seen parts of my bot again, including both Multi Tool
and Legion or similar feed ideas. [CID: 37] He gave me guild ID
1156290166911156324 and four Discord user IDs: 290048318707466250,
439466792855797760, 926252048847085628, 1131535608653807667. He told
me, "Do what you wish with this info. If you wish to ban them," and described the list as King BHD,
Saftladen, Jarvis and "some other acc." I had not independently confirmed that every account on that list
was associated with Jarvis. I asked which bot he meant and asked for the guild ID instead of pre-emptively
banning a list of accounts I had just been handed. Hoks said they had been locked out within about two
minutes and had not managed to make a new video that time.
October kept mixing the technical attacks with public humiliation and the pedophile accusation. [CID: 38] When Mathew was challenged over the DDoS material, he answered by calling me a "Pedo!"
By November impersonation was being used against me too. [CID: 39] [CID: 40] [CID: 41] An account using Legion branding spammed unrelated Discords, and another profile styled as "Soul.dev" appeared using my identity in a degrading way. Then in December somebody joined and unloaded roughly 100 abusive messages before being banned. It included homophobic abuse, repeated images of me while I was sick, sexual violence threats involving my partner and threats involving my children. The dispute had moved a long way from three people arguing about a Discord bot.
On 8 January I received a message telling me that people were coming for me in real life and that I should like the idea of having extra holes in my head.[CID: 42] [CID: 43] That came only months after my home address had been published. The next day Edward contacted Feather privately, insulted her, threatened to expose personal information about her and then started sending photographs of my young children. Those photographs were private. I had been strict about not putting images of my children into public DayZ spaces, and Edward could only have obtained those particular photographs through Mathew. Mathew therefore had to have saved them before our June 2023 split and later passed them on. Edward used one of the photos while taunting that my children were "scared for their lives," while the same wider group was publicly calling me a pedophile.
Edward later unsent messages, but Feather had already taken screenshots and sent them back into the conversation. [CID: 44] The live messages could disappear; the copies did not. That is exactly how a lot of this history survived. People around me were taking screenshots while it was happening and putting them somewhere else before the sender could rewrite the conversation later. On 31 January the threats became even more graphic. Xanax made sexual threats involving my partner, my children and even our pets, including a threat about raping my partner. People in the channel immediately told him how fucked it was and I banned him. He later apologised because he wanted access to a server that had banned him over the abuse, then admitted the apology was not genuine and he only wanted to get unbanned.
At almost the same time, Reddit was building a completely different picture of me.
Around 22 to 24 January a thread titled "Legion Kill feed, What's souls issue?" appeared in
r/DayZDiscussions under Obviously_Mario. [CID: 45] The post presented the user as
a new server owner who had just tried to set up Legion, made an innocent mistake with a token and then been
abused by me for no reason. The Discord-side activity was very different. The account was
im_obviously_mario, ID 443911027764232212, running a newly created guild called Apocalypse
Nightmare PvE with basically nobody in it apart from the setup. The user claimed not to know how to
configure the bot but supplied BahBahBlackSheep as the Nitrado token and claimed it had worked
the day before. Legion's logs show the same ID adding a token, running setup, deleting the channels,
removing Legion, adding it back and tearing the setup down again. The same Discord ID also existed in old
Aggro bot history going back to October 2022.
I treated it like a troll because that is what the activity looked like to me: a
nearly empty new guild, a nursery rhyme where an API token should have been and repeated setup and teardown.
[CID: 46] Reddit got the version where
the reaction was stripped away from that setup and I looked like a developer abusing an innocent new user.
The thread then became somewhere other accounts could stack more allegations.
Brief_Ordinary1438 appeared making claims that Legion had malicious intent, changed server
settings, removed files and destroyed servers. That account already had old Reddit history advertising Anon
PVP. More importantly, the Anon PVP Reddit advertisement was word-for-word the same promotional copy Mathew
had posted under his own name on Facebook for Anon PVP. The account that had published Mathew's exact server
advertisement was now in a hostile Legion thread making serious technical accusations about my bot.
On 31 January the threats against my family became explicitly sexual. In a public Discord exchange, Xanax wrote that my wife had enjoyed him raping her. Other people in the channel immediately called it messed up and fucked up, and I banned him. [CID: 47] The wider evidence from that incident records sexual-violence threats aimed at my family. Months later he tried to get unbanned, which is why the later unban attempt cannot be read as an ordinary moderation dispute.
In March, Papa Blunt's support dispute was added to the same Reddit history. [CID: 48] He had opened a ticket because he was trying to move Legion between Discord servers and I asked him for a screenshot of the error. At the same time a library change had broken several commands across the free beta, which I publicly acknowledged on 5 March while I worked on it. I pinged Papa Blunt to the announcement, fixed the command issue that afternoon and explained what had broken. He later closed his ticket saying he had figured it out, and I reopened it because I had repeatedly been asking for the information I needed while debugging the problem. I was blunt and told him I could not help somebody who would not help me diagnose it. That exchange later became another isolated example of "Soul's support" without the bug, the announcements or the unanswered request for the screenshot.
By April I was digging further into Brief_Ordinary1438 because the
Anon PVP link was not a vague similarity. [CID: 49] The same promotional wording
existed under Mathew's Facebook identity and the Reddit account. By May Jarvis had also joined the Reddit
discussion. The original Obviously_Mario thread was no longer one person's complaint; it was becoming a
long-running place where people from older disputes could add another accusation under a title designed to
make strangers ask what was wrong with me before they knew any of the history.
In late May another review problem crossed directly out of Discord.[CID: 50] A user known as Kyle or cactus said in my Discord that he had left reviews on "trustpilot" and "all the discord bot websites" even though, in the exchange, I pointed out that he was reviewing a bot he had never used. I was already dealing with the difficulty of convincing a review platform that a hostile post was not an ordinary customer experience when the person was openly talking in Discord about leaving reviews around bot sites.
By June a huge amount of the direct abuse had settled into the old Jeabers support Discord, which still had more than 5,000 members, mainly DayZ server owners. [CID: 51] Jeaber was in prison, the killfeed was gone and there was no active owner properly moderating the community, but the audience had not disappeared. Thousands of server owners who had originally joined because they needed a killfeed were still there, many of them now needing a replacement. The attacks on me and Legion were therefore happening in front of the same niche community I worked in, not in a private argument between a few people. On 5 June I filed an Adult Cyber Abuse complaint with the Australian eSafety Commissioner under reference ACA-2024-0528878, covering the doxxing, child targeting, suicide encouragement and false criminal accusations. [CID: 52] eSafety replied on 7 June saying a lot of the background might be treated as defamation or reputational harm outside its powers, but it also acknowledged the rape and death threats as serious material and asked me for live links, screenshots, dates and times. I supplied them. On 10 June I wrote back explaining that this was already close to a year of harassment involving my fiancee and children, my address, private photographs of my children, cloned communities, access to my Nitrado account, suicide encouragement and threats to rape my family. On 12 June, while the abuse was happening again, I sent eSafety the live Discord message link and a recording of the exchange so they were not being asked to rely on my description of it. [CID: 53] The public abuse continued anyway. One exchange attacked whether I could keep my wife and children happy, and when I asked how the fuck they knew anything about my fiancee or kids, the reply turned ominous before I was told:
"You really should just do your kids a favor and just kill yourself, their lives would be better." [CID: 54]
My partner was called a slut in the same run of messages. [CID: 55] This was only months after Edward had been using private photographs of those same children. On 18 June another capture shows 72 notifications while Mathew repeatedly tagged me and my supposed home address was dragged back into the public argument. Edward then told me to go live on Facebook and hang myself. I counted 19 separate child-related references or images in the material around that period. They were not simply making me miserable as a side effect of an argument. They were directly telling me to kill myself, telling me my children would be better off if I did, and bringing those children into the abuse while adults in the same circle already had their private photographs.
I became desperate enough to contact Mathew's family. [CID: 57] I had created
SkyNetKillfeed@hotmail.com before the split, but the only thing I had ever actually used that
address for was contacting his family. I contacted his sister and asked for somebody close to him to
intervene, and the correspondence that followed presented itself as coming from his mother. While I was
using that inbox for those private messages, an email arrived from LegionKillfeed@hotmail.com
saying, "Hello soul, Did you miss me yet? Signed, Legion Killfeed." [CID: 58]
After months of being called a pedophile while Mathew had saved private photos of my children and Edward had used them, I found public registry information that appeared to place Mathew at the same address as a registered sex offender and I reacted publicly to it. [CID: 59] The screenshots of my reaction were then circulated without the months before it: the pedophile smear, my home address, the child photographs, the death threat, the sexual threats against my family, the public Jeabers abuse and the messages telling me my children would be better off if I killed myself.
The next day the record shows that this was not cooling down. On 25 June Mathew was challenged by somebody telling him to move on. He answered that he had given me a year, was fed up and that I could now "enjoy his own medicine." Edward separately sent a message saying to "continue to chase the pedophile." The same evidence set also records Mathew telling Jacob Stoppard "Snitches get stiches" and Edward telling Jacob, by name, "You're Next!" [CID: 60] By that stage the false pedophile label was not just an insult appearing in an argument. It was being used as an instruction to keep pursuing me, while somebody who had brought evidence back to me was being threatened too.
The story did not jump from June 2024 to a Facebook argument a year later. The same
people, sites, reviews and accusations kept moving through the community. On 15 July SecurityTrails showed
IP 15.204.227.181 hosting a cluster of domains already connected to the dispute, and the 17
July records placed dayzskynet.com and skynetvslegion.com in the same hosting trail. [CID: 61] I treated that as infrastructure
evidence tying already-known sites together, not as proof that one IP address identified the human behind
every account. On 21 July a Legion supporter went into the SkyNet Discord and challenged Mathew with the
screenshots and hosting information. Mason Stockton, the same Links/Havasu figure tied to the older Links
history, defended Mathew and immediately accused the supporter of being me on an alt. Mathew joined in with
"Wtf. Soul?" and then told me my project was dead and to focus on it. The supporter later messaged me after
the general chat was cleared. Anybody who challenged Mathew's version could be recast as one of my alternate
accounts before anyone had to answer what the supporter had shown.
Then DayZ++ staff entered the blacklist mess directly. On 7 August, Queen, who was DayZ++ staff, posted in The Blacklist telling people to "avoid these two whenever possible" and described the dispute as "personal beef," saying the original context no longer mattered. [CID: 62] When I finally spoke to her properly on 9 August, the conversation ran for nearly two hours. I went back through why I had reacted, the history with Jarvis and DayZKillfeed.com, Jeabers, Links, SkyNet, the DDoS material, the pictures of my children and why seeing somebody hoks had previously told me to ban using DayZ++ on the same day I found out Queen was staff had set alarm bells off. Queen told me the post had since been edited to remove the businesses and said putting the businesses in it had been a bad call. She said she could see the Kami and Crix bullshit, could not believe what they were saying, and proposed removing both posts. Her proposed middle ground was that anything new from Kami or Crix would be posted, anything genuinely toxic from me outside the SkyNet dispute could be posted, and I had a right to defend myself against those two. She also told me she had removed SkyNet's token, kicked the bot and terminated the partnership. I agreed, removed the DayZ++ material from my old coding Discord and told her I would update the website when I got home. Earlier in that same conversation I had already said that anything posted about me meant I would have to keep explaining the drama over and over until eSafety got it removed. That is the part people outside it do not see. By the time somebody new asks why I am still talking about the same people, I may already have spent hours walking another person through years of context just to stop a stripped-down version becoming the accepted one. From the outside that repetition can look like obsession. From my side it is the same accusation or version of events resurfacing somewhere new and me having to explain it again. The DayZ++ material from the same period also showed hoks with an Administration role and Links/Linksypoo with a Partner role while advertising whitelist.gg.
On 24 August Edward did to another killfeed operator what I had already watched
happen with my family. [CID: 63] [CID: 64] During an argument with T-Bag,
the account aCrix-Legion is Trash posted material from T-Bag's Facebook showing his children
and wrote that "somebody should have kept their mouth shut." I was not the only developer whose family
images were being dragged into a DayZ argument. Around the same time Trustpilot was becoming a constant
fight. Reviews appeared under identities I could not match to customers, and the platform's own decisions
moved back and forth as I reported them. Mason, using the Havasu identity, posted a one-star review
attacking Legion's security, claiming the Nitrado token created huge vulnerabilities, calling me a "chatgpt
coder" and explicitly recommending competing services such as DayZ++, Laws and Hulks. The evidence I later
connected to Mason also tied him to the old Links identity and to whitelist.gg, a competing service. By 31
August I was dealing with a hostile review from somebody who was not just a random dissatisfied Legion user
but was connected to a competing product.
On 27 August SkyNetVSLegion.com was showing prominently for Legion-related searches, and in September a GitHub profile using the Legion name appeared with a repository describing itself as "The code for Legion killfeed remade for free." [CID: 65] [CID: 66] At the same time the Havasu review reappeared and the Trustpilot reporting process kept producing new decisions instead of a clean end to the dispute. I was trying to protect the name in search, answer reviews, document who was behind them and continue building the actual service. The review fight carried through the rest of 2024. Karl Messer, also known as Moley, became another repeated Trustpilot issue. A review under his name attacked the bot and me personally, and by 10 December I was dealing with it being reinstated for the second time. Trustpilot correspondence continued into the following days. This was not a quiet period between two bursts of drama. It was months of reporting, removals, reinstatements and arguments over whether reviewers had any genuine experience with Legion at all.
At the end of August the code issue was corroborated from another direction. Sean Moser, using OzzieHousos, had still been talking to me normally on 31 August. On 1 September he told me Mathew had previously given him access to a private GitHub repository and that "a lot of it is DZMT stuff." [CID: 67] That was somebody who had been close enough to Mathew to be given repository access telling me he had seen DayZ Multi Tool material inside it. He then deleted parts of the conversation, left my Discord and reappeared through an alternate account. By 13 September the same alternate account had been renamed to call me a pedophile using my real name, and Buchanan had also posted a negative Trustpilot review while operating a competing DayZ service. [CID: 68] The same person who first handed me corroborating information about the repository later became another source of the same public smear.
In September Mason Stockton, the same Links/Havasu identity I had been dealing with
since 2022, was still getting into my space through alternate identities including Pups, using the Discord
handle sasha1371731. He was publicly acting friendly and inserting himself into conversations
with me while privately messaging Legion subscribers and supporters to steer them away from Legion and
toward DayZ++. [CID: 69] On 18 September
the Pups account was also prodding at my address and tax information inside support, framed like he was
merely warning me about what people could find. By 21 September I had the screenshot showing the same
account privately approaching my subscribers about switching to DayZ++.
That continued into 2025. [CID: 70] [CID: 71] [CID: 72] In February a former BigFatMods staff member, FaMiN_aKuTaMaY, supplied screenshots intended to establish that the Crix identity I had been dealing with was Edward Griggs and described his own long-running conflict with Edward, including a death threat. I asked for evidence that could actually be given to police rather than simply accepting somebody's word. March then brought more Trustpilot correspondence and the AltDetector/Whitelist.gg dispute. The important part for me was that people from older, separate disputes kept turning up with evidence describing the same identities and behaviour I had already been documenting.
The July 2025 explosion came out of that year of background pressure rather than appearing from nowhere.[CID: 73] [CID: 74] Nathan Putzier claimed he had been charged for a killfeed he had not used in over a year, while my subscription records showed a fresh subscription from May 2025. The next day the claim became a Facebook scam warning. Brett Jones then told people he was replacing Legion because he had supposedly "found out the owner of legion is a pedophile." I removed his access for making that accusation, he pursued a PayPal dispute, and PayPal decided it in Legion's favour. Afterward another person entered support acting friendly, turned abusive and relayed "Tech says hi," tying the contact back into the same dispute.
Then Daniel Santos opened a paid-support ticket about premium features. [CID: 75] I directed him to the announcements and information that already answered what he was asking, while he kept leaning on the fact that he was paying. The exchange became hostile and I told him to stop treating me like a servant, read the information and communicate with basic respect or I would cancel the service. Screenshots of the ticket were taken to Facebook without the full thread, and the public version became that I treated paying customers like shit for asking questions.
Danny Hayes then joined the pile-on. [CID: 76] [CID: 77] He identified himself as a
competitor and had never actually used Legion, but the comments moved into "EVERYONE REPORT LEGION",
"#TeamKami", Danny writing "2 can play that game" and then leaving a one-star Trustpilot review. Brett's
pedophile accusation was mixed into the same public thread. People who pushed back were attacked too:
Codi-lee Brooke Dale defended the support structure, Maddyn Mills challenged the way Santos was going after
anybody who disagreed with him, and KaLee Whitmore pointed out the double standard of abusing me and then
acting shocked when I answered angrily. The Facebook pile-on immediately spilled into Trustpilot, and it did
not arrive as one bad review followed by silence. The first burst produced accounts such as
CUNT, WARZONE and Danny Hayes in rapid succession, then Robert McDonovan appeared
with the claim that I took people's money and deleted their DayZ servers, followed by Z Doneskies with
another supposed support experience. Reviews were being removed, reinstated, edited and replaced while I was
still arguing about the ones that had appeared immediately before them. Some of the reviewers could not be
matched to customers, some were openly connected to the Facebook campaign, and some alleged things Legion
could not technically do, including deleting a customer's DayZ server. Trustpilot then warned me about
"misusing" its flagging system while I was using the reporting process against a burst of reviews that had
followed a public call to report Legion.
The child material was dragged back into the Facebook attacks as well. [CID: 78] Older discussions where I had talked about my children being targeted were turned into sexual jokes and further insinuations. Then a parent connected to my child's school saw one of the posts about me. Thankfully that person did not simply believe it, but the accusation was no longer confined to a niche Discord or an old Reddit thread. Someone around my child's real-world school community had now been exposed to strangers publicly calling his father a pedophile because of a DayZ bot dispute.
I reported the Facebook posts and comments repeatedly.[CID: 79] Meta kept returning decisions that the material did not violate its rules, and at one point suggested blocking or unfollowing people if I wanted to see less of it. Blocking a person only stops me seeing the publication. It does not remove an accusation from a large DayZ group, stop customers reading it or stop another parent around my child's school from seeing strangers call his father a pedophile. The material remained available to the audience while I was being told how to hide it from myself.
I was already taking the same material outside the platforms' own support queues. Between 4 and 7 August I filed another detailed complaint with the eSafety Commissioner, reference CYR-0672200, covering Daniel Santos' Facebook incitement, the cross-platform coordination, Danny Hayes' role in the reporting and review flood, and the commercial competitors involved. [CID: 80] I also made external reports to the Canadian Anti-Fraud Centre, reference 2025-67881, and Thames Valley Police in the UK, reference 43250388789. On 6 August I told Trustpilot I had also contacted the ACCC and the European Commission while I was preserving the platform's handling of the same review material. [CID: 81] I was not waiting until years later to decide I had a problem with the platform responses. I was escalating them while the review bomb and Facebook campaign were still active.
Trustpilot became far more than a disagreement over whether one review should stay online. [CID: 82] Reviews from the Facebook pile-on were being removed, restored and reassessed while I supplied the links, the calls to report Legion, the competitor involvement and the fact that several reviewers could not be matched to customers. The Robert McDonovan review claimed I took customers' money and deleted their servers. It appeared across three separate periods and was reinstated repeatedly even though Legion could not perform the act being alleged in the way the review described.
By 11 August I had escalated the matter to Trustpilot Legal. [CID: 83] Legal asked me to wait until 15 August and avoid taking action that might create "wasteful costs" while it considered my complaint. Within roughly two hours, Content Integrity reinstated the Robert McDonovan review after it had already been removed, saying the content followed the guidelines. Another part of Trustpilot had treated review matters as removed or resolved while another agent was putting the material back online. Trustpilot Legal had asked me to stand down, but its own moderation teams continued publishing and reinstating the disputed content as though the legal escalation did not exist.
I demanded one legal point of contact, a litigation hold and preservation of the moderation history. [CID: 84] I sent formal legal notices, deadlines and a Calderbank offer, then followed up when Trustpilot's teams kept producing conflicting decisions. Instead of Legal taking control of the dispute, messages continued being routed between Legal, Content Integrity, Privacy, support forms and other departments. Reviews could still be restored after removal, while the responses to my legal notices either avoided the substance or sent me back through the same moderation process I was challenging.
Even Trustpilot's explanation of the entity responsible for the service changed. [CID: 85] One response said there was no Australian Business Number involved and that the service was provided by the Danish parent. Days later its privacy side supplied an Australian entity and ABN. I had to preserve the emails, review URLs, ticket numbers and screenshots because Trustpilot's own account of what had been removed, reinstated, closed or resolved did not remain consistent.
September did not cool anything down. Trustpilot reinstated the WARZONE review
again on 1 September. [CID: 86] On 24
September Mathew contacted me directly on Facebook and pointed me back to AggroPVP.com with a "here you go"
style message after saying I wanted his attention. [CID: 87] On 26 and 27 September
another newly created Discord account approached me advertising server and modding services, then admitted
it was an alt account; the name being used was SANTOS, the same surname as Daniel Santos from
the July Facebook attack. [CID: 88] By
29 September AggroPVP.com was again displaying the address they claimed was my home, republishing old
statements for ridicule and putting a direct threat against my partner beside her Discord details. [CID: 89] I was still reporting reviews
while somebody was again putting my family and address into public material.
By October I was also trying to find a lawyer willing to take the wider matter on a contingency basis because I did not have the funding for an open-ended defamation retainer, especially while the campaign was already costing Legion customers. The firms I contacted were not reviewing the underlying record and then deciding the merits were weak. They were seeing Australian defamation plus contingency funding at intake and declining before anybody actually reviewed the evidence. If a lawyer sat down with the full record, I believe the merits would be obvious. I have not found an Australian defamation proceeding with an evidence set remotely this large: years of screenshots and recordings, platform records, review histories, account links, customer evidence, contemporaneous logs, legal notices, moderation reversals and the same allegations being carried across multiple publishers. The practical barrier has been getting past the funding question long enough for somebody qualified to assess the case itself. In the meantime I kept preserving the evidence, writing the notices, reporting the posts and doing the work a lawyer would otherwise have taken over. [CID: 90]
That month I was also putting the platforms on formal notice rather than relying only on ordinary report buttons. On 1 October I sent Reddit a formal cease-and-desist through ticket 14802881 identifying the r/DayZDiscussions publication, the exact accusations and the competitor links. Reddit Legal acknowledged it but pushed me back toward the public reporting form. I sent a second notice on 4 October telling Reddit that its internal workflow did not answer the legal notice. [CID: 91] On 7 October I appealed the Facebook handling to Meta's Oversight Board under case FB-FS9LDNQ3 after 18 reports from me and another 15 reports from other people had still produced no-violation outcomes. [CID: 92]
Discord then began enforcing against my responses. [CID: 93] A returning harasser contacted me again after previous blocking. I replied with a cease-contact style message referring to the wider legal dispute and reported the contact. Discord applied harassment and bullying enforcement to me. My appeal explained the block evasion, alternate accounts, suicide baiting, pedophile accusations and attacks on my family.
On 25 October Joel Walker edited an already established Facebook post and inserted the accusation that I was a pedophile. [CID: 94] [CID: 95] The edit history showed my name had been added after the post already had likes and comments, making the earlier engagement appear beneath a criminal accusation those people had not originally reacted to. The comments moved into talk about violence against pedophiles and suspicion toward people who defended me. Joel kept bumping the post while Meta continued leaving it available.
On 4 November I was having an ordinary Legion support conversation with Tomo about base-radar automation. [CID: 96] I said I had been sidetracked by the people attacking me and linked the page documenting Joel's conduct. Discord treated the message as harassment and bullying. My account was restricted from direct messages, friend requests, server access and uploads until 6 November, and the violation was set to affect my account standing until November 2027. Discord was not being shown that link in a vacuum. My later legal-escalation ticket recorded that I had already supplied the Joel Walker Facebook evidence and identifying Discord details before Discord punished the message that linked to it. [CID: 97]
The Meta phone call on 6 November showed how little of the actual complaint had been absorbed. [CID: 98] The support representative was a woman. She kept trying to troubleshoot my account and get me to share my screen even though I repeatedly told her the problem was not my screen, browser or account. The problem was a public post on Meta accusing me of being a pedophile. After I had already supplied extensive details, she asked whether my concern was that the person was impersonating me. I lost my temper and demanded a supervisor because I was being asked to walk another employee through the basic subject of a complaint I had already explained in writing while the criminal accusation remained public. The call turned into an argument about my language and tone while I was still trying to get Meta to deal with the post itself.
Then, on 10 November, another Discord user sent me a direct message ending with: [CID: 99]
"Hope they do get your family." [CID: 100]
That was the environment in which Discord was judging my replies one message at a time and Meta was trying to troubleshoot my computer instead of dealing with the publication on its own platform. [CID: 101]
Customers told me they cancelled because they saw the Facebook and Trustpilot material and did not want to be involved in the "drama." [CID: 102] A customer did not have to believe every accusation. They only had to think choosing Legion came with too much baggage and install another bot instead. They usually saw a Facebook post, a Reddit thread and a few one-star reviews, not the private photographs of my children, the doxxing, the block evasion, the years of reports or the people openly organising reports against Legion. The timing of the reviews became part of the problem because the bad-review incidents repeatedly arrived in clusters rather than as isolated complaints months apart.
One customer later put that damage in writing. Royal_Russ311 / LEoUR_ said he had been a high-tier Legion subscriber from October 2024 until August 2025 and cancelled because the rumours circulating on Facebook and Trustpilot made him uncomfortable and he did not want to be involved in the ongoing drama. After reviewing the wider record, he returned. [CID: 103] That is a direct example of the smear changing a buying decision rather than me trying to estimate reputational damage from likes or comments.
The same November evidence preserved another practical problem: Discord states that manually deleted messages are not stored and will not appear in a user's data package. [CID: 104] When a threat, child reference or accusation was sent and then deleted, the screenshot or recording taken while it was live could be the only copy left. That is why so much of this archive is screenshots rather than something I can simply ask Discord to export again.
The Consumer/Hooded_Saw incident at the end of November 2025 is one of the clearest
examples of why the review bursts looked orchestrated to me. [CID: 105] The actual paying account was
Z Company under lihou2451. Their support ticket said the killfeed and hitfeed were not working,
but the bot status I could see showed processing and messages being sent, so I asked the basic questions
needed to establish an actual fault: had there been a kill for the feed to post, were there logs showing the
failure, and could the user see the messages I was sending? Instead of answering those questions in the
ticket, lihou2451 went into public chat presenting himself as an inexperienced customer who was
low on the pecking order and just needed somebody to help him. The support problem that later appeared in
review form was being framed publicly before the diagnostic questions had even been answered.
A couple of hours later Hooded, who called himself Frank and described himself as an admin and friend of the customer, messaged me privately instead of using the ticket. [CID: 106] His own message acknowledged that they had overlooked my request for clear information and that I could not do the job without the details I had asked for, but he still put the conversation in terms of whether they would move their server funds to a competitor. I was being presented publicly as refusing support while the person who actually opened the ticket was not answering the questions required to diagnose the issue, and the third party contacting me privately admitted that was what had happened.
The Trustpilot review then appeared under Consumer, later identified
through the review flow as Hooded_saw, saying I was rude, unwilling to help and needed
"profession help." [CID: 107] I
searched Legion's subscription records for both hooded_saw and the private-relay email supplied
through Trustpilot and found no customer record. My Trustpilot invitation count also showed zero invitations
sent for the month even though Trustpilot later labelled the review as having been written in response to an
invitation from me. The paying subscriber was lihou2451; Hooded was the unverified third party
who had bypassed the ticket and contacted me privately.
The review did not sit there by itself. [CID: 108] Consumer/Hooded_Saw, Kamy and Unholy formed the same late-November cluster. Kamy was a direct competitor, yet his review described a supposed first-hand support experience and told prospective customers to look elsewhere. Trustpilot had already dealt with competitor concerns around him, but the review came back and was again processed as if it were an ordinary consumer experience. From where I was sitting, the sequence was becoming repetitive: a support incident was provoked or reframed, one review appeared, then more accounts arrived around it so the first complaint no longer looked isolated.
The Kamy history then became another argument about Trustpilot's own records. There were separate Kamy review notifications and multiple state changes in the Business interface. Trustpilot later told me the reviewer had deleted the review and that the matter was resolved and closed, while my saved notifications, screenshots and reinstatement history showed a much longer publication history than a single review being voluntarily deleted once. The same problem was visible on Consumer/Hooded_Saw: I had screenshots of the Review Versions panel showing repeated reinstatements, including entries from 6 and 8 December, and when I opened the same history again those reinstatement entries had disappeared from the visible panel. [CID: 109]
I copied the ACCC into the correspondence and demanded an explanation for the disappearing history. [CID: 110] By then the evidence I was relying on was not merely a review that Trustpilot disagreed with me about. Trustpilot's own merchant-facing record had shown repeated reinstatements, I had captured it, and then the visible history was compressed so those entries were no longer shown. I demanded preservation of the internal record, an audit trail and an explanation of what had changed because I was watching evidence of Trustpilot's own handling disappear after I had already put the company and regulators on notice.
On 15 December I posted a TikTok explaining the history through the work logs, the split, the harassment and the fact that Legion was still running.[CID: 111] On 19 December Edward appeared in the comments saying I was a clown who was too focused on SkyNet to create new features. I answered with screenshots of his earlier messages telling me my children would be better off if I killed myself, calling my partner a slut and accusing me of raping or touching my own children. Other commenters then spoke about remembering the workload logs and about the help I had given struggling console server owners. The same person who had used suicide encouragement and child-focused accusations in Discord was following the story onto TikTok to mock me again.
On 22 December a Google AI-style summary about Legion pulled together accusations about server sabotage, support, token handling, bans and the rivalry with SkyNet and presented them like neutral background. [CID: 112] The same story had already been repeated on Facebook, Reddit, Trustpilot and hostile websites, so search found the repetitions and an automated summary turned them into another source. Something written in Discord could be copied into Facebook, carried into Trustpilot or Reddit, surfaced by Google, condensed into an AI summary and then brought back into Discord by somebody who thought they had independently researched me.
The same day I preserved a more deliberate credibility trap around AggroPVP.com. A fake DMCA-style mirror could be made public long enough for me to capture or share it and then changed back, creating an easy response that my screenshot must have been fake because the page no longer showed the same thing. [CID: 113] That is why the archive keeps the page captures, the surrounding Discord material and the recording together instead of relying on what the live URL happens to show later.
I filed Google removal and defamation requests because the source platforms were either leaving material up or taking months to change their decisions. [CID: 114] [CID: 115] On 23 December I went back to eSafety with another formal complaint, ACA-2025-0729927 / CRM:0190734, specifically challenging the way the continuing campaign was being reduced to "purely reputational harm." [CID: 116] I was dealing with publication of what people said was my home address, threats, direct suicide encouragement, false criminal accusations, private photographs of my children, family intimidation and people discussing violence after being told I was a pedophile. eSafety did not investigate the wider campaign and instead referred me toward counselling services. By the end of December I had also made a Scamwatch report about AggroPVP.com and was still sending material through Google, Meta, Reddit and Trustpilot at the same time. [CID: 117] Having all of that reduced to "reputational harm" felt fucking insane.
By January Edward was back in my TikTok comments and accounts from the wider SkyNet
circle were still interacting with Legion content.[CID: 118] Then somebody came into
my Discord and openly posted a file advertised as MassReporter&Lagswitch.zip. It was posted
in multiple channels. Another account then shared a folder described as a "SOCIAL MEDIA MASS REPORTER &
LAGSWITCH." At the same time, my Discord Account Standing suddenly moved to "Very limited" with four active
violations, including new harassment/bullying and violent/graphic-content flags based on older messages.
Those restrictions hit first. Then Discord reviewed some of the decisions and removed them. One of the
official messages specifically confirmed the violent and graphic content violation had been reviewed and
removed. Discord does not show the identity behind a report.
What I had in front of me was people openly distributing mass-report tooling, my account getting slammed with clustered enforcement on old messages, and Discord then reversing some of those decisions after review. [CID: 119] If your account is the one your customers contact for support, "we removed the violation later" does not undo the hours or days where your account is visibly restricted. The restriction hits immediately, while a later reversal happens quietly after the damage and interruption have already occurred. That pattern came back again later.
On 17 January Edward went back through months of Legion Facebook posts and spammed the same comment across them: "Nice try pal! One day you'll learn." [CID: 120] He posted it on current material, a TikTok link, the ProjectJackelope documentation and older Legion posts reaching back into July 2025. It was not one reply appearing in his feed. He was deliberately back-scrolling through my page, hitting unrelated posts with the same taunt and flooding my notifications.
KaLee Whitmore confronted him publicly in those comments and said he had sent her pictures of my children and that she had screenshotted the proof before he tried to delete it. [CID: 121] The child-photo history was no longer only something I was saying from my own screenshots. Another person was challenging Edward about it in public while he was actively spamming my Facebook posts.
I also went back to MWFJunkie and received the fuller account of the old FTP dispute involving Azzy. [CID: 122] By then the earlier warnings were sitting beside years of fake identities, server access, private information, family photographs, pedophile smears, copied work, hostile reviews and coordinated reporting. What I had once treated as other people's separate disputes no longer looked separate after the same types of conduct had followed me across several years.
On the same date I also preserved another technical link in a form that was difficult to dismiss as me inventing a connection. SkyNet's own support AI described DayZSkynet.com and SkyNetVSLegion.com as appearing to use the same IP and also linked AggroPVP.com into the same hosting picture. I posted Same IP Same Game around that evidence rather than treating the IP by itself as proof of who controlled every account.
The ACCC trail was still active as well. On 6 January I sent it the contradictory Trustpilot ABN information, the retaliatory editing workflow and the disappearing flag-history problem. [CID: 123] On 8 January the response put me back onto general consumer pathways, which did nothing to stop the live publication or restore the history that had already disappeared. [CID: 124]
The evidence-history fight continued into February.[CID: 125] I again copied the ACCC into correspondence about Trustpilot's changing description of the Kamy review. One response said the review had been filtered for "Not based on genuine experience" rather than deleted. Later Trustpilot said it could only provide the information still available in its system and claimed the reviewer had deleted the most recent review. That did not restore the review states and reinstatement history I had already captured before parts of the visible record disappeared.
The pedophile smear was still being repeated in February. One preserved Joel Walker post told people to "Keep defending the kiddy ticklers Legions Killfeed," while another post told communities using Legion and several other services they would be banned. [CID: 126] In early March the Mr Glizzy / Silly account sequence added another round of alternate-account activity and pedophile comments. The public retelling then stripped away the kicks, bans and alt-account context and used the remaining ban screenshots to portray me as the abusive moderator. [CID: 127]
I did not respond to that by asking Trustpilot to take my word for it. [CID: 128] I demanded the audit trail, the case numbers, the exact status history and a functioning appeal route, issued a preservation notice and copied both Trustpilot Legal and the ACCC. I had already learned that if I did not save their emails and screens myself, the later version of the platform record could be different from the version I had been looking at when I made the complaint.
By that point there had not been a clean gap where one episode ended and I got my life back before the next one started. December 2023 alone had a burst of roughly 100 abusive Discord messages. January 2024 brought the real-life death threat, Edward sending my children's private photographs to Feather and the sexual threats against my family. June brought the 72-notification capture, 19 separate child-related references or images, my address being thrown back into the public argument and direct instructions to kill myself. [CID: 129] The following year added hostile domains, repeated review reinstatements, the Facebook pile-on, competitor reviews, Meta refusals, Discord strikes against my responses, TikTok comments, another return of the doxxing site, then the mass-report tools and clustered Discord enforcement in January 2026. I was coding and supporting customers in the gaps between saving screenshots, writing platform replies, opening cases and checking whether the next account or review was another person from the same history. [CID: 130]
By April I had escalated the handling of the eSafety complaint itself. On 25 April I lodged a complaint with the Commonwealth Ombudsman about eSafety's treatment of ACA-2025-0729927 / CRM:0190734, explaining that I was a sole trader being targeted personally through my business name, my partner, my children, my home and my safety, and that treating the whole thing as business reputation ignored how the abuse was actually being delivered. [CID: 131] I had already gone through eSafety's own process before taking its handling to another Commonwealth body.
The Obviously_Mario thread from January 2024 is still active. [CID: 132] The same discussion space
still had Brief_Ordinary1438, the account with the older Anon PVP connection, repeating the FTP
accusations and other claims about Legion. My response pointed out that both Greedy Peasant and
PissedOffTexan had said the FTP incident was not me, while Mathew had previously blamed Azzy before later
shifting the accusation onto me. PissedOffTexan's involvement in this part of the history was him defending
me against the Reddit FTP accusation, not refusing to support Mathew during some unrelated argument.
When I responded from a brand-related account I was accused of hiding behind
accounts even though I openly said it was mine. [CID: 133] [CID: 134] The subreddit
interface was also telling users links were not allowed when creating posts. The accusation could remain
searchable while answering it with a link to the full evidence was harder. A thread that began around the
fake BahBahBlackSheep support setup was still shaping how strangers saw Legion more than two
years later.
By 14 April the old server-data accusation was still producing practical business harm. A preserved message said Legion would not return because I was supposedly known to get information from servers and sell it to other servers. [CID: 135] That is the kind of sentence that does not need a reader to know any of the people involved. It simply tells a server owner that installing my bot is a security risk, and it was still circulating while I was asking Google and Reddit to deal with the older publications feeding the same claim.
Reddit also removed my ability to participate from another direction. By 5 May the DayZ Multi Tool Reddit account was showing "This account has been banned," and I separately hit Reddit's network-security block while the hostile material I had been reporting was still available. [CID: 136] By then I had not just clicked report and complained that nothing happened. I had Reddit support tickets, direct legal correspondence, Lumen defamation notices, Google complaints about Reddit material and a consolidated Reddit/Google evidence packet tying the publications, account links, moderation decisions and search results together. [CID: 137] Reddit could leave the accusation searchable while the DayZ Multi Tool side of my own presence was banned and my access to the platform was being blocked.
On 11 May I condensed the code history, repo traces, matching bot behaviour, public pile-ons, review abuse and search damage into Nice Grin. It was not a substitute for the archive; it was a short public route into the same evidence for people who were never going to read thousands of files first.
In July I banned an Xbox account using a name tied to my child.[CID: 138] Then another
account appeared using another variation connected to my child. This was years after I had first asked
people to keep my children out of it. It was after Mathew had possessed private photos of them. It was after
Edward had those photos and used them against me. It was after the sexual threats. It was after the June
messages telling me my children would be better off if I killed myself. I followed the Xbox account through
Legion's own associated-account information, old names, shared servers and the Purple Hats/The Collective
network I had already been tracking. The trail led back toward Mathew. I was looking at an account entering
my server using information tied to my ten-year-old child after years of adults from the same dispute using
my family to get at me. Then, on 31 July, I found another cluster of Xbox accounts while I was working on
code: urserversuxx886, CryPus e, MajinSoul1823,
YrJustBad, Diptwich, Lf is tuff, DrunkBlock93,
Your to slow302, MrStreetSweepa and TheDenialssd.
Some were obvious insults about Legion. [CID: 139] Some reached into
parts of my actual life. Diptwich mirrored Ipswich, where I grew up. DrunkBlock93
lined up with my history with alcohol and my birth year. MrStreetSweepa pointed at an old job I
had worked as a street sweeper operator. On the same day I was also sent a screenshot from the Purple Hats
side showing a Discord status saying:
"Soul at Legion KillFeed Smokes Meth & Scams." [CID: 140]
After years of doxxing, family photos, alternate accounts and impersonation, seeing usernames built around where I grew up, my old drinking problem and my previous job did not feel like random strangers choosing funny gamertags. [CID: 141] It felt like another part of my life had been dragged into a fucking DayZ dispute.
The Ray Smith review was another support story that arrived with enough surrounding activity to make me question whether I was looking at an ordinary dissatisfied customer at all. The review claimed a paid subscription had been cut off mid-month after a polite support issue and later expanded into accusations that I lied, suppressed reviews, manipulated feedback and breached American consumer rules. [CID: 142] [CID: 143] [CID: 144] When Ray eventually edited it, he withdrew the false FTC and US-law premise and corrected Legion to Australia, but kept the rest of the accusation. Trustpilot continued publishing it after my notices and deletion demands.
Almost immediately around the Ray Smith dispute, three more one-star accounts
appeared with arbitrary complaints about the website rather than a purchase or an identifiable support
transaction. [CID: 145]
Killfeed review, Kyle and then Anthony complained about layout,
mobile design and the site looking old or difficult to navigate. The wording and subject were so generic
that the reviews did not need a real Legion service interaction to exist. Trustpilot's automated system
blocked or filtered one of the three while the other two remained visible. To me it looked like the same
pattern again: one supposed service dispute followed by a small burst of separate reviews that made the
first complaint look less isolated.
By the Ray Smith incident I had seen the same shape too many times to treat the
timing as meaningless. The July 2025 Facebook campaign produced a burst of one-star reviews and
replacements. [CID: 146] [CID: 147] [CID: 148] The Consumer/Hooded_Saw
support incident was followed by Kamy and Unholy. Ray Smith was then followed by three generic website
complaints from Killfeed review, Kyle and Anthony. Trustpilot's own
automation blocked or filtered one of those three while the other two stayed up. Trustpilot could split
every account into a separate moderation ticket, but I was watching the bursts arrive around the same
harassment history, with each extra review making the original supposed customer complaint look more organic
than it had looked on its own.
By July 2026 I was no longer asking Trustpilot merely to remove one review. I wanted the forced association gone. For almost two years I had done what the platform kept telling me to do. I asked reviewers for identifying information, checked names and emails against Legion's membership and subscription records, checked payment history, answered reviews publicly, used the flag categories Trustpilot instructed me to use, appealed rejected flags, supplied ticket logs, screenshots, videos and transaction records, identified competitor relationships, answered repeated requests for more information and asked Trustpilot to verify whether the people claiming customer experiences had actually bought anything from me. When ordinary moderation failed, I escalated to Legal, asked for one accountable point of contact, sent formal notices, demanded preservation and a litigation hold, made a Calderbank offer, exercised privacy rights to access, rectify, restrict and erase my data, objected to further processing and ultimately demanded that Trustpilot remove the business association entirely. [CID: 149] [CID: 150] [CID: 151]
By 16 July the privacy fight was also before regulators outside Trustpilot. I had active OAIC matters under WEB-CP-26-08655 and CP26/03054 and had complained to Denmark's data protection authority, Datatilsynet, about Trustpilot's refusal to restrict or erase the processing, its continued processing after objection, adverse processing after legal notice, automated decisions and the linked Google-account data I could not disconnect. [CID: 152] I kept copying those regulators into later Trustpilot correspondence rather than letting each new Trustpilot reply reset the history to another isolated support ticket.
I did the same thing everywhere else before resorting to public fights or regulator complaints. [CID: 153] [CID: 154] [CID: 155] I blocked people and documented block evasion, opened Discord Trust and Safety and developer-support tickets, supplied message links and screenshots, and appealed enforcement when Discord punished my replies. I used Meta's in-app reports, support chats, legal routes and copyright channels, supplied URLs and edit histories and even sat through the phone call where support wanted access to my screen instead of dealing with the post. I reported Reddit content and later served formal notices, sent repeated Google removal and legal requests, filed eSafety complaints, contacted registrars when my address was published, went to the OAIC over privacy, copied the ACCC into the Trustpilot evidence dispute, contacted Mathew's family because I hoped somebody close to him could stop it, and kept preserving the evidence when each platform sent me somewhere else. From around October 2025 I was also trying to get the wider defamation case in front of a lawyer on a contingency basis. By February 2026 I had blanket-emailed dozens of firms. The recurring problem was not a lawyer reviewing the evidence and telling me I had no case; the enquiries were being rejected at intake once they saw defamation and contingency together, before the record was reviewed.
Trustpilot's correspondence made that process even harder because almost every
later response was unsigned by an identifiable decision-maker. [CID: 156] [CID: 157] A few older Content
Integrity messages had names such as Neenu D or another first name and initial, but the later traffic
overwhelmingly came from labels such as Trust Support, Content Integrity Team,
Privacy, Legal, an automated Do Not Reply address or another generic
department. I could have dozens of emails about one review without a named person taking responsibility for
the decision. When one team reinstated something another team had removed, or Legal said one thing while
Content Integrity did another, there was usually nobody signing the email who could be held to the previous
answer.
Trustpilot Legal had already shown how meaningless an escalation could become internally. In August 2025 Legal asked me to wait and avoid creating "wasteful costs" while it reviewed the dispute, then Content Integrity reinstated a disputed review within hours. [CID: 158] Reviews that one part of Trustpilot treated as removed or closed could later be back online through another team. I sent preservation requests, a litigation hold, legal notices, deadlines and a Calderbank offer, but Legal never took control of the moderation history in a way that stopped the same review material being processed and republished through ordinary support.
In July 2026 Trustpilot then moved from refusing my removal demands to taking adverse action against the profile itself. It accused me of misusing the flagging tool without giving me one clean schedule of the reports it said were improper, objected to material on killfeed.co, accused Legion of displaying Trustpilot content improperly and threatened restrictions, removal of review invitations, hiding of the TrustScore and a public Consumer Warning. [CID: 159] [CID: 160] I responded by showing that killfeed.co was not using the Trustpilot logo, stars, TrustScore, TrustBox, API, widget or live feed in the manner alleged and by sending formal privacy and subject-access requests for the records behind the warning, misuse classification, website monitoring and moderation decisions.
By then I had hundreds of Trustpilot emails spread across scores of case and thread numbers, and I had to build my own chronology simply to know what Trustpilot had previously told me. On 30 July Trustpilot said Legion had failed to comply with its cease-and-desist, restricted the account to replying to and flagging reviews, withdrew branding permissions, disabled review invitations and announced a Consumer Warning with the TrustScore hidden. [CID: 161] Later that night it delivered a subject-access package including a 184-page communications export and other usage, profiling and enforcement material, but it still did not give me the complete deletion and disassociation I had repeatedly demanded.
On 31 July the red Consumer Warning was public and Legion's rating was unavailable. [CID: 162] [CID: 163] Then on 1 August Trustpilot removed Joel Walker's review after saying it had asked him to edit or delete the material and he had not done so. After all the arguments that its ordinary processes could not simply remove the material I was complaining about, Trustpilot was capable of removing that review while its own warning remained over my business. That was the state of the platform when I sent the further privacy update to the OAIC.
On 3 August a simple Discord question about SkyNet turned into another full argument after I answered with the code-theft history and somebody reacted with an eye-roll. [CID: 164] I responded in detail rather than pretending the child-photo issue was some vague side argument. I said Mathew had saved photographs of my children from my private Facebook account, that Edward later obtained and used those photographs, and that the children had repeatedly been dragged into attacks that were supposed to be about code, bots and DayZ servers. I said Mathew was living with a registered offender. The public-record/portfolio composite I posted with that statement placed a search result describing a lewdness-with-a-child-under-14 conviction beside a Mathew Trojanowski portfolio page. I posted that material while explaining why the private child photographs, their redistribution and the people around Mathew were not a side issue to me. The thread then filled with support, objections to the @everyone ping, arguments about reporting the conduct and people debating how far a response was justified.
That same 3 August record contains much more than the argument itself. I posted the R BRODIE Xbox material: the Xbox profile displayed the name Robert Brooks, Legion's own retained activity showed the R BRODIE account in the service history, and my forwarded account-linkage explanation connected the profile to the earlier Purple Hats, The Collective, PVP Island and Anarchy++ records I had been documenting. Another capture shows Discord Account Standing with five active violations, four classified as violent or graphic content and one as harassment and bullying, together with temporary access restrictions and account-standing consequences extending into 2028. The conversation continued into 4 August with people comparing enforcement screens, discussing reports that had been removed and talking about the earlier child-image sharing. [CID: 165]
On 5 August I sent the next Trustpilot privacy update to the Office of the Australian Information Commissioner under complaint CP26/03054. [CID: 166] I told the OAIC that Trustpilot's 30 July subject-access response had not resolved the rectification, erasure, restriction or Article 21 objection requests, and that the package still omitted the enforcement, monitoring, classification and decision material I had specifically asked for. The OAIC acknowledged receiving the update. By then I was not dealing with one platform complaint. The same dispute had produced Discord enforcement against responses, repeated Meta reporting and support calls, Trustpilot Legal and privacy correspondence, eSafety complaints, Google removal requests and repeated attempts to find a lawyer I could afford.
On 6 August I preserved three Google sessions for exactly the same Legion Killfeed search because the first page was not being presented consistently. Legion remained the leading result, but the ordering below it changed, the AI Overview presentation changed and a SkyNet result appeared in one presentation and not another. The point of saving all three sessions was the visible difference itself: somebody searching for the same service at roughly the same time could be shown materially different surrounding results and generated presentation. [CID: 167]
Feather was originally my friend, and our retained DMs give her a confirmed and secretive connection to Purple Hats. On 27 August 2025 she told me outright, “I'm friends with ‘purple hats’.” On 16 May 2026, while talking about one of them, she said “If I was still friends with rage I'd give him info”. On 13 June she showed me the Bypass / Purple Hats DM where Virus†Bypass wrote “Like the new server? Also his website n gameserver won't seem to stay up for long”, while Feather told me “it sounds like kami made friends.” On 11 August a separate person then gave me another direct connection I had not supplied for them. After I showed the Purple Hats / Bypass material, they replied “NOOOO WAY”, “thats it”, “thats how I know Kamikaze” and “him and perplehats play together”, then said they had come into the same redacted server together years earlier. That sat beside the pattern I had already been explaining to customers: Purple Hats accounts presenting themselves as people fighting “admin abuse”, provoking or using minor public conflict with a server owner as justification for escalation, then showing up around DDoS, server-crash or mass-report material. I had also repeatedly noticed Purple Hats-associated accounts in the Lawless Distopia Discord community. [CID: 167]
The platform records kept moving at the same time. On 13 August Facebook first displayed a hate-speech standards enforcement notice suggesting my account was banned for it, then later displayed an account-restoration notice saying the reviewed account followed Community Standards on account integrity. On 14 August Facebook advertised Meta Verified to me with the wording “stop impersonation before it starts”, selling proactive account protection, prioritised support and a verified badge months after Meta staff had miscategorised my report about Joel Walker's Facebook post as “impersonation”. That sequence suggests Meta then used harassment material it still had not removed to market paid protection to me while the hostile publication and the legal obligations I had already raised remained unresolved.
Trustpilot's 14 August disclosures were even more specific. Its two-page Contact Details export identifies Anthony Brodie, the Killfeed account and legionkillfeed@outlook.com, and records the internal tier status “Minimum - DO NOT CONTACT” together with Business User ID 66d82d425be1f1001bb7d149. The F3 disclosure puts the July enforcement trail together in Trustpilot's own records: the 3 July message called the display of Trustpilot reviews “scraping”; the 11 July warning said a consumer alert was being added; and the 19 July cease-and-desist described itself as the final warning and threatened a prominent Consumer Warning for at least six months, a hidden TrustScore, restrictions on the Business account, removal of access to Trustpilot brand assets and TrustBoxes, and stopping Trustpilot review data being shared with search engines. My 15-page response in request 03030641 then used those newly supplied records to challenge the earlier SAR search, make a fresh Article 15 request for the later enforcement period, continue the rectification, erasure, restriction and objection requests, and ask for the records behind the “DO NOT CONTACT” classification, automated processing, Google and Veriff verification, invitation suppression and recipients of my personal data.
On 17 August the Purple Hats / Bypass contact came back again. A Discord profile using username js6r, Purple Hats branding and an “Alt-Account” profile line sent me another friend request. I answered with an explicit no-contact notice and recorded Discord user ID 461963351707222035, the same identifier already preserved in the June Purple Hats / Bypass records. The notice tells the account not to send more friend requests, DMs or indirect contact. The account sent another friend request anyway and then hurled insults at me and my fiancée. Its status called me a “kike” and said “Soul from Legion Killfeed smokes meth”. After that I ended my friendship with Feather. I cannot remain friends with someone who will sit by while people she is connected to target my fiancée like that. [CID: 167]
The final 17 August composite does not make the older MassReporter material new. I had preserved that months earlier. What I found now was the same account trail using the Queen Python profile, carrying my private note “PIGEONS ARE DRONES / onetoolshort” and advertising bot development including a “Jupiter AntiSpam BOT”. The earlier PIGEONS ARE DRONES posts repeatedly pushed a MediaFire MassReporter/Lagswitch archive and said “Feel free to mass report the server”; the Carl-bot records show the same Discord ID, 1435049062897422346, in ban case 264 and in the deleted-message log containing that link. Seeing that account now marketing an anti-spam bot beside the wider Purple Hats spam and mass-report record suggests Purple Hats are creating the demand and then selling their anti-spam product to people they have been harassing.
The record continued after 17 August. On 26 August I preserved a sixteen-page Google AI Mode session showing materially different framing as the same archive was supplied with more context. On 28 August I added three ACCC evidence packets covering Trustpilot’s enforcement trail, the subject-access completeness dispute and the follow-up privacy/data-processing correspondence. On 8 September I preserved the twenty-one-page continuation of Google removal case 6-6692000040714, and on 11 September I preserved the complete visible r/DayZDiscussions thread about Legion Killfeed and me. All six source PDFs are linked directly in the updated proof record. [CID: 168]
What the record shows by the end
The language in this record changes as the years drag on. The early material is mostly technical: code, server access, account links, logs and formal reports. As the same allegations, doxxing, child targeting and suicide encouragement kept resurfacing, while platforms repeatedly reduced a connected history to one post, one reply or one ticket, my language became more profane, angry and exhausted. That progression is part of the evidence too. It shows what repeated exposure to an abusive, fragmented complaint system did over time, rather than pretending every message was written from the same emotional starting point. [source] [source]
The process became Kafkaesque because every platform could demand the full context and then judge only a fragment of it. Reports were redirected, closed, reopened, split between teams or sent back to the same service already being complained about. At the same time the people, accounts, reviews, screenshots and accusations could move between Discord, Reddit, Facebook, Trustpilot, Google, Xbox and hostile websites. A new account or repost could effectively reset the process while I had to reconstruct years of context again. [source] [source]
That is why this site is built as a dated, source-linked record rather than a defence of individual reactions. It preserves the June 2023 SkyNet split and development history, the later account and infrastructure incidents, the publication of my home address, threats and family targeting, the platform and review trail, and the commercial consequences that followed. Mathew Trojanowski, Kamikaze, DayZ SkyNet, SkyNet Killfeed and SkyNet 2.0 appear here because those names recur in that record. The point is to let the sequence be read in full instead of allowing the entire history to be reduced to whichever screenshot happens to be circulating that day. [source] [source] [source]
Read the whole record.