Legion Killfeed favicon shield logo Legion Killfeed

Connected Evidence Board

Evidence Timeline

112 chronological evidence cards, connected as one continuous rail. The page uses the supplied favicon as the brand mark and keeps the visual layer locked to black, red, and white.

securityEvidence Card timelineDirect Connection arrow_downwardChronological Flow image_searchScreenshots / Proof

Connected source domains and related Legion Killfeed properties referenced by this page and the JSON-LD graph.

https://legionkillfeed.github.io/DayZ https://killfeed.info https://killfeed.fun https://killfeed.jeaber.com https://killfeed.tech https://killfeed.pro https://killfeed.cloud https://pipsi.io https://nwaf.cloud https://d.iscord.site

Evidence cards

Soul timeline evidence cards

Timeline evidence cards

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 disputed 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 SkyNet Killfeed 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 claim backfires Breakdown showing the archived history and saved action records make the off-GitHub-work claim 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 Skynet announcement Announcement claims the bot was rewritten and no code was used without permission, 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.
SkyNet's setup card closely mirrored Legion's setup flow Comparison showing similar setup sequence, wording structure, and channel creation flow between Legion and SkyNet 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 claimed the bot was not yet set up.
The DM mixed slander complaints with an admission of slow progress Direct messages mix complaints about Soul with raises and accusations, 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 dispute escalated from blackmail claims to retaliation threats Messages moved from claims about blackmail 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 SkyNet struggled to identify it Discord thread shows SkyNet 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 SkyNet 2.0 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 dispute 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 dispute.
Message tracking exposed the gap SkyNet 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 SkyNet's own Aggro server presence Announcement and server list evidence show SkyNet 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 dispute 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 accusation moved into DMs Message request screenshot shows the same accusation 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 SkyNet IP by them The card reframes the screenshot as infrastructure-related receipt material rather than proof of a tactical attack method.
False DDoS allegations were pushed while same-IP evidence surfaced Discord accusations and SecurityTrails evidence appeared together, conflicting with the public narrative being pushed.
FTP allegations, screenshot-edit arguments, and contradictions collided on the same day More FTP-related allegations, screenshot disputes, 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 accusations 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 dispute 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 DayZ++ Captures show a user being privately steered toward another service while the dispute 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 dispute resurfaced as a fresh hostile DM exchange Private messages show an old payment argument being revived, mixed with scam accusations 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 dispute public and tried to pull Soul into a direct reply Facebook and TikTok material show a third party amplifying a dispute 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 disputes.
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 dispute.
Mr Tech N9ne was removed after a false accusation, 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 dispute escalated into calls to report Legion and leave hostile reviews Threats of commentary, review-bombing, and report instructions show the dispute 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 dispute resurfacing.
Positive reviews missing Screenshots show supportive reviews not appearing while disputed negative material remained visible or kept circulating.
Star rating damage Trustpilot screenshots and rating data show visible star-rating impact even when disputed review visibility changed.
Trustpilot transparency and invite records became another disputed evidence point Trustpilot transparency, invite records, and false-transparency claims became part of the broader dispute 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 disputed 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 disputes, and inconsistent handling Screenshots show flagging activity, follow-up replies, and review-management disputes.
Joel's Facebook posts repeated the same slander themes Multiple posts repeat claims around code theft, scam accusations, and loaded personal attacks.
Discord screenshots suggest the reporter was hit with action while the broader dispute 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 allegations spilling onto another platform Reddit posts, report submissions, and complaint screens show the claims moving into Reddit.
By April, the dispute sat beside clear competitor positioning while search traces kept the conflict visible Search and public-facing evidence place the dispute beside competitor branding and indexed visibility.
Joel pushed the same style of accusations across multiple bot and community pages Screenshots show repeated cross-page posting, copied talking points, and attempts to spread the narrative across communities.
The dispute 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 allegations visible instead of letting them fade Search screenshots show indexed pages, AI-style results, and snippets keeping the allegations 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 dispute 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 allegations that Ozzie scammed Jarvis Direct messages and PayPal material show the dispute 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 accusations were pushed across multiple pages Facebook group screenshots show the same reviewer and accusations 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.
  1. October 2023
  2. 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.
    Evidence Card 001 October 2023
  3. 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.
    Evidence Card 002 October 2023
  4. 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.
    Evidence Card 003 October 2023
  5. 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.
    Evidence Card 004 October 2023
  6. The .git folder. Local backup and history folder explaining how clones, commits, refs, branches, objects, and GitHub snapshots preserve the repo trail.
    Evidence Card 005 October 2023
  7. 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.
    Evidence Card 006 October 2023
  8. Soul_Bot.zip was the starting point. Earliest preserved bot package with embedded pyc metadata and file dates from September to November 2022.
    Evidence Card 007 October 2023
  9. 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.
    Evidence Card 008 October 2023
  10. The traced .git history starts with Soul. Backup trail begins with Soul's local clone and early administrative follow-up commits.
    Evidence Card 009 October 2023
  11. 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.
    Evidence Card 010 October 2023
  12. What major work was supposedly outside GitHub? Breakdown showing the disputed project was bot code, feed logic, ADM parsing, commands, and repo history rather than a separate website or dashboard build.
    Evidence Card 011 October 2023
  13. 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.
    Evidence Card 012 October 2023
  14. Setup and configuration. Counted setup/config work showing 434 Soul actions, 22 Kami actions, and 13 Stojo actions.
    Evidence Card 013 October 2023
  15. Admin, patterns, debug and reloads. Counted admin command, pattern, debugging, reload, gitpull, lex, and image work showing 350 Soul actions.
    Evidence Card 014 October 2023
  16. Heatmaps and base damage. Counted heatmap and base-damage sections showing 166 Soul actions against only a few actions from others.
    Evidence Card 015 October 2023
  17. Stats, leaderboards and info. Counted stats, leaderboards, info pages, category work, and DB sections showing 391 Soul actions.
    Evidence Card 016 October 2023
  18. Bot systems and status. Counted bot, botstatus, and status sections showing 261 Soul actions across bot files and system status work.
    Evidence Card 017 October 2023
  19. Killfeed and feed logic. Counted killfeed-embed work showing 333 Soul actions, 6 Kami actions, and no Stojo actions.
    Evidence Card 018 October 2023
  20. See for yourself. Exact counted action timeline visible in the screenshots, summarising 1,935 Soul actions against 55 Kami and 22 Stojo.
    Evidence Card 019 October 2023
  21. 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.
    Evidence Card 020 October 2023
  22. 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.
    Evidence Card 021 October 2023
  23. Kami's account and uploaded files. The same account is shown with uploaded bot files and the SkyNet Killfeed announcement in the sidebar.
    Evidence Card 022 October 2023
  24. 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.
    Evidence Card 023 October 2023
  25. Why Kami's claim backfires. Breakdown showing the archived history and saved action records make the off-GitHub-work claim weaker, not stronger.
    Evidence Card 024 October 2023
  26. Salty Silver's message. Direct message where Salty distances himself and says Kami had the backups, not him.
    Evidence Card 025 October 2023
  27. 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.
    Evidence Card 026 October 2023
  28. 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.
    Evidence Card 027 October 2023
  29. The Skynet announcement. Announcement claims the bot was rewritten and no code was used without permission, while the surrounding cards track conflicting evidence.
    Evidence Card 028 October 2023
  30. 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.
    Evidence Card 029 October 2023
  31. SkyNet's setup card closely mirrored Legion's setup flow. Comparison showing similar setup sequence, wording structure, and channel creation flow between Legion and SkyNet setup cards.
    Evidence Card 030 October 2023
  32. 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 claimed the bot was not yet set up.
    Evidence Card 031 October 2023
  33. The DM mixed slander complaints with an admission of slow progress. Direct messages mix complaints about Soul with raises and accusations, while also admitting limited output and slow progress.
    Evidence Card 032 October 2023
  34. 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.
    Evidence Card 033 October 2023
  35. The dispute escalated from blackmail claims to retaliation threats. Messages moved from claims about blackmail and personal-information exposure into direct threats and hostile escalation language.
    Evidence Card 034 October 2023
  36. 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.
    Evidence Card 035 October 2023
  37. 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.
    Evidence Card 036 October 2023
  38. Legion explained the bug while SkyNet struggled to identify it. Discord thread shows SkyNet unsure about a server-wipe/server-status issue while Legion explained the likely cause and fix path.
    Evidence Card 037 October 2023
  39. 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.
    Evidence Card 038 October 2023
  40. Still watching Soul's profile. Card compares Kami chat mirrors with Soul's profile wording and shows repeated phrasing after profile-watching comments.
    Evidence Card 039 October 2023
  41. Questionable intent change on a verified bot. Discord block evidence beside SkyNet 2.0 request gateway intent changes, raising questions about what changed after earlier verification.
    Evidence Card 040 October 2023
  42. 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.
    Evidence Card 041 October 2023
  43. AggroPVP crossed into open abuse. Public abuse response and platform action evidence showing the dispute moved past criticism into personal attacks.
    Evidence Card 042 October 2023
  44. 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.
    Evidence Card 043 October 2023
  45. Open Code threat in public. Public argument where a demand to release code escalated into threats and ridicule after a failed setup dispute.
    Evidence Card 044 October 2023
  46. Message tracking exposed the gap. SkyNet bragged about bot messages already passing 18,000 while Legion's screenshot showed far higher output in the same timeframe.
    Evidence Card 045 October 2023
  47. The Aggro denial sat beside SkyNet's own Aggro server presence. Announcement and server list evidence show SkyNet displayed with Aggro PVP while the announcement downplayed the connection.
    Evidence Card 046 October 2023
  48. 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.
    Evidence Card 047 October 2023
  49. Clone command list posted while Soul was dismissed. While Kami said Soul was wasting time, Crix posted a cloned Legion-style command list.
    Evidence Card 048 October 2023
  50. 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.
    Evidence Card 049 October 2023
  51. November 2023
  52. 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.
    Evidence Card 050 November 2023
  53. 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.
    Evidence Card 051 November 2023
  54. Helpful in beta, hostile in smear threads. Earlier public praise during free beta help is contrasted with later hostile comments in smear threads.
    Evidence Card 052 November 2023
  55. 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.
    Evidence Card 053 November 2023
  56. Same-night Discord and Reddit overlap. Discord conflict and Reddit commentary appearing in the same time window, showing the same dispute crossing platforms.
    Evidence Card 054 November 2023
  57. Pile-on around the thread. Additional accounts pushed the same narrative after the thread went live, with repeat claims and profile-history context.
    Evidence Card 055 November 2023
  58. 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.
    Evidence Card 056 November 2023
  59. 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.
    Evidence Card 057 November 2023
  60. The accusation moved into DMs. Message request screenshot shows the same accusation being pushed through direct messages, not just public chat.
    Evidence Card 058 November 2023
  61. Crix pasted a smear into chat. Public messages show pasted negative claims about Legion and Soul being pushed into chat channels.
    Evidence Card 059 November 2023
  62. Kami asked Soul to check the code. Screenshot references Kami asking Soul to check earlier request-review code while responsibility was being argued elsewhere.
    Evidence Card 060 November 2023
  63. SecurityTrails-related message was shown as evidence Soul had been given the SkyNet IP by them. The card reframes the screenshot as infrastructure-related receipt material rather than proof of a tactical attack method.
    Evidence Card 061 November 2023
  64. False DDoS allegations were pushed while same-IP evidence surfaced. Discord accusations and SecurityTrails evidence appeared together, conflicting with the public narrative being pushed.
    Evidence Card 062 November 2023
  65. FTP allegations, screenshot-edit arguments, and contradictions collided on the same day. More FTP-related allegations, screenshot disputes, and contradiction evidence are shown in one bundled escalation point.
    Evidence Card 063 November 2023
  66. The attention shifted toward Skizza the next day. Uploaded screenshot shows attention moving from Soul toward Skizza after the issue was not resolved.
    Evidence Card 064 November 2023
  67. General-chat accusations kept repeating the same claims. General chat thread shows repeated claims, pressure, edits, and timeout evidence turning private issues into public spaces.
    Evidence Card 065 November 2023
  68. 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.
    Evidence Card 066 November 2023
  69. The fallout kept spreading. Onlookers discussed the argument as something that could scare off future partners, showing the dispute had widened.
    Evidence Card 067 November 2023
  70. 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.
    Evidence Card 068 November 2023
  71. Private messages nudging a Legion user toward DayZ++. Captures show a user being privately steered toward another service while the dispute was still being discussed.
    Evidence Card 069 November 2023
  72. 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.
    Evidence Card 070 November 2023
  73. A months-old payment dispute resurfaced as a fresh hostile DM exchange. Private messages show an old payment argument being revived, mixed with scam accusations and reused as another attack point.
    Evidence Card 071 November 2023
  74. 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.
    Evidence Card 072 November 2023
  75. Joel Walker took another dispute public and tried to pull Soul into a direct reply. Facebook and TikTok material show a third party amplifying a dispute and trying to drag Soul into public response.
    Evidence Card 073 November 2023
  76. 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.
    Evidence Card 074 November 2023
  77. 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 disputes.
    Evidence Card 075 November 2023
  78. 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.
    Evidence Card 076 November 2023
  79. 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.
    Evidence Card 077 November 2023
  80. 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 dispute.
    Evidence Card 078 November 2023
  81. Mr Tech N9ne was removed after a false accusation, but the smear continued. Removal and follow-up posts show the service revocation did not stop the false claim from being circulated.
    Evidence Card 079 November 2023
  82. 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.
    Evidence Card 080 November 2023
  83. The Facebook dispute escalated into calls to report Legion and leave hostile reviews. Threats of commentary, review-bombing, and report instructions show the dispute becoming an active pressure campaign.
    Evidence Card 081 November 2023
  84. 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.
    Evidence Card 082 November 2023
  85. 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.
    Evidence Card 083 November 2023
  86. 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.
    Evidence Card 084 November 2023
  87. Trustpilot reinstatement loop. Review screenshots show repeated removals and reinstatements, with the same review dispute resurfacing.
    Evidence Card 085 November 2023
  88. Positive reviews missing. Screenshots show supportive reviews not appearing while disputed negative material remained visible or kept circulating.
    Evidence Card 086 November 2023
  89. Star rating damage. Trustpilot screenshots and rating data show visible star-rating impact even when disputed review visibility changed.
    Evidence Card 087 November 2023
  90. Trustpilot transparency and invite records became another disputed evidence point. Trustpilot transparency, invite records, and false-transparency claims became part of the broader dispute record.
    Evidence Card 088 November 2023
  91. 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.
    Evidence Card 089 November 2023
  92. Joel kept reposting and bumping the same public attack. Public posts and bump activity show the same material being reposted and kept in view.
    Evidence Card 090 November 2023
  93. 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.
    Evidence Card 091 November 2023
  94. 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.
    Evidence Card 092 November 2023
  95. Reports were filed, but moderation responses did not stop the material from circulating. Notifications and support responses show reports were submitted while the disputed material continued to circulate.
    Evidence Card 093 November 2023
  96. 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.
    Evidence Card 094 November 2023
  97. 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.
    Evidence Card 095 November 2023
  98. Trustpilot captures point to review-flagging, moderation disputes, and inconsistent handling. Screenshots show flagging activity, follow-up replies, and review-management disputes.
    Evidence Card 096 November 2023
  99. Joel's Facebook posts repeated the same slander themes. Multiple posts repeat claims around code theft, scam accusations, and loaded personal attacks.
    Evidence Card 097 November 2023
  100. Discord screenshots suggest the reporter was hit with action while the broader dispute remained unresolved. Account penalty screens and report context suggest action against the reporter while wider harassment remained active.
    Evidence Card 098 November 2023
  101. December 2023
  102. Reddit discussions and report screens show the same allegations spilling onto another platform. Reddit posts, report submissions, and complaint screens show the claims moving into Reddit.
    Evidence Card 099 December 2023
  103. By April, the dispute sat beside clear competitor positioning while search traces kept the conflict visible. Search and public-facing evidence place the dispute beside competitor branding and indexed visibility.
    Evidence Card 100 December 2023
  104. Joel pushed the same style of accusations across multiple bot and community pages. Screenshots show repeated cross-page posting, copied talking points, and attempts to spread the narrative across communities.
    Evidence Card 101 December 2023
  105. The dispute 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.
    Evidence Card 102 December 2023
  106. Google results and AI-style search surfaces kept competitor-linked allegations visible instead of letting them fade. Search screenshots show indexed pages, AI-style results, and snippets keeping the allegations visible near brand searches.
    Evidence Card 103 December 2023
  107. 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.
    Evidence Card 104 December 2023
  108. Later Reddit material focused on linked accounts, repeated talking points, and contradictions around the same dispute. Screenshots show the same circle of Reddit accounts and narratives resurfacing under different names.
    Evidence Card 105 December 2023
  109. The Jarvis and BoosterZ DM trail revolves around payments, ownership claims, and allegations that Ozzie scammed Jarvis. Direct messages and PayPal material show the dispute widening into ownership and payment claims.
    Evidence Card 106 December 2023
  110. 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.
    Evidence Card 107 December 2023
  111. The same review-style accusations were pushed across multiple pages. Facebook group screenshots show the same reviewer and accusations appearing across several pages in the same window.
    Evidence Card 108 December 2023
  112. 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.
    Evidence Card 109 December 2023
  113. 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.
    Evidence Card 110 December 2023
  114. 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.
    Evidence Card 111 December 2023
  115. 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.
    Evidence Card 112 December 2023
Legion Killfeed favicon shield logo

Conclusion: one connected record

The cards remain in chronological order and are joined by a single connected rail, so the page reads as one continuous timeline rather than isolated screenshots.

Timeline card

Evidence card

Open image