I Built a Game With AI. It’s Beautiful, Minimalist, and Completely Forgettable.

I watched a heart beat on my screen. It was supposed to be the center of a resource management game I’d built with an AI coding partner. The pixel art was clean, the loop was simple—keep the heart alive by feeding it what it demands. And it was… boring.

The developer of Vein posted a raw confession on Hacker News: “It works, but it isn’t yet the game I imagined.” That sentence is more valuable than any polished press release. It’s the kind of vulnerability that makes you lean in, because you’ve felt that exact pinch. You’ve built something that functions, yet has no soul.

Vein is an open-source, minimalist resource management game built with Godot. The idea is radical: strip everything down to a single core loop. No upgrades, no branching paths, no narrative. Just a heart that needs resources, and you, the player, deciding what to feed it. The developer worked with Claude Sonnet (an AI) as a coding partner, focusing on design and iteration. The result is a clean, playable proof of concept—and a masterclass in what’s missing.

Here’s the paradox: Minimalism isn’t the absence of complexity—it’s the perfect placement of friction. Vein removes friction so aggressively that there’s almost nothing to push against. The heart beats, you click, it lives. There’s no tension, no consequence, no anticipation. The game is a system that runs, but doesn’t dance.

Think about the games that hook you. Cookie Clicker has the dopamine of numbers growing. Faster Than Light has the constant threat of disaster. Papers, Please has moral friction. The best minimal games don’t just remove—they replace. They take away the noise, but they amplify the signal. Vein hasn’t found its signal yet. The heart beats, but it doesn’t need you. The resources appear, but they don’t cost you. The loop is a circle, not a spiral.

This is where the AI angle gets interesting. The developer didn’t write the code—they directed the AI. They acted as designer and critic, not typist. That’s the future: AI can write your code, but it can’t feel your game’s heartbeat. The human role shifts from execution to emotional pacing. And that’s exactly where Vein falls short. The mechanics are implemented, but the rhythm is off. The AI could generate the loop, but it couldn’t generate the tension.

You’ve probably felt this. You cut a feature thinking it would streamline the experience, and suddenly the game felt hollow. You added a tutorial that explained everything, and the mystery vanished. The friction you remove is often the very thing that makes the player feel alive. A game without friction is a movie without conflict—it’s a slideshow.

So what would fix Vein? The developer asks for feedback on making the core loop deeper without adding complexity. Here’s the answer: Don’t add more mechanics. Add more feedback. Give the heart a reason to race. Make the resources scarce. Create a timer that forces a trade-off. Let the player lose—not just fail, but lose something they care about. The minimalism is fine; the stakes are missing.

I’ve seen this pattern in indie games before. The developer falls in love with minimalism as a philosophy, but forgets that minimalism is a tool, not a goal. The goal is a meaningful experience. You can have a game with three rules and infinite depth. But only if those three rules create a system that pushes back. If the player never feels the bite, they never feel the thrill.

Go play Vein. It’s free, it’s open-source, and it takes five minutes. Then ask yourself: what’s the one thing that would make you care about that heart? That’s the question every indie dev should be asking. The AI can implement the answer. Only you can find the question.