An AI game maker without a credit counter, and what it costs instead

The problem with a visible balance is not the money. It is what it does to iteration. Every time you consider trying a second version of something, the counter is an argument against it, and you accept the first result more often than you should.

That is the opposite of how anything creative works. A game gets good because you did the thing eleven times. A pricing model that makes attempt eleven feel expensive is quietly making your game worse.

So the counter is not just an accounting choice. It is a design constraint on the user, and it usually was not intended as one.

By plan. There is a free plan, Indie is $10 a month, and Pro is $50. What you pay for is more usage of the parts that run on our infrastructure — Director 1 writing your code, and asset and world generation.

Here is the honest part: more usage is not infinite usage. Any tool that pays a model provider per request and offers you unlimited requests is either mispricing or planning to change the terms. The difference is that a plan is a broad allowance you work inside rather than a number that ticks down in your peripheral vision while you decide whether to try something.

Paid plans do not unlock features. They are the same engine and the same builder. You do not get better code by paying more.

The builder is yours. Placing terrain, shaping a coastline, moving a building, adjusting weather, rearranging a whole level twelve times — none of that touches our infrastructure and none of it is metered.

Playing your game is free in the same sense. It runs locally on the copy of Godot bundled with the app, on your own machine, for as long as you want.

So the pattern that gets expensive elsewhere — endlessly re-rolling a scene — is here mostly a thing you do with your hands at no cost.

A desktop application for Mac and Windows, downloaded and installed, with Godot inside it. Not a browser tool. Your project is a real Godot project on your disk.

Director 1 writes the GDScript for the behaviour you describe. You build the world by hand and judge the result by playing it.

Building needs an internet connection because the AI and generation are online. Playing what you built does not.

The question worth asking about any of these tools is what happens on your eleventh attempt at the same thing. If the answer involves opening a top-up page, that will shape your project whether you want it to or not.

The free plan is there so you can find that out without paying anything. That is the point of it.

Two things run on our infrastructure: Director 1 writing code, and generation of assets and world data. Those are what a plan meters, because those are what costs money per request.

Everything else is your machine. The builder, the editor, the game running on the bundled Godot, your project files on your own disk. None of that is counted and none of it stops if your allowance runs low.

So the practical shape is that heavy world-building days cost nothing and heavy system-writing days are where usage goes. That is worth knowing when you plan a week.