Can it do a traditional turn-based, grid-based roguelike?

Yes. Turn order and grid movement are rules, and rules are what Director 1 writes. It is also fine with real-time action roguelikes; the genre boundary is a design decision rather than a supported-features list.

Do I have to design the procedural generation myself?

You decide what it should feel like and Director 1 writes the generator. You supply the rooms and pieces it assembles, which is the part that decides whether runs feel handmade.

Godot does both and so can you. The builder is at its strongest on 3D worlds with terrain and weather, so a 3D or isometric roguelike plays to its strengths.

Free to download with a free plan. Indie is $10 a month, Pro is $50. The paid plans buy usage, not a different engine.

Can I put it on Steam?

It is your Godot project, so nothing stands in the way. Releasing a game is its own body of work, but the tool does not hold your project hostage.

AI roguelike maker: the genre where code is most of the game

A roguelike is almost entirely rules: runs, drops, modifiers, death. Stage Engine hands that to Director 1 in GDScript while you tune the feel by playing.

A genre made of code

Most genres are part scenery and part system. Roguelikes lean hard towards system. What makes one good is the interaction between a hundred small rules: what drops, how often, what stacks, what the run does when you get an item early that you were meant to get late. Very little of that is visible in a screenshot.

That makes it an awkward genre to attempt without programming, and a very good fit for a tool where the code is written for you. You describe a rule, it exists, you play a run, you change it. The distance between an idea and a playable version of the idea is the entire bottleneck in roguelike design, and shortening it is the point.

What Director 1 handles

Run structure: seeds, floors, the branch after the third one. Item and modifier systems where effects combine rather than merely coexist. Enemy behaviour that changes with depth. Meta progression between runs, including the save that has to survive being closed mid-floor. Death, scoring and the summary screen.

All of it is GDScript written into your own Godot project on disk. You can read it. Nothing in the workflow expects you to, and the useful skill here is not reading code but noticing that runs are ending at the same point every time.

When you notice, you say so. The change is made and you play again. This is the loop, and it is not a fallback for when the automation fails; it is how the design gets found.

Procedural levels and the parts you author

Procedural generation is a rule set, and rule sets are code, so Director 1 can write yours. What it cannot invent is the hand-authored material the generator assembles: the room shapes, the set-piece arena, the terrain of the overworld if you have one. You build those in the builder, by hand, and the generator combines them.

This split is why hand-built pieces matter even in a procedural game. Generators that assemble from bland parts produce bland runs no matter how clever the assembly. Generators that assemble from parts somebody cared about produce runs that feel authored, which is the trick every good roguelike is playing.

Where it runs, and the trade

Stage Engine is a desktop app for Mac and Windows. You install it, and it brings Godot with it, so the game runs locally on your machine. That matters for a genre where people play hundreds of runs and notice a dropped frame during a dodge.

Building needs an internet connection because Director 1, asset generation and world data come over the network. Playing the game you built does not. There is no browser version, which is the trade for the local performance and for owning a real Godot project rather than a file that only works inside somebody else's site.

The download is free, there is a free plan, and Indie is $10 a month with Pro at $50 for more usage.

The first ten seconds of a run

Roguelikes live or die on repetition, so the opening is played more than any other part of the game, often hundreds of times. Anything slow, unskippable or fixed in that window becomes the thing people quit over, and it is almost always the last thing anyone thinks to test.

Get into the game fast. No long intro, no menu tour, no walk down a corridor before the first decision. Ideally the run is meaningfully different within the first minute so the player has something to think about rather than a routine to perform.

It is worth building the restart loop early and playing it twenty times in a row. That is an unpleasant test and it finds problems nothing else will.

Questions

Can it do a traditional turn-based, grid-based roguelike?: Yes. Turn order and grid movement are rules, and rules are what Director 1 writes. It is also fine with real-time action roguelikes; the genre boundary is a design decision rather than a supported-features list.
Do I have to design the procedural generation myself?: You decide what it should feel like and Director 1 writes the generator. You supply the rooms and pieces it assembles, which is the part that decides whether runs feel handmade.
Is this 2D or 3D?: Godot does both and so can you. The builder is at its strongest on 3D worlds with terrain and weather, so a 3D or isometric roguelike plays to its strengths.
What does it cost?: Free to download with a free plan. Indie is $10 a month, Pro is $50. The paid plans buy usage, not a different engine.
Can I put it on Steam?: It is your Godot project, so nothing stands in the way. Releasing a game is its own body of work, but the tool does not hold your project hostage.