A Complaint That Wouldn’t Go Away

The neckless look was never a bug so much as a stylistic shortcut, and for a while it was easy to wave off as a quirk. The trouble is that players did not see charm — they saw heads bolted straight onto shoulders, and they said so, loudly and often. When the same gripe shows up review after review, it stops being noise and starts being a signal.

Newman’s response was refreshingly blunt: rather than defend the design, he conceded the crowd was right and gave the characters necks. For a developer with nothing left to prove, choosing the humble fix over the stubborn stance is a small masterclass in not falling in love with your own decisions.

Why the Fix Matters More Than the Necks

On its own, a neck is a rounding error in a game’s feature list. What makes this worth writing about is the posture behind it. Newman treats blunt, even harsh, user feedback as raw material rather than an attack, and that mindset is the reason his studio has survived where flashier outfits have folded.

Entrepreneurs and product builders should recognise the pattern. Negative reviews are the cheapest market research you will ever get, and the recurring complaints are a roadmap in disguise. Facepunch’s willingness to read the one-star pile and act on it — quickly, publicly, without ego — is exactly the discipline most teams claim to have and quietly avoid.

The Facepunch Way of Building in Public

This is nothing new for a studio that has built its reputation on developing in the open. Rust spent years in early access being reshaped by its community, and Newman’s current work continues that habit of shipping, listening, and iterating rather than polishing in secret and hoping for the best. It is the same spirit you see in the best early access overhauls that tear out what isn’t working and rebuild it.

That approach carries risk — building in public means your mistakes are public too — but it also builds a loyal audience that feels heard. From indie studios taking on genre giants to solo developers polishing passion projects, the winners increasingly treat their players as collaborators. The neck saga is a small, funny reminder that even a veteran with a legacy like Newman’s still wins by staying humble enough to change his mind.

Related on BizzNerd

• Menace’s Big Early Access Overhaul Killed Its Most Hated System
• Paralives Hands-On — The Indie Sim Putting EA on Notice
• Dodo Duckie Is the Indie Puzzle Platformer You Didn’t Know You Needed

The Bigger Picture

Garry Newman gave his characters necks because the people playing his games would not let it go, and he was smart enough to treat that persistence as a gift. The change itself is trivial; the instinct behind it is not. In a market crowded with studios that argue with their audiences, the developer who reads the bad reviews, laughs at himself, and quietly fixes the thing everyone hates is the one still standing years later. Sometimes the most valuable feature you can ship is the willingness to admit the critics had a point.

The post Garry Newman Finally Gives His Game Characters Necks appeared first on Bizznerd.