How long does it take to make a game with AI?

Realistic: a piece of ground you shaped, a character that walks and jumps on it, and one thing that happens when you reach a particular place. Two to four hours including the download and finding out where everything is.

That is not a game. It is the moment where the project becomes real to you, and it matters mostly because it happens at all — the same milestone by hand means learning an engine first, which is weeks.

What eats the time in that first session is not the AI. It is you deciding what the space should be, and then deciding again after you have walked through it.

A small thing with a beginning and an end. One room or one short area, one mechanic, one reason to be there. Maybe five to fifteen hours spread over evenings.

Most of that time is playing your own game and disliking parts of it. The jump is wrong. The room is too big. The thing you thought was clever is tedious the second time. Each of those is a decision that could not have been made in advance, because it depended on something that did not exist yet.

The code changes in that week are minutes each. That is the whole shift: what used to be the expensive part is now the cheap part, and the ratio of thinking to typing goes up sharply.

Something you would put in front of a stranger. Several areas, a reason to keep playing, art that holds together, sound, a menu that is not embarrassing. Call it a few months of evenings for one person, and be suspicious of anyone quoting less.

The world is a large share of that. Building terrain, water, weather and places by hand takes real hours, and it is the part AI does not compress because it is taste rather than typing.

Polish is the other share, and it is the part everyone underestimates in every medium. The last ten per cent of quality is not ten per cent of the time.

The learning curve before you start. That is the largest single saving and it is invisible in any comparison that starts from "an experienced developer would take".

The implementation cost per idea. Trying a variation stops being a decision about whether it is worth an evening, so more ideas get tested, which usually improves the game more than the speed does.

And the debugging you would have done on your own mistakes. Some of it comes back as debugging the model's, which is a real cost and a smaller one.

Building the world. You shape terrain, water, weather, buildings and characters by hand in the builder, and that is hours of real work by design rather than by omission.

Judging the result. You play the game and say whether it is right, and being handed work back is the normal loop rather than a failure. Not writing the code does not mean not having an opinion about the game.

Practically: it is a desktop app for Mac and Windows with Godot inside it, the game runs locally, and building needs an internet connection while playing does not. The download is free and there is a free plan, so finding out how long your game takes costs nothing but the evenings.