Make a video game with AI: a straight account of how it works

Here is what happens, step by step, from installing the app to having a game you can play. No claims about typing a sentence and receiving a finished product.

Step one: it is a download

Stage Engine is a desktop application for Mac and Windows. You install it like any other program. There is no browser version, and no version that runs on a phone or a tablet.

Inside it is a copy of Godot, the open-source engine. That is what your game actually runs on, on your own hardware, when you press play. Nothing is streamed from a server and nothing renders remotely.

You need an internet connection while you build, because Director 1, asset generation and world data all come over the network. The game you have built plays without one.

Step two: you build a place

Before anything can happen in a game there has to be somewhere for it to happen. You make that yourself, in the builder, looking at it in a 3D viewport.

Terrain gets sculpted. Water takes an outline you draw. Sky and weather are settings of the world. Buildings, rocks, trees, furniture and characters get placed where you put them. Assets come from generation, from the web, from your own files, or get built directly as geometry when that is the straightest route to something playable.

This part is manual on purpose. Describing where things go in sentences is slower and less accurate than putting them there.

Step three: you describe what happens

This is where the AI is. You tell Director 1 in ordinary language what the game does — how the character moves, what the enemies want, what happens when you pick something up, when the level ends.

Director 1 writes GDScript into your project. Real files, real code, in a project you own. You are not required to read any of it.

You are required to play it. First versions are usually close and rarely correct, because the specifics of how something feels cannot be known before it exists. So you play, you say what is wrong, and it changes.

Step four: the loop, which is most of the time

Play, find the annoyance, fix it, play again. That is game development, with or without AI. What AI removes is the part where fixing the annoyance means a week of learning.

What it does not remove is you noticing the annoyance in the first place. Nobody else knows what your game is supposed to feel like.

What it costs and what it does not do

Free to download, with a free plan you can build on. Indie is $10 a month, Pro is $50, and paid plans buy more AI usage rather than a bigger engine. There is no team or enterprise tier.

It does not generate your game from a prompt, publish it to a store, or make design decisions for you. It removes the programming barrier and gives you a world builder, which turns out to be enough for a person with an idea and some patience.

Mistakes that cost people their first week

Building the world before movement works. You will size everything wrong, because scale only makes sense relative to how fast the character moves.

Asking for six things before checking whether the first one was right. Each of them assumes the others, and untangling that takes longer than doing it in order.

And starting too big. An open world is not harder to build than a small one in this tool, which is exactly why it is a trap: the building is easy and the filling is not.

Questions

What do I actually type?
Descriptions of behaviour, in plain language. Not code, and not descriptions of where objects go — you place those yourself.
What engine runs my game?
Open-source Godot, bundled with the app, running locally on your machine.
Can I make 2D as well as 3D?
Yes. Godot handles both natively.
Is any part of this in a browser?
No. It is a downloaded desktop app for Mac and Windows.
How much does it cost?
Free download and free plan. Indie $10 a month, Pro $50, for more usage.