What can Stage Engine not do?

Stage Engine is a desktop application for Mac and Windows, made by Flockbay. You download it and install it. Inside there is a builder where you place terrain, water, weather, buildings and characters by hand, and Director 1, which writes GDScript into your project. The engine underneath is Godot, which is open source, and your game runs locally on the copy of Godot that ships inside the app.

It is not a plugin for Unreal Engine and has nothing to do with Blueprints. It is not a Unity asset, not a website, not a phone app, and not a chat product that hands back a finished game. That confusion is common enough to be worth stating flatly before anything else.

Everything below follows from that shape. Most of these limits are not oversights waiting to be closed.

There is no web version and no plan for one. You cannot open a tab and start building. The app is downloaded and installed and runs on your own machine, and so does the game when you press play. No streaming, no cloud rendering, no remote preview.

There is no mobile or tablet app either. A phone can be a target you design for, but it is not a place you can work. Building a world means comparing things constantly, and that needs screen area and a mouse.

And it is not a VR tool. No headset preview, no controller mapping, nothing in the builder assumes a stereo camera, and none of the design problems that make VR hard are addressed anywhere in it. If the headset is the point, use Unity or Unreal, or Godot directly with its own XR support.

Director 1, asset generation and world data all come over the network. Without a connection you cannot build. This is not a degraded mode or a queue that catches up later. It is a plain requirement.

There is no offline mode and there is not going to be one, so a laptop on a plane is not the case this is designed for. We would rather say that than describe an offline story that quietly does not work when you need it.

The line worth remembering is that building needs the connection and playing does not. The game you have made runs locally on Godot, on your machine, with nothing of ours involved.

There is no button that puts your game on Steam, the App Store, Google Play or a console store. Not a hidden one and not a paid one.

Each of those is a process rather than a setting. Steam wants a developer account and a store page. Mobile stores want accounts, signing and review. Consoles want you approved as a registered developer by Nintendo, Sony or Microsoft, working on hardware they issue, passing their certification. That is true of every engine, including the expensive ones, and a product implying otherwise is selling you a story.

What you have instead is a real Godot project, and Godot has its own export tooling for desktop and mobile targets. Console ports usually happen through studios that hold the platform licences. All of that is outside this app, it is genuine work, and it starts after the game is finished and worth shipping.

No servers for your players. No multiplayer hosting, no matchmaking, no player accounts, no leaderboards, no cloud saves, no analytics. Godot has networking and Director 1 writes Godot code, so asking for networked behaviour is a normal thing to do. Running the servers a multiplayer game needs is yours to arrange, and multiplayer is genuinely harder than single player in every engine there is.

There is also no asset store. Nothing to browse, nothing to buy, no catalogue of packs. Art gets into a project three ways: it is generated, you bring it in from the web or your own files, or the shape is built directly in the builder because that is the honest way to get you playing.

The reason is not that a store would be too much work. A catalogue is a list somebody decided in advance, and it pulls every project toward the middle of the list.

It is not a Godot editor plugin and does not install into a copy of Godot you already have. There is no command line tool. There is no team plan, no per-seat pricing and no collaboration: one person, one app, one machine, and nothing merges two people editing the same project. AI usage is metered by plan rather than unlimited, and no plan buys a different engine, a better model or a higher ceiling.

It also will not tell you whether your game is good. It has no useful opinion about whether your village feels lonely enough, and there is no template that guarantees a result. You play it and you decide, and going back in because you disliked something is the normal shape of this work rather than a fault in it.

If you have read all of that and still want to download it, you are the person it is for: somebody who wants to build a specific game on their own machine, does not write code, and would rather own the project than rent it. If one of the limits above rules it out, that is an evening saved, and it is much better learned here than three weeks in.