Skip to content

Instantly share code, notes, and snippets.

@TejasLamba2006
Last active May 5, 2024 17:50
Show Gist options
  • Save TejasLamba2006/6d424dab08cc7ecc518bd20b04254a51 to your computer and use it in GitHub Desktop.
Save TejasLamba2006/6d424dab08cc7ecc518bd20b04254a51 to your computer and use it in GitHub Desktop.

CraftCord's Revelations on Pika Analytics & Pikachu's Stats


Date: 5 May, 2024

To Whom It May Concern:

CraftCord has undertaken a thorough investigation into the practices of Pika Analytics(1223541991187419201) and Pikachu's Stats(1112768481956479108), and the findings are deeply concerning.

Uncovering the Truth:

CraftCord's investigation has uncovered a multitude of unethical behaviors and abuses perpetrated by Pika Analytics and Pikachu's Stats. These include:

  1. Data Manipulation: Pika Analytics and Pikachu's Stats have been caught manipulating data to deceive their clients and the public.

  2. Toxic Work Environment: Reports of a toxic work environment within both organizations have surfaced, including instances of harassment and discrimination.

  3. False Claims: Pika Analytics and Pikachu's Stats have made false claims about their services and capabilities, misleading their clients and stakeholders.

  4. Breach of Privacy: There have been instances of Pika Analytics and Pikachu's Stats breaching privacy regulations and exploiting user data for their own gain.

Taking a Stand:

CraftCord condemns these reprehensible actions and stands in solidarity with those affected. We refuse to turn a blind eye to such blatant disregard for ethics and integrity.

Call to Action:

We urge individuals and organizations to reconsider their associations with Pika Analytics and Pikachu's Stats. It is imperative to hold them accountable for their actions and demand transparency and accountability in all dealings.

discord-term-1

Conclusion:

CraftCord remains committed to exposing wrongdoing and advocating for a fair and just industry. We will continue to shine a light on unethical practices and support those who have been wronged.


background information

Characters

  • kebal, forti123__ (911972249194614814), InfernoBlzDEV, InfernoBlz (799160175079850004), v3n0m_m1x (1090190986178744350) (Yea all of them are his alts, 2 of them got terminated as we reported them to discord as he was underage.)
  • deyo.exe (773986611079806986)
  • fireor (943788869604741121)
  • progamerzyt (721922737953570836)
  • sti1ltyping (840587974000771072)

How it started?

On a fine evening (15th April, 2024), I received a direct message from Kebal with an image. Initially, I disregarded him as he had betrayed our organization by joining competitors. After he sent his first message with the image, he followed up with a second message containing only a question mark. My curiosity piqued, I tapped on the notification (yes, I was on mobile at the time). He had sent me a screenshot of his email, with messages reading "Tejas wtf" and "legit". Let me share the screenshot: kebal-dms-1. Let's zoom in on the image he sent: kebal-dms-email. The email was from craftioverlay@gmail.com, directly related to my future project, Crafti Overlay, which I was about to release. My theory is that they took advantage of me not claiming the email and did this themselves. While anything is possible, this is just my theory.

Later that night, on the same day, I was banned by Pika Network for doxxing: tejasispro-ban-onday. Let's all assume I doxxed him. This incident didn't occur on Pika Network's official Discord server or in the Minecraft server; it was a private matter. Why was Pika Network involved? Let's assume Pika Network can ban people based on DMs. Okay, fine. But I'm not on their Discord server, nor did I link my account with that Discord account. How can they assume my IGN is TejasIsPro? Furthermore, if that rule exists, their staff is unaware of it: unglue-dms. It's weird, right? Despite making two appeals with all the evidence, they were denied. I gave up and started to investigate, uncovering the following information. Enjoy, guys.

Evidence

Toxic Work Environment, False Claims and Data Manipulation

Under the umbrella of toxicity and false accusations, the narrative of data manipulation unfolds. They persistently doxxed themselves and unjustly pointed fingers at us.

fireor-doxxed-them-1 foreor-doxxed-them-2 It's noteworthy that despite their uncertainty, they continued to shift blame. How are we expected to access a private server? They're clearly amateurs.

fireor-doxxed-them-3 Here, Kebal (Venom Dev) threatens legal action 💀 against us.

fireor-doxxed-them-4 He claims to possess evidence against us, even hinting at threats to our lives. Absurd! He also criticizes our code, despite his own incompetence.

kebal-being-dumb fireor-doxxed-them-5 Kebal's folly reaches its peak when he mentions, "dude you use VPN, I told you it's not safe." Clearly, he misunderstands the purpose of VPNs.

fireor-doxxed-them-6

Now, shifting focus to Pro AI's IQ, he delusionally believes we gained access to his bot's code or Discord account. How laughable! Perhaps he's running token or Nitro generators, revealing his lack of intelligence.

pro-ai-false-claims-1 He falsely claims I reside in Mumbai, despite evidence on my LinkedIn stating otherwise.

tejas-so-smart Their theory crumbles when confronted with factual information.

pro-ai-false-claims-2 pro-ai-false-claims-3 Upon realizing their error after viewing my LinkedIn profile.

pro-ai-false-claims-4 Any alleged proofs are null and void, as they were baseless to begin with.

pro-ai-false-claims-5 pro-ai-false-claims-6 pro-ai-false-claims-7 pro-ai-false-claims-8 pro-ai-false-claims-9 pro-ai-false-claims-10 pro-ai-false-claims-11 pro-ai-false-claims-12 pro-ai-false-claims-13 pro-ai-false-claims-14

Turning attention to Fireor, evidence suggests his involvement in the doxxing.

fireor-doxxed-random-1

Later, they redirected these doxxing accusations towards Forgiobombi, a fellow CraftCord developer.

kebal-acting-dumb-again-1

Additionally, kebal entered our server and launched verbal attacks at us while we were addressing technical issues with Discord and re-verifying our bots.

kebal-acting-dumb-again-2 kebal-acting-dumb-again-3

Yes, our bots were reverified.

Breach of Privacy

Their scheme involved direct messaging guild owners or administrators of prominent servers with our bot, falsely accusing us of nuking their server, supported by fabricated evidence. They even resorted to using their own bot to expel ours, showcasing their incompetence and disregard for server privacy.

plan-to-nuke-servers-1 plan-to-nuke-servers-2 plan-to-nuke-servers-3 plan-to-nuke-servers-4 plan-to-nuke-servers-5 plan-to-nuke-servers-6 plan-to-nuke-servers-7 plan-to-nuke-servers-8

Note After Reading Everything

After carefully reviewing this GIST, we extend an invitation for you, the reader, to contemplate the situation and determine whether you wish to entrust your server to individuals who display immaturity and disregard for Discord policies.

@ProAi-0121
Copy link

Lol Okay I don't have time to write a big reply anyways.. congrats for verification and good luck with your bot 🥰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment