AI incremental game maker: layers, resets and the moment it opens up

The genre gets flattened into "idle game" a lot, and the distinction is worth keeping. An idle game accumulates. An incremental game reveals: you play one system until it is solved, and then something unlocks that reframes what you were doing.

The good ones do this several times. The first layer is a resource. The second makes the first layer's output an input. The third makes the whole thing you were optimising into a single tick of something larger. Each turn is a small shock, and the shock is the product.

That structure is entirely mechanical. There is no art direction that saves a badly layered incremental, and no bad art that sinks a well-layered one.

The awkward part of building this genre is that each new layer touches everything below it. Prestige resets some values, keeps others, and applies a multiplier derived from what you gave up. Add a fourth layer and you are rewriting how the first three save.

You describe that to Director 1 instead. "Ascending resets all generators and currency, keeps upgrades bought with shards, and grants shards equal to the cube root of total lifetime output." It writes the GDScript into your Godot project, and when you decide the exponent is wrong, you say so.

Being able to restructure a layer in a sentence is what makes trying five versions of the prestige curve practical. In hand-written code, most people ship the first version because rewriting it is a week.

The failure mode is always the same: a stretch in the middle where the player is waiting and nothing new is coming. Twenty minutes of that and they close it and do not come back.

Finding those stretches means playing your own game slowly, over days, resisting the urge to give yourself resources. It is tedious and it is the job. Nobody can tell you where the dead hour is by reading your formulas.

A useful discipline is to write down, before you build, roughly when each unlock should arrive. Then play and see how far reality drifts. The drift is always larger than expected.

Most incrementals are interface. If you want yours to be more than that, Stage Engine runs Godot locally and is built around 3D, so the layers can be visible — a structure that grows, a landscape that changes each time you reset.

You build that by hand in the builder rather than describing it. That is deliberate: what a place looks like is a judgement you make by looking at it.

It is optional. A purely numeric incremental works and the code side is unchanged.

A desktop application for Mac and Windows with Godot bundled inside it. Your project is a real Godot project on your disk. The game runs locally when you press play.

Building needs an internet connection because Director 1 and generation are online. Free download and free plan; Indie is $10 a month and Pro is $50 for more usage.

An incremental game is played over weeks, which makes the save file the most important object in the project. A corrupted save is not an inconvenience, it is the player leaving permanently.

It also has to survive you changing the game. Adding a fourth layer must not break the save of someone who was halfway through the third, and getting that wrong is one of the most common ways these projects lose their players.

Say so up front. Describe that saves must keep loading as the game grows, and treat it as a requirement rather than something to sort out later.