Random game idea generator, and what to do the moment after

Random idea generators are fun and almost useless on their own, because the value of a game idea is entirely in what happens when you play it. The interesting question is how fast you can get from a sentence to something running.

Why random prompts feel good and rarely go anywhere

A generated combination — a fishing game about grief, a stealth game where you are the building — is genuinely useful as a jolt. It gets you out of the ruts you already have and it is a decent way to start a game jam.

The problem is that an idea has no quality until it is played. "Time slows when you stand still" sounds brilliant and may be tedious. "You can only move one square per hour of real time" sounds terrible and might be the best thing you make. There is no way to tell from the sentence.

So the generator is not the bottleneck. Getting to the point where you can tell is the bottleneck, and traditionally that took a week of code.

Cut the distance to the first play

In Stage Engine you describe the core mechanic and Director 1 writes the GDScript into your project. Then you press play, on your own machine, with the game running locally on the bundled Godot.

You will usually know within about ten minutes whether the idea has anything in it. That is the whole value. Nine ideas out of ten die at that point, which is exactly what should happen to them, and dying cheaply is what makes the tenth affordable.

The world around the mechanic gets built by hand in the builder — terrain, water, weather, buildings, wherever the idea needs to live. For a first test that can be crude on purpose.

How to test an idea properly

Strip it to the one thing that is interesting and build only that. No menus, no art pass, no title screen. If the idea is about a rope, make a rope and nothing else.

Play it yourself, then have someone else play it without explaining it first. Their confusion is data. If they need the explanation to enjoy it, the idea is not carrying itself yet.

Then either sharpen it or throw it out. Being willing to throw out something you spent two hours on is much easier than throwing out something you spent two weeks on, which is the real argument for making the two hours possible.

Where the ideas that survive end up

A Godot project on your disk, which is a real one rather than a file only this tool understands. If a prototype turns out to be worth years, it is not stranded in a sandbox.

Stage Engine is a desktop app for Mac and Windows. Building needs an internet connection, because Director 1, asset generation and world data all come over the network; playing what you built does not. Free to download with a free plan, Indie at $10 a month, Pro at $50.

Bad ideas are the point

The generator is not trying to hand you a good idea and neither is anyone else. What it does is widen the pool, and a wider pool means a better best item even though the average gets worse.

So treat volume as the strategy. Ten prototypes that die in an afternoon each is a better month than one prototype you nursed for four weeks because you were too invested to admit it was dull.

Keep a note of the ones that half worked. A mechanic that was boring on its own is sometimes exactly what another idea was missing, and you will not remember it in six months if you did not write it down.

Questions

Does Stage Engine generate game ideas for me?
That is not what it is for. It is for finding out quickly whether an idea you already have is any good.
How long does a first prototype take?
That depends entirely on the idea. A single mechanic is a short session; a world with systems is not.
Is this good for game jams?
The short loop between describing something and playing it is the part that suits a jam. Remember that building needs a connection.
Can I keep several prototypes?
Yes. Each one is a separate Godot project in its own folder on your disk.
Is it free to try?
The download is free and there is a free plan. Indie is $10 a month, Pro is $50.