Game development software you install, with AI inside it

A place on your disk. Your project is a folder of real files rather than rows in someone database. You can back it up, copy it to another machine, put it in version control, and open it with something that is not this app.

Your own hardware. When you press play, the game runs on your graphics card and your memory rather than a slice of a shared server or a browser tab. That is what makes a large 3D world a reasonable thing to build.

And a version you control. Software on your machine keeps working the way it worked yesterday. That has become an unusual property and it is worth naming.

Godot, bundled. It is open source, it is what your game actually runs on, and your project is a normal Godot project. Nothing about the format is proprietary to this app.

A builder, which is where you construct the world by hand. Terrain, water, weather, buildings, characters, lighting. It behaves like a level editor because that is what it is.

Director 1, which writes the code. You describe what should happen and it produces GDScript inside your project. You are not asked to read it, though you can.

It is installed software but it is not offline software. Director 1, asset generation and world data come over the network, so building requires an internet connection. Working on a train without signal is not a thing this does.

What runs without a connection is the game you built, because it runs locally on the bundled Godot.

There is no cloud rendering, no streaming and no browser preview anywhere in the product. The only thing that goes over the network is the building help.

Mac or Windows. Both platforms ship and neither is an afterthought. You need to be able to install software on the machine, which rules out a lot of managed school and work computers.

The download is free and there is a free plan. Indie is $10 a month and Pro is $50. The paid plans buy more usage of the AI. They do not unlock engine features, export targets or a larger project size, and there is no per-seat or enterprise tier.

Trying it costs nothing, which is the sensible way to find out whether the shape of the tool suits how you work.

Because your project is a folder of ordinary files, everything you would normally do with files works. Copy it before a risky change. Put it in git if you know how. Keep it in a synced folder if you do not.

This sounds obvious and it is worth stating, because tools that keep your project on a server take the decision away from you and usually offer their own history instead.

The habit worth having from the first week is a copy of the project from before anything large changed. It is the cheapest insurance in game development and it costs one drag of a folder.

Because the project is a folder, working across a Mac and a Windows machine is a matter of moving the folder. Godot opens it on both and the app runs on both.

That is not a headline feature; it is a property of building on files and open source rather than on a service. It also means a collaborator with their own Godot install can work on the same project.

The thing that does not travel is your AI usage, which belongs to your account rather than the machine. Everything else is on disk.