A monster collector is a spreadsheet with a world around it

Designing creatures is delightful. Deciding that the grass one evolves into something with a bell for a head, working out that the type chart needs a fourth element to stop one strategy dominating, drawing the routes between towns — this is why people want to make these games.

Implementing the battle system is not delightful. Turn order with priority moves, status effects that tick at the right phase, stat stages, accuracy checks, experience curves per species, a catch formula, evolution triggers, a party and a storage box, and a save file that holds every creature's individual state. It is weeks of exact, unforgiving code before the first battle resolves correctly.

That split is the reason this genre has so many abandoned projects. Stage Engine moves the second job to Director 1.

You describe the systems in plain language. Six types with these strengths. Moves have power, accuracy, a type and an optional effect. Creatures have six stats and a growth rate. Catch chance depends on remaining health and status. Director 1 writes the GDScript inside your project.

Then adding the sixtieth creature is a sentence rather than an afternoon, which is the difference between a demo with four creatures and a game with a roster. Balancing is the same: you say the fire line is too strong at level twenty, you play the fight again, you decide.

You never have to open a script. You do have to play the battles and have opinions about them, and that is not a lesser role. The person who plays it is the person who knows whether it is right.

The world is half the appeal of this genre. Routes that gate progress, a cave that connects two areas, tall grass in the right places, a town you return to. That is placement work, and it is faster and better done with your hands in a 3D builder than described in a paragraph.

Stage Engine is built for worlds with real terrain, water and weather, which suits the genre well. Weather that changes what appears in an area is a classic mechanic in creature collectors and it sits naturally on top of a weather system that already exists.

The look is up to you. Art comes from generation, from the web, or from your own hand, and geometry can be built directly in the builder when that is the honest way to get you playing.

A desktop app for Mac and Windows with Godot bundled inside. Your game runs locally when you press play. There is no browser version and no streaming.

Building needs an internet connection, since Director 1, asset generation and world data all come over the network. Playing what you built does not. The download is free, there is a free plan, Indie is $10 a month and Pro is $50, and the paid plans buy more usage rather than a bigger engine.

You can build a type chart that looks symmetrical on paper and produces one dominant strategy in practice. The only way to find that out is to play the game and notice that you always pick the same creature.

So the balance loop matters more than the initial numbers. You play, you notice, you say the water line needs a weakness it does not have, and the change gets made. Fast changes mean many passes, and many passes is what separates a roster that rewards experimenting from one where three creatures are correct.

Progression pacing is the same kind of judgement. How long until the second evolution. Whether the third gym is a wall. Whether the player has enough creatures by then to have a strategy at all. Play it as though you had not designed it, and take the boredom seriously when it arrives.