PirateSoftware loses 90% of his audience after World of Warcraft Hardcore disaster and refusal to accept blame

It was when 2 teammates died and the frost mage had mana gems but no apologies.

Streamer chatting while browsing Firefox on desktop.
(Image via AnythingElse on Kick)
TL;DR
  • PirateSoftware's average Twitch viewership dropped from 20,000+ to 2,000–3,000 following a WoW Hardcore incident where he left teammates to die and refused to apologize.
  • The frost mage had mana gems and crowd control abilities available but chose to save himself, then defended the decision despite video evidence contradicting his claims.
  • Follow-up controversies including his "Stop Killing Games" critique and various development disputes kept the audience decline going for months before stabilizing at the lower level.
Community Reactions
How do you feel about this story?
👍
1
👎
0
😂
0
😡
0
😢
0

PirateSoftware has seen his Twitch viewership collapse from peaks above 20,000 to a current average of 2,000–3,000 viewers. The months-long decline started with a World of Warcraft Classic Hardcore incident in early 2024 and accelerated through subsequent controversies.

The game dev streamer, known for coding tutorials and industry advice content, was playing WoW Hardcore when the initial incident occurred. In Hardcore mode, character death is permanent. During a Dire Maul dungeon run, a pull went wrong and two of his teammates died.

PirateSoftware was playing a frost mage. Viewers immediately spotted that he had tools available to help his team escape—Frost Nova to freeze enemies, Blizzard to slow them, and mana gems he could have used for additional casts. Instead, he left the dungeon to save his own character while his teammates’ characters were permanently deleted.

The real damage came afterward. Rather than admitting he panicked or made a mistake, he defended his actions across multiple streams. He claimed he was completely out of mana, but viewers pulled clips from his own VOD showing he still had resources available. The group removed him after the run.

TwitchTracker data shows the decline hit hard. His average concurrent viewership dropped from regular 10,000–20,000 viewer streams to current levels around 2,000–3,000. During the peak of the drama, he was reportedly losing roughly 1,000 followers per day.

The WoW incident might have blown over, but follow-up controversies kept the audience bleeding. In mid-2024, an older video where he criticized the “Stop Killing Games” consumer rights initiative resurfaced. Critics argued he misrepresented the campaign’s goals, reigniting scrutiny of his content.

Additional disputes followed. He had public arguments with other developers including one with a creator called CodingJesus. Clips circulated questioning whether his “blind” puzzle playthroughs were actually blind. Some criticized the code quality of his in-development game Heartbound. Various other allegations about his streaming practices made rounds in developer communities.

The metrics tell a clear story. Last month saw a 26% drop in average viewers compared to the previous month. This month the decline slowed to 4%. The drop appears to be stabilizing, but at a fraction of his former audience size.

The current situation represents an unusual case. Most streamer drama results in temporary dips followed by recovery. This decline has persisted for months, suggesting deeper audience trust issues rather than typical controversy cycles.

Explore More
Meet the Editor
mm
Head of Spilled