An FPS maker that runs the shooter on your own machine

Stage Engine is a desktop app for Mac and Windows with a copy of Godot inside it. Pressing play runs your shooter on your own machine, at your machine framerate, using your machine memory and graphics card.

Browser-based makers cannot do this, and the consequence is not abstract. It is why their example projects are small, why the draw distance is short, why there are rarely more than a handful of active enemies, and why the lighting is baked flat. A tab is a budget.

If what you want is a shooter with a long sightline, a real skybox, dynamic shadows and twenty things happening at once, running locally is not a preference. It is the requirement.

You build the level directly. Terrain, buildings, cover, props, light. It is a level editor, so you are looking at the thing you are changing rather than describing it and waiting.

Director 1 writes the code: the controller, weapons, damage, enemy behaviour, objectives, the pause menu, the save. GDScript, inside your project, where you can see it. You describe what should happen and then check by playing.

The check is the important half. Play the level, notice you always approach from the left, and go move something. Nobody can tell you that from a description and no generator can predict it.

The app assumes you do not write code. It does not assume you cannot tell a bad shooter from a good one. Those are different things and most tools in this space confuse them.

So the loop is: describe, play, disagree, describe again. Handing work back because the recoil is too heavy is the normal state of the project, not a fault in the process.

What you will not do is spend the first two weeks getting a character controller to stop clipping through walls before anything is fun.

It is a download and an install, on Mac or Windows, and both platforms ship. The project it produces is a real Godot project, so it is not locked to this app.

Building needs an internet connection, because Director 1, asset generation and world data come over the network. The finished game runs without one.

The download is free and there is a free plan. Indie is $10 a month and Pro is $50. Those buy more usage, not a bigger engine or a higher level cap.

Long sightlines with things worth seeing at the end of them. Dynamic shadows that move. A skybox and weather that change the read of a level between the start and the end. Twenty enemies active rather than five.

None of those are exotic. They are ordinary shooter features that a constrained runtime makes into a fight, and running on your own hardware makes into a default.

It also means your performance testing is real. What you see when you press play is what someone on a similar machine will see, rather than a number filtered through a shared server and a browser tab.

Because you are testing on your own hardware, you find out early what your level can afford, and that is useful information rather than bad news.

Knowing you have headroom lets you commit to a long sightline or a heavier lighting setup. Knowing you do not lets you design around it while the level is still cheap to change.

Either way it is a real measurement of the machine your player will use, taken during the work rather than at the end. That is not something a shared or browser runtime can give you honestly.