Is there a Stage Engine command line?

No. Building a game in Stage Engine happens in the app: a desktop application for Mac and Windows, with a 3D builder in it and Director 1 alongside. There is no command you type to make a level, generate an asset or run a build, and there is no headless mode you drive from a script.

That is a deliberate consequence of who this is for. The person using it does not write code and has no reason to open a terminal. A command line surface would be a second, worse way to do everything the app already does, aimed at somebody who is not the user.

A project directory. The engine underneath Stage Engine is Godot, which is open source, and what you build is a real Godot project: ordinary files, in ordinary folders, in a documented format.

That is the part people usually want a CLI for. Backing the project up, copying it to another machine, putting it in version control, handing it to somebody who does write code, or opening it in Godot directly. None of those need a command from us, because none of them are special. They are file operations on files.

It also means nothing about your project is locked behind a tool that has to still exist. A directory of Godot files is readable by an engine anybody can download for free.

Director 1 writes GDScript into your project. Those are text files sitting in the project directory with everything else. You are never asked to open them, and nothing hides them from you.

This is worth knowing if you have any technical background at all, or if you might work with somebody who does. A programmer looking at your project sees a normal Godot project with normal scripts in it, not an exported blob or a proprietary bundle. Handing the work over is a handover rather than a migration.

The reverse is also true: files you put into the project, whether models, textures, audio or your own scripts, are read the way Godot reads them.

Building. Director 1, asset generation and world data all come over the network and run through the application, which is also why an internet connection is required while you build. There is no offline path and there is no scripted path.

Playing is different. The game runs locally on the copy of Godot bundled with the app, on your machine, at your framerate, and it does not need a connection.

If you were hoping to automate world building from a script, that is not what this is. The world is built by hand, in the builder, by a person looking at it. That is the design rather than a gap waiting to be filled.

Mac and Windows, as a download. No browser version, no phone version.

Free to install with a free plan. Indie is $10 a month, Pro is $50. Those buy more usage rather than a different engine or a different set of tools.

None of the above is required. Most people building here will never open a terminal, never hand the project to anybody, and never need to know where the files sit on disk. The point is only that the option exists, that it costs nothing to keep open, and that it is there because the project is stored in a format somebody else already documented rather than one we invented.

Plenty of non-technical creators work with somebody who is not. A friend who programs, a contractor for the last ten percent, an artist with a technical streak.

The arrangement that works is that they open the project in Godot and work in it the way they normally would, while you continue in Stage Engine building world and asking for behaviour. Nothing about the project format prevents this, because there is no proprietary layer between the app and the files.

What is worth agreeing up front is who owns which files, since two people editing the same scene at once ends the way it always does.

The other thing that helps is deciding early which parts are theirs permanently. A programmer who owns the systems and a creator who owns the world is a clean division. A programmer who is called in to fix things intermittently ends up rewriting whatever changed since last time.