Small Kings, Big Ban Hammers: Why Indie Gaming’s Discord Fiefdoms Keep Imploding

If you want to witness the absolute peak of human delusion, don’t look to Wall Street or Washington. Look at an indie game development Discord server where someone running a two-person studio with an unreleased pixel RPG gets handed administrator perms.
Suddenly, you’re not talking to a stressed freelancer trying to fix collision code. You’re talking to a digital Sun King.
The modern indie scene loves to sell a cozy, democratic fantasy. We’re all scrappy underdogs standing shoulder-to-shoulder against EA and Ubisoft, right? We’re all wholesome artists fighting the AI apocalypse together. But step behind the curtain into the industry’s actual networking hubs, and the vibe turns from Stardew Valley to Lord of the Flies faster than you can type /ban.
The dirtiest open secret in indie gaming is that the entire ecosystem is being held hostage by Discord mods who confuse administrative access with absolute divine right.

The Fiefdom Formula

The setup is always identical, and it always rots the same way.
An industry server pops up. Maybe it’s an indie dev festival hub, a game jam community, or a local network meant for voice actors, composers, and coders to land gigs. Because setting up a Discord is free and community labor is cheap, the organizer hands mod roles to their creator buddies: the local studio lead, the webcomic author, the freelance artist who spends 18 hours a day online.
At that exact moment, professional infrastructure dies. A petty fiefdom is born.
The conflict of interest is staggering. In no other functioning industry on Earth does the CEO of Company A get to unilaterally kick a contractor out of the entire city’s trade floor just because the contractor quit to take another job. But in indie dev land? If a developer, voice actor, or tech specialist decides they’re done working for a studio lead, that studio lead doesn’t send an email saying, “Best of luck with your future endeavors.”
They throw a fit in private chats, manufacture an excuse, and click the ban button across three different mutual servers before lunch.
This isn’t just an abstract theory; it is a recurring nightmare for indie creators who don’t have the platform to fight back. I know this firsthand because it happened to me. During a high-stakes game jam, I fell backward into the teeth of this exact power dynamic. Over nothing more than minor creative differences, the game jam owner—who also ran the entire community server—decided to play god. My game was instantly eliminated from the competition, and the admin wielded their access like a personal weapon, banning and blacklisting me across multiple interconnected spaces. My hard work was instantly vaporized, my momentum was killed, and I was left with no choice but to completely shelve a project I poured my soul into. To keep making games at all, I had to retreat entirely into the shadows, going dark and rejoining the scene under a completely different name just to build in peace.
When administrators act as gatekeepers, an independent creator’s entire career can be derailed in a single click. Seeing this exact same pattern of abuse happen to someone else didn’t just frustrate me—it completely pissed me off. It brought back the reality of how fast these insular cliques will ruin someone’s livelihood just to protect a bruised ego.
[ Routine Career Move / Creative Input ]
│
▼
[ Studio Head’s Ego Bruised ]
│
▼
[ Cry “Harassment / Doxxing” ] ──► Weaponize Server Perms ──► Nuclear Deplatforming
│
▼
[ Silence & Scrub Timelines ]

????️ Editorial Note from the Author: Why These Receipts Exist

Before detailing the specifics of the recent fallout, let it be explicitly clear: The developer targeted in the following case study has absolutely nothing to do with the writing or publication of this article. When this public meltdown detonated across X.com, multiple horrified peers in the indie community—including myself—watched the toxicity unfold in real-time. Knowing the standard playbook of these moderation fiefdoms, independent observers immediately captured full, unedited screenshots of the public timeline before the studio leads could hit delete. The receipts below were preserved by outside third-party creators who refuse to let history be rewritten—not by the victims of the ban. Any attempt by the studio to retaliate against the affected developer over this article only proves their utter desperation to deflect from the crowd that witnessed them.

The Altabe Blueprint: Banning a Tot Over a Polite Resignation

If you think the game jam abuse I faced is an exaggeration, look at the disaster that recently detonated out of Altabe Studio.
The case is practically a clinical study in moderation derangement. Seasoned developer, cybersecurity expert, and voice actress Erin LaVaux—better known by her streaming handle Amorlea, who runs two separate software firms including her own independent indie outfit, Tawaci™ Media—decided to step away from the studio’s production, Cante Diary. She and her tot submitted a routine, polite resignation, wished the team good luck on their future roadmap, and closed the door professionally.
For normal adults, that is the end of the transaction. For Altabe Studio’s leadership, it was apparently an act of high treason.
Instead of accepting a clean departure, Altabe owners Mayshing and Cinnamonro weaponized their massive administrative footprint. These two individuals didn’t just run their own studio; they held moderator status across three major industry Discord servers, a game festival board, and a prominent community subreddit. They built an absolute monopoly over the local community’s infrastructure.
When the resignation dropped, they didn’t just coordinate a standard ban—they used their backchannel whisper networks to spread unverified, toxic rumors and actually went out of their way to ban the tot.
The rest of us in the community watched on in absolute horror as this unfolded. We stood by silently, witnessing an incredibly cool, respected developer and her kid get completely deplatformed and falsely accused by people they had worked with for years. Turning administrative weapons on a tot because you can’t handle an adult’s polite resignation crosses straight into self-parodying villainy. It laid bare the exact rot at the heart of these setups: when you give studio leads unchecked moderation power across every hub in the scene, their fragile ego becomes the ecosystem’s law.

The Anatomy of the Coward’s Purge

What makes these backchannel purges so uniquely pathetic isn’t just the abuse of power—it’s the sheer cowardice of the playbook:
• The Phantom Threat: The moment someone dares to resign or set a boundary, the mod-developer immediately reframes reality. A polite resignation letter becomes an “existential safety threat.” Sharing a text message you typed yourself gets branded as “malicious doxxing.” Suddenly, the contractor who built your website is cast as the leader of a shadowy cabal coming to burn down your server.
• The Collateral Punishments: When insecure bullies get emotional, they don’t stop at their target. They ban friends, mutuals, and actual tots just to feed a petty grudge.
• The Serial Pattern (The Staff Page Question Marks): This behavior is rarely a one-time mistake; it’s a habit. If you look closely at Altabe Studio’s public website, the staff and contributor pages are filled with glaring red flags—numerous past talents and creators have their names scrubbed, altered, or replaced with strange, unexplained question marks. It leaves any outside observer wondering just how many times these studio leads have run this exact same burn-and-ban playbook on other creators who didn’t have the receipts to fight back.
• The Timeline Whitewash: The second their public tantrum ends and reality sets in, the panic begins. Realizing their public meltdown looks completely unhinged to normal human beings, Mayshing frantically scrubbed her X.com timeline, deleting thousands of direct messages and erasing almost all her public posts before fleeing to Bluesky to slap a “clean, professional, wholesome” coat of paint over a new profile.
• The Ghost Town Effect: Meanwhile, the rest of the server watches in dead silence. Do dozens of developers know the ban was a toxic vendetta? Absolutely. Will anyone say a single word in general chat? Not a chance. When your next gig or festival placement depends on access to the servers that Mayshing and Cinnamonro control, self-preservation beats solidarity every single time. Everyone keeps their heads down and prays the ban hammer doesn’t swing their way next.

Avatars Won’t Save You From the Logs

The most hilarious part of this dynamic is the contrast in how these people present themselves.
On one side, you have creators hiding behind layers of digital insulation—elaborate VTuber rigs, high-fantasy personas, and quirky anime pseudonyms where they roleplay as untouchable goddesses or mythical tricksters. It’s an engineered aesthetic designed to project effortless superiority while shielding the fragile ego underneath.
On the other side, you have the people they try to cancel: actual professionals who use their real names, show their real faces, bring real industry credentials to the table, and—most dangerously for the gatekeeper—keep pristine server logs.
Because that is the ultimate kryptonite to an insecure Discord tyrant: receipts.
A studio lead can throw buzzwords around, shout about “Erin and her associates,” whisper poison in private mod channels, and scrub their timeline until it shines. But they cannot outrun a cold, unedited screenshot of their own behavior. The second unassailable chat logs hit the public timeline, the mythical avatar shatters, the “goddess” looks like a petulant middle-manager throwing a tantrum, and the entire high-and-mighty act collapses into pure internet embarrassment.

Drop the Hammer or Kill the Scene

Indie development desperately needs to grow up and ditch the high school lunch table mentality.

If a Discord server claims to be an open industry networking space, an indie festival hub, or a professional creative exchange, active studio owners cannot hold the keys. Full stop. You do not let people with financial and creative skin in the game act as judge, jury, and bouncer for their own peers.
Until organizers pull the ban hammer out of the hands of insecure studio leads, these platforms aren’t networking spaces. They’re just personal playgrounds where insecure creators play dress-up as royalty—right up until someone shows up with the logs and reminds everyone who’s actually holding the cards.