An asset generator attached to the game the assets are for

Generate art in a standalone tool and you get a file. Then you import it, discover it is the wrong scale, fix the orientation, notice the material does not match the rest of the scene, and find the topology is unusable for the thing you wanted it to do.

None of that is generation failing. It is generation happening in a place that does not know what your game looks like. The generator had no idea what your scale is, what your lighting is, or what the rest of your world is made of.

Stage Engine generates inside the project. What comes out lands in your scene, at your scale, under your lighting, next to the things it has to sit beside. You can see immediately whether it belongs, which is the only test that matters.

Art can come from generation, from the web, or from you. All three are normal and the app does not push you toward one. A generated rock, a model you downloaded, and a shape you built by hand can sit in the same scene and often should.

For a stylised game, built geometry is frequently better than anything generated, because the style is the point and geometry is exact. For set dressing at distance, generation is fast and nobody is looking closely. Knowing which is which is a judgement, and it is yours.

What the app will tell you is which route it took. If something was built as geometry rather than generated, you will know.

It is worth saying plainly, because asset generation is the most demoable part of AI tools and the least load-bearing. A folder of beautiful assets is not a game and does not become one.

The game is the world you build out of them and the code that makes it do something. You place the world by hand in the builder. Director 1 writes the GDScript. Assets are supply for both of those and they matter, but a project stalls on systems and level design far more often than on art.

That is why generation here is a feature of the builder rather than the product. You reach for it while placing things, in the middle of a world, not as a separate errand.

Stage Engine is a desktop app for Mac and Windows, built on open source Godot. Assets go into a normal Godot project on your disk, so nothing you generate is trapped in the app.

Generation happens over the network, so you need an internet connection while building. The finished game runs locally on the bundled Godot without one.

The download is free and so is the free plan. Indie is $10 a month, Pro is $50, and what those buy is more usage, which for asset generation is the meaningful axis.

The most common mistake with generated art is judging each asset on its own. A world is judged as a whole, and a whole made of individually impressive but unrelated pieces looks worse than one made of simple pieces that agree.

Agreement means shared proportions, a shared level of detail, and materials that respond to light the same way. Those are properties of a set rather than of an asset, which is why generating into the scene is the right place to do it: you are always looking at the set.

Practically, decide the style early, produce a few things, put them next to each other, and be willing to throw out the best-looking one if it does not belong. That is art direction, and it is yours.

Sometimes the honest way to get what you asked for is to build the shape directly rather than generate it. Clean geometry is exact, cheap to render and easy to change, and for a stylised look it is often better than any generated result.

The app will do that when it is the right answer, and it will tell you which route it took. Knowing whether the thing in your scene was generated or built matters when you go to change it.

The point is that generation is a means rather than a commitment. What you want is the object in your world looking right, and there is more than one way to get there.