Create a game with AI, and keep the part that makes it yours

The common pitch is a text box. You type a description, something appears, and you type again to fix it. It demos beautifully and it stops being fun about twenty minutes in, when what you want is "that tree, two metres left" and the only instrument you have is a paragraph of English.

The problem is not that the model is weak. It is that description is the wrong interface for spatial decisions. Nobody arranges a room by writing a memo about it. The moment your world has a hundred objects in it, saying which one you mean costs more effort than moving it would.

So the useful question is not how much of the game the AI can generate. It is which half of the work is genuinely better done by a machine.

Writing GDScript is a skill, it is learnable, and it takes months you may not want to spend. It is also unambiguous, testable and mechanical in a way that placing a forest is not. That makes it exactly the right thing to hand over.

Director 1 writes the code for your game inside your own project. The player controller, the enemy that hears you before it sees you, the inventory, the day that turns into night, the door that needs the key you have not found yet. You describe the behaviour, it writes the script, you run the game.

The code is visible. It is a normal Godot project, so a person who reads GDScript could read it. You are not required to. The expectation is that you play the game and tell Director 1 what is wrong with it, which is a judgement anybody who plays games can make.

You build the world by hand in the builder. Terrain that rises where you want it to rise. A lake with the outline you drew. Weather, buildings, characters, the ordering of the things a player walks past on their way somewhere.

This is not a consolation prize. It is the part where a game becomes a specific game rather than a competent generic one. The reason a place feels good to walk through is a hundred small choices that nobody can specify in advance, and making them directly is faster and better than negotiating each one in a chat window.

The two paths are separate on purpose. Director 1 writes code. You use the builder controls. There is no hidden third path where you ask and something quietly rearranges your world behind your back.

Stage Engine is a desktop app for Mac and Windows. You download it, you install it, and it brings its own copy of Godot. When you press play, the game runs on your machine, at your framerate, using your memory. No streaming, no render queue, no browser tab.

That is what makes a real world affordable. A scene with terrain, weather and a lot of moving characters is not something a browser tool can hold, which is why browser tools keep steering you back to flat little scenes.

Building needs an internet connection: Director 1, asset generation and world data all come over the network. Playing what you built does not.

Make something you can play on day one. A character, a small space, one thing to do in it. Play it. It will be worse than you imagined and that is the useful information you came for.

Then iterate in the direction of the thing you liked. Ask Director 1 for the behaviour you now know you need, and shape the world around it by hand. The loop is short because the game is running locally and you are the one deciding whether it is right.