How Friends Take Our Game Apart (and Why We Ask Them To)

We don't have a QA team. We have something better: friends who are honest.

Bastian and the first hour. Bastian took the game on seriously — and died. Again and again, before the fun even started. Three reports came in a row: "I keep starving — and I can't even find seeds!" (The starter kit had no food, and the game never explained that you eat berries, not seeds.) "The robot shoots through the wall — and all I have is a machete!" (Enemies chased players through solid rock, and the melee machete was shorter than the enemy's bite.) And: "On Linux it feels nailed to 30 fps." An entire release afterwards revolved around nothing but the first minutes: starting rations, a scrap pistol to defend yourself, line-of-sight requirements for all enemies, a VSync toggle. Bastian's reports practically wrote that changelog themselves.

Severin and the seven findings. Later Severin tested — and found a different kind of problem: the quiet ones. There was no pause menu on Esc. Settings only took effect after a restart. The oxygen display didn't reveal that you can breathe on this world. Iron was there, but nobody thought to dig down. Seven items, all fixed, and Severin is now in the credits — like everyone who helps us this way.

The pattern behind it: Developers test what they built. Friends test what's there. I can no longer experience the first hour of play without bias — after all, I know where the iron is. A friend doesn't. That's exactly why his failure is more valuable than my success.

If you're testing the game and get stuck somewhere: press F1 and write. You're not doing us a favor — you're making the game.