Why Godot? — The Engine Behind Talisman Codes

I've Tried a Few Engines

Unity, Unreal, a bit of others here and there. I'm not starting from zero when it comes to game engines. Each one has its strengths, and I have opinions about all of them.

So why Godot?

Not Because It's the Best

I'll be upfront: Godot isn't objectively superior to Unity or Unreal. Those engines have massive ecosystems, proven track records, and enormous communities.

But for what I'm building — a 2D card battle game with a vibe coding approach — Godot fits. It's lightweight, the 2D workflow is clean, and it doesn't get in your way. For this project, that's exactly what I needed.

The Real Game Changer: VS Code + Claude CLI

Here's the part that actually transformed my workflow.

I'm not using Godot's built-in editor to write code. I write GDScript in VS Code with Claude CLI running alongside it. Claude handles the heavy lifting — generating logic, suggesting structure, iterating fast. Godot becomes the runtime: I push changes and check the results there.

This setup gave me a development speed I genuinely didn't expect. The bottleneck in solo game dev is usually writing code. With Claude in the loop, that bottleneck is mostly gone.

Right Tool, Right Job

Godot isn't the answer for every game. But for a 2D indie project built by one person with an AI-assisted workflow, it's a great fit.

Sometimes good enough — with the right setup — is better than the best.