AI idle game maker: the genre that is almost entirely code

Most genres have a physical half you can build with your hands. Idle games do not. There is no level, often no character, and frequently no space at all. What there is instead is a lot of arithmetic that has to be exactly right.

Production rates that compound. Upgrade costs on a curve. Offline progress computed from a timestamp. Prestige that resets some values and not others, with a multiplier derived from what you had. Numbers that exceed what a normal float can hold and need their own representation.

That last one catches nearly everybody. Get to the point where the counter should read a hundred quadrillion and a naive implementation quietly stops being accurate. It is a known problem with a known solution, and it is not one a first-time developer expects to meet.

With Stage Engine you describe the economy and Director 1 writes the GDScript into your Godot project. "Each generator produces one per second, costs 15% more each time you buy it, and the fifth of each type doubles the output of the one before."

That sentence is a complete specification, which is unusual — in most genres a sentence is a vague gesture. Idle games are the case where plain language is genuinely precise, and it is why they suit this way of working so well.

Then you play it, which for an idle game means playing it over several days and finding out that hour four is dead. Balance is the whole craft here, and balance is discovered by living with the curve rather than reading it.

Idle games that survive tend to have a place attached — a factory that visibly fills, a city that grows, a ship that gets larger. The numbers give the compulsion and the visible change gives the reason to come back.

You build that half by hand in the builder. Because Stage Engine runs Godot locally and is built around 3D, an idle game here can be a world that accumulates rather than a column of buttons, which is a less crowded shape than the standard one.

That is a suggestion rather than a requirement. A plain numbers game works fine and the code side is identical.

Offline progress. It is the defining feature of the genre and it is the most common thing to get subtly wrong, because the bugs only appear when the clock does something unusual — a long gap, a timezone change, a machine that slept.

Test it by actually leaving. Close it, come back tomorrow, check the number. Simulated tests pass while real clocks fail.

Desktop app for Mac and Windows, Godot bundled. Building needs an internet connection because Director 1 and generation are online. The game runs locally, so an idle game ticking away on your own machine does not need one.

Free download with a free plan. Indie is $10 a month, Pro is $50, both buying more usage.

One resource. One generator that produces it. One upgrade that makes the generator better, at a cost that rises. Offline progress. That is a complete idle game and it can be running in an evening.

Play it for two days before adding anything. You will find out where it goes flat, and the fix will be obvious once you have felt it rather than reasoned about it.

The second version is where the genre gets interesting, because that is where you add the thing that makes it yours rather than the thing every idle game has.