Notable Staff Cases

Archive ID: No ID
Category: General
Date: Unknown

Notable Staff Cases

📚 Historical Record: These cases document important server history and explain current security measures.

🚫 The Anchoraura Blacklist Case

Overview

  • Position: Co-Founder (highest rank below Joey)
  • Active During: Season 3 only
  • Blacklist Vote: 7-0 unanimous decision
  • Status: Permanently blacklisted, zero chance of appeal

Major Violations

  1. Racist Behavior:
    • Used Hindi-language slurs in ticket channel
    • Posted extremely offensive messages including n-word
    • Targeted staff member Stormgaming
  2. DDoS Threats:
    • Threatened server attacks after demotion
    • Claimed to use friend's DDoS tools
    • April 16, 2025: Demanded 500 rupees to stop threats
    • Server may have been DDoSed after his removal
  3. Power Abuse:
    • Tried to get Stormgaming demoted unfairly
    • Called Joey "jobless" despite being 15 years old
    • Demanded 40+ apologies from staff

The Ticketv2-1 Incident

Started when Joey created a test ticket. Stormgaming responded seriously by mistake. Anchoraura insulted his English, leading to an escalation where Anchoraura sent two extremely racist messages. Results:

  • Stormgaming: 1 strike
  • Anchoraura: 2 strikes

Impact on Server

His case led to the current strict security measures and influenced the role structure. He created roles like Co-Founder and Regulator before his removal.

💻 The NotMukundOp Griefing Cases

The Developer Who Griefed Twice

  • Position: Developer
  • Hired by: ItzEpiales (passed dev test)
  • Notable for: Being hired TWICE despite griefing

First Incident

  1. Android allegedly pranked him using Joey's name
  2. Called him "the worst developer"
  3. NotMukundOp griefed both Discord and Minecraft servers
  4. No security bots existed at the time
  5. Minecraft restored from backup, Discord severely damaged
  6. Server temporarily moved to Android's Discord

Second Incident

  • Rehired AGAIN by ItzEpiales
  • Hyper suggested using Xenon bot for backups
  • When he griefed again, damage was minimal due to precautions

🔧 The Bcolbyb RandomTickSpeed Disaster

The Manager Who Crashed Everything

  • Position: Manager
  • What happened: Set RandomTickSpeed to 999,999,999
  • Reason: Wanted his sugarcane to grow faster
  • Result: Server down for almost 2 full days

Aftermath

  • Apex Hosting had to assist through support tickets
  • Not fully blacklisted, but demoted to lower position
  • Key admin commands disabled via LuckPerms
  • Given second chance under tight controls

Legacy: One of the most infamous technical mistakes in JosephSMP history

🎮 The Android Discord Ownership Saga

Background

After NotMukundOp's first grief, the server moved to Android's Discord since he owned it. This created major issues:

Problems During His Ownership

  • Abused powers frequently
  • Once stopped server for 15 minutes because his base got raided
  • Punished everyone instead of just the raiders
  • Couldn't be demoted due to Discord ownership

Resolution

  • Joey waited until gaining Discord ownership
  • Android received 3 strikes for various actions
  • Once Joey had ownership, Android was demoted
  • Update: Android was rehired April 11, 2025 (hours before Season 4)
  • Final Update: Android resigned June 2025

⚠️ The Exo 15-Strike Points Case

Details

  • Date of Offense: April 16, 2025
  • What happened: Used F and S words in staff chat
  • Investigation opened: May 1, 2025 by ItzEpiales
  • Result: 15 strike points issued
  • Current status: Still Assistant Staff Manager (needs 30 SP for demotion)

💡 Lessons Learned

These incidents led to:
  • Implementation of strict security bots
  • Regular server backups
  • Strike point system for staff accountability
  • Careful vetting of staff permissions
  • Zero tolerance for discrimination and threats
Back to Archives