A character is a model plus everything that makes it move

When someone searches for a character generator they usually picture a finished thing: someone who stands in the world at the right height, walks, turns to look at the player, and has an opinion about them.

A generated model is a portion of that. The rest is scale relative to your world, a skeleton, animations that do not slide, a collision shape that matches the silhouette, and code that decides what the character does. Every one of those is defined by your game rather than by the model.

This is why generating characters inside the project is different from generating them in a separate tool. The character arrives in your scene, next to your player, under your lighting, at your scale. You can see in a second whether it belongs there.

A villager with a daily route. A guard with a suspicion level. An enemy that hesitates before committing. A shopkeeper who remembers what you sold them. That is all GDScript, and Director 1 writes it inside your project.

You describe the behaviour, play the game, and say whether it reads. This is where most character work actually happens, because behaviour is judged by watching and not by specifying. A guard whose patrol is technically correct can still look wrong, and the only way to find out is to stand and watch it.

Saying it looks wrong and asking for another pass is the normal loop. Not writing the code does not remove your opinion about how the guard should move.

A world where every character was generated separately tends to look like it. Different proportions, different levels of detail, different material treatment. Individually fine, collectively incoherent.

The way through is to decide the style first and then hold everything to it, whether it came from generation, from the web, or was built as geometry. Simple built characters, consistently proportioned, will beat a mixed bag of impressive ones almost every time.

Because you are placing them yourself in the builder, you see the collection rather than the individual. That is the view that tells you the truth.

Stage Engine is a desktop app for Mac and Windows. The engine underneath is open source Godot, and characters go into a real Godot project on your disk.

Generation happens over the network, so building needs an internet connection. The game runs locally on the bundled Godot and does not.

Free to download with a free plan. Indie is $10 a month, Pro is $50, and the difference is usage.

A crowd of twenty identical villagers reads worse than four who are clearly different and are somewhere specific. Population is not a number, it is a set of small stories about who is where and why.

Because you place characters by hand, you can put someone in a doorway rather than distributing them evenly. That single decision does more for a village than any amount of variation in the models.

It is also cheaper. Four characters with real routines is less work than twenty with none, and it is what a player will actually remember about the place.

The character players remember is usually the one who was there at the right moment, not the one with the best model. Someone at the gate when you first arrive. Someone who is missing later.

That is placement and timing rather than art, which is good news, because both are things you control directly.

So before generating a cast, work out which one or two people the game is actually about and build those properly. The rest of the population can be simpler than you think and nobody will notice.