History

Legion Killfeed history

Legion Killfeed history, Soul's DayZ work, public records, and the evidence timeline behind the Kamikaze/Mathew source-code theft and harassment record.

The Soul - First Killfeed Attempts

Aggro PVP - #1 on Jeaber’s Killfeed leaderboards for 3 years!

Aggro PVP was where the most DayZ console players knew Soul from before Legion Killfeed. It had both DeathMatch servers and Full Map with heavy traffic, Aggro PVP achieved the longest run at the top of Jeaber’s DayZ Killfeed global leaderboard.

Soul's Aggro PVP held the #1 global server spot on Jeaber’s DayZ Killfeed leaderboard for several years. He had three servers inside the top 10 for kills and player activity. Aggro PVP NWAF, Aggro PVP Kamy, and Aggro PVP Full Map were visible beside the biggest console PvP communities in the scene.

That meant dealing with busy-server problems every day: population swings, combat arguments, staff trust, spawn tuning, economy balance, performance complaints, Discord structure, Nitrado limits, leaderboard pressure, and players expecting fixes.

Aggro PVP is the server-owner background where Soul learnt what all server owners experience, which gave him the path to build Legion Killfeed in a way that improves the admin experience in the most simple ways possible.

Aggro PVP was the #1 server on Jeaber's Killfeed before Legion was made.
Before the #1 hold, Aggro PVP NWAF was already sitting near the top of Jeaber’s global server list while Aggro PVP Kamy was also visible on the board.
Aggro PVP NWAF at #1 on Jeaber’s DayZ Killfeed global server leaderboard, with Aggro PVP Kamy and Aggro PVP Full Map also inside the top 10.
Aggro PVP NWAF still holding #1 later on, with multiple Soul-run servers still sitting in the top 10. Legion Killfeed came from that server-owner background.

Greedy Peasant's Server Reviews - Tech Support from "Super Soul"

After DayZ and Discord Services (DaDS) started burning Soul out, so he majorly slowed down with the customers he took on.
The first server Soul was banned from was TheGreedyPeasant's "HELL IN LIVONIA" but it had been several years since then Soul stumbled into being Tech Support in TheGreedyPeasant’s community, from banned by the owner, to running his discord. This gave Greedy the freedom to focus on his server-review/promotion streams where he focused on positives to help promote servers, by doing this promotional gameplay it showed everyone all the brilliant servers and helped them find a server designed perfect to their style. Soul handled all of the Discord side: setting up channels & custom commands, organising server lists, recruiting new servers, moderating his peers, providing support, resolving community issues and technical questions in chat.

The nickname "SuperSoul" came from the community, Soul was always there to help as soon as anyone asked, he would fix the problem and even explain where they went wrong, until he kept getting pulled into arguments with trolls, most were just rage-baiting doing petty stuff.

The relationship cooled because the toxic groups started to cross into communities Soul was trying to help and the unpaid fixer role kept growing, it became not worth the hassle so Soul lost the passion and returned but to keeping to himself for a while.

Greedy Peasant's Server Reviews was part of the period where Soul was helping with Discord structure while Greedy focused on server reviews.
The "SuperSoul" nickname was used by all while Soul showed up for free and help with all Discord and server problems.
The nickname lived inside the community rather than being a formal brand.
The repeated use of the SuperSoul emoji shows it was a running community nickname for Soul, not just a once off random emoji.
This shows how Soul used humour during community conflicts using it to diffuse drama and people leaned on Soul for the practical call.

DayZ Multi Tool

DayZ Multi Tool came from Soul linking up with JayJay after the D.M.A.E. and Law’s Killfeed circles brought the right people into the same space. It became a Discord-based DayZ reference and utility bot for item lookups, XML help, file explanations, and repeated server-owner questions.

The goal was to stop basic server knowledge being locked behind a few people. If someone needed an item name, file clue, spawn hint, category, or command example, DayZ Multi Tool gave them somewhere to start.

DayZ Multi Tool connected server ownership to public tool development. Legion?s setup flow, file tools, search pages, and guides followed the same idea: turn repeated support questions into tools people can use.

Spawn file help has been one of the repeated free support jobs Soul has given owners for years.
A lot of the free support was turning what an owner wanted into valid DayZ file structure that would actually load.
Repeated spawn mistakes became the kind of problem Soul helped explain publicly, then later turned into tools and validators.
Spawn gear support needed exact nesting, valid syntax, and working structure, not random advice that failed on restart.
The same support patterns Soul repeated for free are the patterns now built into faster reusable editor and generator logic.
Events.xml support kept coming up for owners dealing with lifetimes, restocks, names, nesting, and broken XML.
Those repeated free explanations became clearer support material and file-checking logic for problems owners still hit today.
Lighting and object work is another example of Soul giving exact file help where small mistakes can break the result.
These older manual support examples show the same thing Legion still does now: turn messy DayZ file work into usable answers.

DayZ and Discord Services - DaDS

DayZ and Discord Services was Soul doing small DayZ and Discord jobs for low prices. Discord setups, server edits, XML changes, file repairs, and direct troubleshooting were normal work.

Accolade shows that period: exact briefs, direct file work, handovers, and server owners not being left stranded when Soul stepped back from paid side jobs.

The low-cost Legion Killfeed model came from that earlier work. Soul was already doing server and Discord jobs for low amounts before there was a subscription bot.

DaDS was Soul doing cheap DayZ and Discord work before Legion Killfeed became the main service.
Accolade shows the paid-help period in direct Discord form: someone needed work done and Soul dealt with the job.
A lot of the work was rough, fast Discord help that solved the issue in front of the owner.
The support trail shows practical answers instead of hidden server knowledge.
Some jobs were direct file work, some were Discord setup, and some were explaining what broke.
The same pattern later became setup guides, command flows, and website utilities.
Before Legion Killfeed subscriptions, Soul was already turning repeated help into repeatable systems.

Aggro PVP - Proof coding is so easy, even a drunk can do it!

Soul has never hidden that he had an addiction to alcohol (it was never a problem). In October 2022, Soul dug out his old killfeed code and worked on it to distract himself, after getting passed a bug that had him stuck for ages, he realized how long he had gone without alcohol. The idea became simple: if he's coding, he's too busy to drink.

By April 2023, he had worked on code every day since October while still working two jobs. Legion Killfeed came out of that stretch of work. It was not a weekend clone or a borrowed public script. It was also part of staying sober.

When Joel Walker made the November 2022 "drunk blathering" comment he knew Soul was trying to get sober, but rather than be hurt by words, Soul turned it into his server's slogan: “Aggro PVP - proof coding is so easy, even a drunk can do it.”

The drunk insult became Aggro humour: loud, self-deprecating, and turned back into work.
Soul was open about the addiction, then used coding as the replacement habit that kept him sober.

Legion Killfeed

After Aggro PVP closed and another owner took over Aggro PVP with the request Soul stayed as admin and coder, this gave Soul enough time to return to working on the killfeed idea. The old "The Soul" code became the starting point for what became Legion Killfeed.

Kamikaze420 and SaltySilver were brought on at first because Soul was still new to building the bot at that scale and he wanted to ensure it had a full support network. The bot started getting attention because setup was simple, the feed output was visual, and normal staff could understand what happened without reading raw logs.

The current Legion Killfeed service is the solo continuation of that work, Soul has done all updates, provided all support, personally helped users setup the bot, built heaps of file tools, customized and added all the feeds, built in moderation & tracking features that no other has and done it all for the cheapest pricing out of all comparative bots all without annoying feature paywalls.

Proof of Kamikaze's bot code-theft.

Soul split from the others in June 2023 and despite all the misinformation circulating, it came down to workload, ownership, and control. Soul was doing the work, it's proven that Soul did 1935 edits to the bot's code to Kamikaze420's 55 total edits & SaltySilver's 22 total edits, Soul said it plainly, if the others wanted equal shares, they had to contribute equally. He was told they weren't interested in making money so he deleted his intellectual property from their shared workspace, factory reset it to prevent restoration of his code and left to rebuilt alone. SaltySilver confirmed Kamikaze420 has a backup of Soul's code and evidence surfaced showing Kamikaze420 using ChatGPT to "rewrite" Soul's code in an API. To add insult to injury, Kamikaze420 even used Soul's servers logfiles to have the AI "rewrite" the stolen code.

The evidence shows Anthony “Soul” Brodie with 1,935 provable actions and edits tied to the original code history. Mathew “Kamikaze” Trojanowski did not contribute more than 50 edits in 8 months and the trainee later made public death-wish comments toward him.

Kamikaze's bot stole Legion Killfeed's code - See for yourself.

The shared repo was deleted on June 25 2023 Repo.destroy entry placed beside the split-up discussion, showing the deletion happened directly alongside contribution and workload arguments.
Soul raised the workload issue and Kami's reply was about something else Discord messages showing Soul asking for contribution and coordination while Kami replied that he was not chasing money, leaving the workload issue unanswered.
Soul raised workload, contribution, and overlap concerns directly Message breakdown showing Soul asked for more contribution, proposed a WIP workflow, and framed the bot as a business rather than a hobby.
Kami's reply largely sidestepped the workload issue Side-by-side breakdown showing Kami acknowledged money was not the point, while Soul's core concern remained contribution, ownership, and business work.
The.git folder Local backup and history folder explaining how clones, commits, refs, branches, objects, and GitHub snapshots preserve the repo trail.
The same code appears in Our-Projects Hash comparison showing 45 of 50 exact matches from Soul_Bot.zip inside the Our-Projects beta and Soul Bot archive.
Soul_Bot.zip was the starting point Earliest preserved bot package with embedded pyc metadata and file dates from September to November 2022.
The code carries forward into Other_Bots Other_Bots-main.zip contains exact matches to Soul_Bot.zip, showing continuity rather than a fresh start.
The traced.git history starts with Soul Backup trail begins with Soul's local clone and early administrative follow-up commits.
The traced.git commits still lean heavily toward Soul Selected traced commits show Soul making the heavier run of multi-file changes while Kami's available history is shorter and more limited.
What major work was supposedly outside GitHub? Breakdown showing the stolen-code project was bot code, feed logic, ADM parsing, commands, and repo history rather than a separate website or dashboard build.
The traceable action records are even more one-sided Saved action records show 1,935 Soul actions, 55 Kami actions, and 22 Stojo actions, with Soul as the primary maintainer by a wide margin.
Setup and configuration Counted setup/config work showing 434 Soul actions, 22 Kami actions, and 13 Stojo actions.
Admin, patterns, debug and reloads Counted admin command, pattern, debugging, reload, gitpull, lex, and image work showing 350 Soul actions.
Heatmaps and base damage Counted heatmap and base-damage sections showing 166 Soul actions against only a few actions from others.
Stats, leaderboards and info Counted stats, leaderboards, info pages, category work, and DB sections showing 391 Soul actions.
Bot systems and status Counted bot, botstatus, and status sections showing 261 Soul actions across bot files and system status work.
Killfeed and feed logic Counted killfeed-embed work showing 333 Soul actions, 6 Kami actions, and no Stojo actions.
See for yourself Exact counted action timeline visible in the screenshots, summarising 1,935 Soul actions against 55 Kami and 22 Stojo.
The public commit graph already leaned heavily toward Soul Public GitHub graph for February to June 2023 showing Soul had about 4.7 times as many commits as Kami during the public period.
The repo itself points back to Soul and Aggro Saved repo traces connect Soul identity, config references, branch names, code references, and Aggro server links.
Kami's account and uploaded files The same account is shown with uploaded bot files and the Kamikaze's stolen-code bot announcement in the sidebar.
Kami said GitHub doesn't show all the work Screenshot of Kami arguing GitHub did not show all work, paired with explanation that deeper records still pointed heavily toward Soul.
Why Kami's theft denial backfires Breakdown showing the archived history and saved action records make the off-GitHub-work theft denial weaker, not stronger.
Salty Silver's message Direct message where Salty distances himself and says Kami had the backups, not him.
The upload points back to Soul's server Uploaded logfile includes the Aggro PVP server page number, pointing the file trail back to Soul's Aggro PVP server.
This chat asks for FastAPI work Discord request asks for a FastAPI component using killfeed-embeds.py and turn0 into a FastAPI/database-only component, using Soul's file.
The Kamikaze's bot announcement The announcement denies the code theft while the surrounding cards track the conflicting evidence, while the surrounding cards track conflicting evidence.
He blamed Soul for the work-in-progress state Public chat screenshot combines blame toward Soul with an assertion that project code could still be restored.
Kamikaze's bot setup card closely mirrored Legion's setup flow Comparison showing similar setup sequence, wording structure, and channel creation flow between Legion and Kamikaze's bot setup cards.
The bot appeared online while Kami said it had no token yet Public chat screenshot shows a visible online bot presence in the same conversation where Kami said the stolen-code bot was not yet set up.
The DM mixed slander complaints with an admission of slow progress Direct messages mix complaints about Soul with payment pressure and harassment attacks, while also admitting limited output and slow progress.
Kamikaze said aggropvp.com was going live with 44 screenshots Public message says the website was going live and that some screenshots were not flattering to anyone, followed later by a specific screenshot count.
The harassment escalated from blackmail threats to retaliation threats Messages moved from blackmail threats and personal-information exposure into direct threats and hostile escalation language.
JayJay said the website was published, and Kamikaze denied it was him Chat contrasts a third-party description of the website being published with Kamikaze's public denial.
Soul tried to address the split privately before the public fallout Earlier private exchange shows Soul raised the issue directly and Kami said text was the wrong medium before public escalation.
Legion explained the bug while Kamikaze's bot struggled to identify it Discord thread shows Kamikaze's bot unsure about a server-wipe/server-status issue while Legion explained the likely cause and fix path.
Soul identifies the bug immediately General-chat and team-chat screenshots show Soul naming and explaining the exact cause while the original developer did not identify it.
Still watching Soul's profile Card compares Kami chat mirrors with Soul's profile wording and shows repeated phrasing after profile-watching comments.
Questionable intent change on a verified bot Discord block evidence beside Kamikaze's second stolen-code bot version request gateway intent changes, raising questions about what changed after earlier verification.
Denied it, then threatened it Same public record contains denial of involvement in the website and later threat language around using or posting about the site.
AggroPVP crossed into open abuse Public abuse response and platform action evidence showing the harassment moved past criticism into personal attacks.
Proof gave way to personal abuse Evidence of proof being met with personal attacks, face-crop posting, and confrontation instead of a clean factual response.
Open Code threat in public Public argument where a demand to release code escalated into threats and ridicule after a failed setup harassment.
Message tracking exposed the gap Kamikaze's bot bragged about bot messages already passing 18,000 while Legion's screenshot showed far higher output in the same timeframe.
The Aggro denial sat beside Kamikaze's bot's own Aggro server presence Announcement and server list evidence show Kamikaze's bot displayed with Aggro PVP while the announcement downplayed the connection.
Infiltration framed as a win Kami praised infiltration and later Crix was shown using an alt to access Legion, linking bragging to later access evidence.
Clone command list posted while Soul was dismissed While Kami said Soul was wasting time, Crix posted a cloned Legion-style command list.
Lykos tried to help Screenshots show a community leader trying to get slander taken down and get Soul to help rather than joining the pile-on.
Set up first, fake token later Bot setup screenshots show a server returned using a token, while a later claim described a fake token story.
New-user act vs old-account history Contradiction between an account pretending not to know what was happening and an established role/account history from 2021 and 2024.
Helpful in beta, hostile in smear threads Earlier public praise during free beta help is contrasted with later hostile comments in smear threads.
Sock-puppet pattern around a free beta Setup and subscription screenshots show a beta incident moving from setup help into Discord posts, Reddit, forums, and threat screenshots.
Same-night Discord and Reddit overlap Discord conflict and Reddit commentary appearing in the same time window, showing the same harassment crossing platforms.
Pile-on around the thread Additional accounts pushed the same narrative after the thread went live, with repeat claims and profile-history context.
Drama brought in, then review threats Bot-community and DayZ Multi Tool screenshots show an outside drama topic being imported and then tied to review threats.
Bug handled, then turned into drama Command issue was acknowledged and fixed, then recycled into public drama despite the error logs confirming the actual issue.
The harassment attack moved into DMs Message request screenshot shows the same harassment attack being pushed through direct messages, not just public chat.
Crix pasted a smear into chat Public messages show pasted negative claims about Legion and Soul being pushed into chat channels.
Kami asked Soul to check the code Screenshot references Kami asking Soul to check earlier request-review code while responsibility was being argued elsewhere.
SecurityTrails-related message was shown as evidence Soul had been given the Kamikaze's bot IP by them The card reframes the screenshot as infrastructure-related receipt material rather than proof of a tactical attack method.
False DDoS harassment was pushed while same-IP evidence surfaced Discord harassment and SecurityTrails evidence appeared together, conflicting with the public narrative being pushed.
FTP harassment, screenshot-edit arguments, and contradictions collided on the same day More FTP-related harassment, screenshot conflicts, and contradiction evidence are shown in one bundled escalation point.
The attention shifted toward Skizza the next day Uploaded screenshot shows attention moving from Soul toward Skizza after the issue was not resolved.
General-chat harassment kept repeating the same claims General chat thread shows repeated claims, pressure, edits, and timeout evidence turning private issues into public spaces.
After Queen said she ended the partnership, the mods chat turned openly hostile Mod-room screenshots show disagreement turning into open hostility and escalation instead of a calm private resolution.
The fallout kept spreading Onlookers discussed the argument as something that could scare off future partners, showing the harassment had widened.
Ozzie said he had seen a private repo and focused on deleted messages and loyalty Private messages show confrontation around deleted messages, switching sides, and frustration over who was cooperating.
Private messages nudging a Legion user toward a competitor Captures show a user being privately steered toward another service while the harassment campaign was still being discussed.
The pups account connected the timeline to the same person behind AltDetector Screenshots connect private steering, Discord names, and AltDetector activity around the same user pattern.
A months-old payment argument was reused as a fresh hostile DM exchange Private messages show an old payment argument being revived, mixed with scam harassment and reused as another attack point.
Kami recruited people and made self-harm harassment references Captured comments show harassment prompts and self-harm references aimed at Soul rather than a legitimate product complaint.
Joel Walker took another harassment thread public and tried to pull Soul into a direct reply Facebook and TikTok material show a third party amplifying harassment and trying to drag Soul into public response.
AltDetector's closure post revealed the operator redirecting users elsewhere Shutdown screenshots show a sole-owner notice, refund wording, and a redirect away from Legion while hiding operator identity.
The public pile-on moved into DMs full of posturing, denials, and pressure Contact screenshots show public escalation continuing in direct messages with pressure and accountability arguments.
A later contact from the same circle added another explanation that clashed with earlier links New definitions and domain/contact screenshots add another explanation layer that conflicted with earlier AltDetector and pups links.
A public still-being-charged claim resurfaced despite recent subscription records Subscription screenshots and public posts are paired to show the claim was being repeated despite fresh records and support replies.
After Soul posted a proof-backed warning, the AltDetector side gained a new ally who publicly challenged him Public post sequence shows a warning, a challenge, and another profile entering the harassment.
Mr Tech N9ne was removed after a harassment allegation, but the smear continued Removal and follow-up posts show the service revocation did not stop the false claim from being circulated.
Private abuse and public rumor-sharing started building before the major ramp-up Screenshots show private hostility and public rumor sharing before the later coordinated-looking push intensified.
The Facebook harassment escalated into calls to report Legion and leave hostile reviews Threats of commentary, review-bombing, and report instructions show the harassment becoming an active pressure campaign.
A Facebook complaint thread quickly turned into a public pile-on Complaint post and comment activity show a broader anti-Legion pile-on forming around the original post.
Supporters forwarded proof that the hostility was spreading beyond Facebook into Discord channels Discord and supporter messages show the same hostility moving across wider Discord circles.
Repeated Facebook reports were filed, yet much of the damaging material remained online Meta report responses and follow-up lists show many reports were submitted while harmful posts still circulated.
Trustpilot reinstatement loop Review screenshots show repeated removals and reinstatements, with the same review harassment resurfacing.
Positive reviews missing Screenshots show supportive reviews not appearing while negative review harassment material remained visible or kept circulating.
Star rating damage Trustpilot screenshots and rating data show visible star-rating impact even when hostile review visibility changed.
Trustpilot transparency and invite records became another harassment thread evidence point Trustpilot transparency, invite records, and false-transparency claims became part of the broader harassment record.
The warning was in the comments, and the attacks followed Comment warning and follow-up attack examples show the predicted pile-on materialising after the public post.
Joel kept reposting and bumping the same public attack Public posts and bump activity show the same material being reposted and kept in view.
The public pile-on spilled into direct contact and secondary harassment Outside contact and direct-message examples show public posts turning into direct pressure on Soul.
Meta reports were filed on Joel Walker's Facebook posts Report review screens and moderation screenshots document the Meta reporting trail attached to Joel Walker's posts.
Reports were filed, but moderation responses did not stop the material from circulating Notifications and support responses show reports were submitted while the harassmentd material continued to circulate.
A burst of Facebook posts, comments, and notification shows the issue turning into a visible spam wave Repeated Facebook posts, stacked comments, and notification volume show a sustained pile-on rather than one isolated complaint.
After the first post drew reactions, the situation kept escalating instead of cooling off More comments, tags, and public reactions show the issue continuing after the initial post.
Trustpilot captures point to review-flagging, moderation conflicts, and inconsistent handling Screenshots show flagging activity, follow-up replies, and review-management conflicts.
Joel's Facebook posts repeated the same slander themes Multiple posts repeat theft evidence and harassment, scam harassment, and loaded personal harassment.
Discord screenshots suggest the reporter was hit with action while the broader harassment remained unresolved Account penalty screens and report context suggest action against the reporter while wider harassment remained active.
Reddit discussions and report screens show the same harassment reports spilling onto another platform Reddit posts, report submissions, and complaint screens show the claims moving into Reddit.
By April, the harassment sat beside clear competitor positioning while search traces kept the conflict visible Search and public-facing evidence place the harassment beside competitor branding and indexed visibility.
Joel pushed the same style of harassment attacks across multiple bot and community pages Screenshots show repeated cross-page posting, copied talking points, and attempts to spread the narrative across communities.
The harassment quickly moved beyond product criticism into personal insults, mockery, and loaded attacks Public posts and profile examples show personal abuse, hostile phrasing, and ridicule replacing ordinary criticism.
Google results and AI-style search surfaces kept competitor-linked harassment reports visible instead of letting them fade Search screenshots show indexed pages, AI-style results, and snippets keeping the harassment reports visible near brand searches.
Complaints and takedown attempts were lodged, but the reporting trail shown ends in refusals and non-removal Complaint and denial screenshots show reports continuing while removal attempts failed to meaningfully stop the material.
Later Reddit material focused on linked accounts, repeated talking points, and contradictions around the same harassment Screenshots show the same circle of Reddit accounts and narratives resurfacing under different names.
The Jarvis and BoosterZ DM trail revolves around payments, ownership claims, and harassment reports that Ozzie scammed Jarvis Direct messages and PayPal material show the harassment widening into ownership and payment claims.
Later captures mixed delete-pattern claims, renewed personal remarks, paid promotion, and screenshot posting Screenshots show renewed conflict after paid promotion and public posting, rather than a clean resolution.
The same review-style harassment attacks were pushed across multiple pages Facebook group screenshots show the same reviewer and harassment attacks appearing across several pages in the same window.
The review posts were actively bumped to keep them visible Repeated bump-style comments and review posts show material being pushed back to the top instead of fading.
An old private remark was resurfaced as a fresh public issue A year-old private comment was revived and reframed publicly as a current scandal point.
A cropped private quote was recast as a public insinuation A private Discord comment was cropped and reposted without context as a misleading public insinuation.
Final tab: the documented pattern was sustained, cross-platform pile-on, not one isolated complaint Timeline summary card groups the evidence into public-post escalation, review push, private-channel spillover, search visibility, and moderation gaps.

Legion Killfeed’s position is clear and we can legally say this directly: Kamikaze's stolen-code bot stole Legion Killfeed’s code. The record points to matching command logic, matching feature flow, the same bot behaviour, old repo traces, code history matching Legion’s original work, upload logs, support screenshots, Facebook spam, review abuse, search-result damage, and years of harassment aimed at the developer whose work was taken.

Legion Killfeed also keeps a 100% uptime operational record backed by support history and 64 verified Trustpilot reviews , including 63 five-star reviews and one four-star review, showing the real customer record not the fabrications on reddit.

The full public archive is here: https://they-wish-i.died.space/

Jack Jackelope's Facebook Group - How Joel Walker played the victim while attacking everyone.

Reports date back to 2021 Report history shows complaints dating back to June 2021, with the same behaviour still being reported years later instead of being meaningfully stopped.
It wasn't just one post The same style of claims appeared across multiple posts and screenshots, Joel Walker AKA Jack Jackelope paid his way to running a 33,000 member facebook group and used in to attack everyone against him with public spammed posts.
The smears turned personal The public attacks moved past bot conflicts and into personal harassment attacks, keeping the pressure on Soul instead of answering the evidence.
The reports were detailed Written complaints, screenshots, and report history show the issue was reported with detail and evidence, not casually flagged once.
The public posts kept coming Screenshots show more posts and comments after reports had already been made, keeping the same harassment attacks visible.
Years of reporting, still nothing done The record shows reporting back to 2021, detailed follow-up material, and repeated non-resolution while the posts kept spreading.
The smears got absurd The narrative escalated into dramatic claims and false framing, including a “breaking news” style card used to make the story look bigger than the proof.
He turned it into a movement The posts stopped looking like normal criticism and started looking like a repeated public campaign around Soul and Legion Killfeed.
The smears kept mutating When one angle did not land, the narrative kept changing while the target stayed the same.
Meta left the harassment standing The appeal record argues that response handling punished the victim while the harassment and defamatory material remained online.
The posts were everywhere The same material appeared across different posts, screenshots, and surfaces instead of staying in one contained harassment thread.
Soul mentioned the heart surgery Soul tried to calm the situation by appealing to basic compassion over a real medical issue, and the response escalated anyway.
An hour later, Joel posted shit A private throwaway comment was lifted out of context and pushed publicly to make the issue look worse.
Soul told his fiancee himself The card shows there was no hidden relationship issue; Soul had already communicated openly with his partner.
Joel starts the framing Private screenshots show participation and encouragement in the exchange, not distance from the later public framing.
Soul challenged the manipulation publicly Soul pushed back because Joel kept him blocked while continuing to split vague, one-sided public posts.
What the full context actually shows The full context shows Soul made the throwaway reply while defending Joel Walker's ex, and the cropped screenshot omitted Joel making the identical comment about Soul ten messages earlier.

Reddit denial - Oops, I dropped the proof again...

The "Oops, I dropped evidence again" parody of "Oops, I did it again"

The phrase they - wish - i . died . space uses their words. Soul turned it into a documented timeline.

Selected evidence image

Soul fights for the community - without clout chasing!

Soul publicly reported an undeletable DayZ console server.log growing to 2.44 GB, shared CPU and RAM measurements, and gave Bohemia Interactive enough detail to act on. After the change was added, Bohemia came back to Soul for live testing on a real console server. Soul posted the follow-up results publicly: average CPU dropped from 64.34% to 38.96%, and RAM usage dropped by about 223 MB.

Soul's detection of the bloated logfile issue should not be undersold, to be completely clear, Soul improved all DayZ servers by 40% across all devices.

He also posted a console admin-tooling proposal asking for restricted init.c access or an official API/RCON-style alternative for announcements, messages, kicks, bans, teleport help, and faster exploit response. Those suggestions were specific admin tools based on the limits console owners deal with every day.

The RPT spam report broke down roughly 77 MB and more than 1.08 million lines across about five hours, showing how unreadable logs hurt moderation and support.

Read more about Legion Killfeed's features

Site search

Find pages, tools, and guides

Copyright

© 2022-2025 Legion Killfeed. All Rights Reserved.

This website and its content, including but not limited to text, graphics, images, logos, icons, and software, are the property of Legion Killfeed and are protected by Australian and international copyright laws.

Rights Reserved: No part of this website may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the copyright owner, except in the case of brief quotations embodied in legitimate critical reviews and certain other non-commercial uses permitted by copyright law.

Disclaimer: All trademarks, logos, and service marks displayed on this site are the property of their respective owners. Use of these marks does not imply any affiliation with or endorsement by them.

Australian Copyright Law: This copyright notice is governed by the laws of Australia. Unauthorized use of this material is strictly prohibited and may result in civil and criminal penalties.

Open legal page