Ever found yourself grinding through a game and wondering about the human cost behind it? Wardogs, the early access multiplayer FPS that's been blowing up, is now in the spotlight for a different reason entirely. Bulkhead CEO Joe Brammer sat down with The Game Business and openly backed crunch—both as a general practice and specifically during Wardogs' development.
Crunch, for those lucky enough to avoid it, is the industry term for mandatory overtime, often unpaid, that devs endure to hit deadlines. It's been a hot-button issue for years, linked to burnout and high turnover. Brammer's comments didn't just raise eyebrows; they lit a fire under a community that's already passionate about the game.
Wardogs has enjoyed a booming early access launch, with players flocking to its tactical multiplayer action. But this controversy threatens to overshadow that success. Fans who've been singing the game's praises are now questioning the ethics behind its creation. It's a classic case of loving the art but side-eyeing the artist.
Brammer went on the defensive after the interview, but the damage may already be done. In an era where players increasingly care about how games are made—not just how they play—comments like these can tarnish a reputation fast. The gaming public has a long memory, and social media is unforgiving.
So what does this mean for Wardogs? The game itself isn't going anywhere; it's still in active development and has a dedicated player base. But the conversation has shifted from "this game is fun" to "should I feel good about playing it?" That's a tough spot for any studio.
For Bulkhead, the next steps matter. Will they double down, issue a mea culpa, or let the controversy fade? Brammer's stance has already alienated some potential fans, and in the crowded FPS market, goodwill is currency. The studio might need to do some serious PR repair to win back trust.
What's your take on crunch in game development? Does it change how you feel about Wardogs? Let us know in the comments.
Comments (0)
Log in to join the discussion
Log InNo comments yet