Claude Code schreibt Spielcode, aber nicht das ganze Spiel

Posted on Oct 13 • Originally published at alegauss.github.io

A coding agent can write a lot of a game today: the player controller, the menu logic, the save system. Then you need a mascot, a coin sound, a background loop and a third level, and the agent can't help anymore. It can't see a render, hear a sound or play a level, and it has no idea when any of those is good enough.

AI generators don't fix that. You type a prompt and get a 3D model, a picture or a voice line in seconds, and then the real work starts. Does it match your sketch? Is it the right orange? Does the loop click at the seam? Does it look like it belongs in the same game as the other forty assets? The generator made a guess, and you're the one who has to check it.

polyweave is a free, open-source plugin for Claude Code that takes on that checking.

polyweave started inside a real game. Cottony is a plush-themed match-3, with hearts, drops and stars made of felt that squash when they land. Its tiles are rendered in Blender, and getting them to look right meant tuning fourteen render settings by hand: change one number, wait about two minutes for a render, look at it, decide, repeat.

Making the model was quick. Most of the time went into the stretch between having a model and knowing it's right. That stretch is what polyweave is for.

With polyweave, every part of your game starts as a short file that says what correct means for it. You don't write that file yourself. You describe what you want in plain words, and Claude Code writes it down as a list of checks with limits:

Once that bar exists, the work no longer depends on someone squinting at renders. Claude Code can make a candidate, measure it against the bar, adjust the settings and try again, and the misses get thrown out before they ever reach you.

The same loop covers every layer of a game:

Every layer shares one config file, one record of how each part was made and one review page, so you judge the game's parts together instead of one tool at a time.

polyweave doesn't replace Blender, Godot or your favourite generator. It sits in the middle and talks to each one in its own language:

Here's what that looks like for a mascot drawn from your sketch:

There are plenty of tools that connect an agent to Blender or Godot. What they don't tell the agent is when to stop. In polyweave that's the job of the bar, so the agent works on the tools until the result is right, not just until it's done.

Which tool you use is a line in a config file in your repo. Swap models whenever you like and the bar each part has to pass stays the same.

Handing an agent a credit card and your art direction is a fair thing to be nervous about. polyweave has three rules about that, and the agent can't get around any of them:

Each file also keeps its history: which model, prompt, seed, cost and licence produced it. Writing your credits screen and checking licences become a lookup.

Viglet Games is making its games with polyweave, and both are in development for Steam:

You need Claude Code and Python 3.11 or newer. Blender and Godot are optional: polyweave tells you which tools it found and what each missing one would unlock.

pip install git+https://github.com/alegauss/polyweave /plugin marketplace add alegauss/polyweave /plugin install polyweave@polyweave Enter fullscreen mode Exit fullscreen mode Then ask:

Set up polyweave in this project, and make me a mascot from docs/sketch.png.

If you're making a game with an agent, I'd like to hear which part of it is still eating your time. Leave a comment.