Can AI make a 3D game?

A third-person controller, a camera that follows sensibly, an inventory, a save system, an enemy that patrols and then chases — a model writes all of these about as well in 3D as in 2D. The extra axis adds arithmetic, not difficulty.

So if your question is whether a non-programmer can get a character moving through a 3D space they made, the answer is straightforwardly yes, usually within the first evening.

The difference between 2D and 3D shows up somewhere else entirely: in the world, and in what it takes to run one.

More on this: A copilot for Godot, or something that does not need one

A 3D world is spatial taste expressed at scale. Where the ridge sits, how the valley funnels the player, which way the light falls, what you can see from the top of the hill. None of that survives compression into a sentence, and none of it has a correctness test — only whether it is the one you wanted.

Ask a model for a valley and you will get a valley. It will be plausible, generic, and not yours, and fixing something almost right by describing the difference is slower than shaping it with a mouse in the first place.

This is why serious 3D tools do not put the world on the model. It is not a capability gap waiting to close; it is a mismatch between the medium and the instrument.

More on this: Prompt to 3D game: the prompt writes the systems, you shape the space

A 3D world with terrain, water, weather and a few hundred simulated characters is real computational work. It needs a GPU and it needs memory, and where the game runs decides how much of it you can have.

This is why so many AI game tools are 2D or near-2D. A browser tab is a constrained environment, and a tool that renders inside one has to steer you toward small flat scenes whether or not it says so on the homepage. That is a legitimate trade for convenience, and it does put a ceiling on 3D.

Running on your own machine removes the ceiling and replaces it with your hardware, which is at least a limit you can see and choose.

More on this: A no-code game engine that is still a real engine

Making a project asks which kind of game it is before it makes anything: 2D or 3D, shown as two pictures, with no default. Pick 3D and the rest of this page is the case it was built for. Pick 2D and the flat world has its own set of tools — same app, same builder, the same chat. Either way it is a desktop app for Windows with Godot bundled inside it, and the game runs locally on that copy of Godot, at your machine's framerate.

In a 3D project, terrain, water, weather and populated worlds are the intended shape rather than an advanced feature you graduate into. You build them by hand in the builder, which is the manual half described above, and it is manual on purpose.

Flockbay writes the GDScript for everything the world does. Building needs an internet connection because the chat, asset generation and world data come over the network. Playing what you built does not.

If you wanted the AI to lay out the level for you, that path does not exist here, and it is a deliberate absence rather than a roadmap item.

If you need to work in a browser, on a phone or on a Chromebook, this is a download for Windows and a 3D game needs a real machine to run. And if you are after photorealism at the level of a large studio production, Unreal has more of that road paved and it is worth saying so.

More on this: Roadmap: the direction, and the things we have ruled out