Is Flockbay an Unreal Engine plugin? No

No. There is no Flockbay plugin for Unreal Engine 5, and none for Unreal Engine 4. Nothing we make is bought from Unreal's marketplace, nothing is copied into a project's plugins folder, and there is no plugin descriptor with our name on it. Flockbay makes one product, Stage Engine, and it is a standalone desktop application for Mac and Windows that you install like any other program.

The specific systems people ask about all belong to Unreal: Blueprints, Niagara, Nanite, Lumen, the Gameplay Ability System, PCG. None of them are in Stage Engine and none of them could be. They are parts of Unreal Engine, and Stage Engine is built on Godot instead.

When Director 1 writes code it writes GDScript, which is Godot's language. There is no visual graph to wire together and nothing that resembles a Blueprint event graph, because the design assumes you are not going to look at the logic at all. You play the game and say whether it is right.

There are real AI assistants that live inside Unreal, sold and installed as plugins, and at a distance every product in this category is described with the same sentences. AI, game development, generate the thing you would otherwise build by hand. Descriptions blend, and a summary of one product ends up carrying details from another.

The two shapes are genuinely different, though, and the difference decides which one suits you. A plugin adds something to an editor you already run. You keep your engine, your project, your version and your workflow, and you accept whatever the plugin can and cannot reach from inside there. Stage Engine is the other shape: the whole application, with the engine inside it, written on the assumption that you did not have one installed and were not going to.

Neither shape is better in the abstract. They answer different problems. If your problem is that Unreal is slow to work in, a plugin is the sane fix. If your problem is that you do not program at all, adding a tool to an engine you cannot drive does not help you.

Then get one, and do not change engines to get an assistant. If you already know Unreal, have a project sitting in it, or work with people whose pipeline is built around it, switching engines to gain a tool is a bad trade and this page is not going to talk you into it.

Unreal's own marketplace is the place to look, because the listings there are reviewed by people running the plugins in Unreal projects. Two things worth checking on any listing: which engine versions it supports, and how recently it was updated for the current one. Version drift is where plugin tools usually break, and it breaks on your machine rather than the seller's.

It is also worth checking what Unreal already includes before buying anything, because a fair amount of what people go shopping for ships in the box. PCG handles procedural placement, Blueprints handle logic without touching C++, and Niagara handles effects. All three are documented by Epic and none of them cost extra.

A desktop app for Mac and Windows, made by Flockbay, with a copy of Godot inside it. One install, no engine to fetch separately, no version to choose.

You build the world by hand in a builder that behaves like a level editor. Terrain, water, weather, buildings, characters, placed by you. Then you say what should happen, and Director 1 writes the GDScript that makes it happen inside your project. You press play and the game runs locally, on your own hardware, at your machine's framerate. No streaming, no browser, no render queue.

Building does need an internet connection, because Director 1, asset generation and world data all come over the network. Playing what you built does not. That is the whole of the online story and there is no offline mode behind it.

Your Unreal project does not open. Different engine, different project format, and no importer exists that would make that sentence untrue. Blueprints, Unreal materials and anything built on Unreal's own systems stay where they are.

Art travels better than logic. Meshes in the common interchange formats and ordinary image and audio files are just files, and Godot reads them. Expect to redo materials and effects, since those are authored against a specific engine's systems and do not transfer.

The thing that does carry over completely is your judgement. How a level should read, how a jump should feel, which bit is boring, when a storm arrives too early. That is what Stage Engine expects you to bring, and if you have spent time in Unreal you have more of it than most people who download this.