AI sprite generator, and the part it leaves you holding

Generating a single good sprite is close to a solved problem. There are plenty of sites that will do it, and some of them are excellent at it. If that is all you need, use one of those; there is no reason to install a game engine to get one image.

The problem starts at sprite number two. You need it to match the first: same palette, same weight of outline, same light direction, same apparent scale. Then you need the walk cycle to match the idle, and the enemy to look like it lives in the same world as the player.

Consistency is what actually decides whether a game looks made or assembled, and it is the thing that a series of one-off generations in a browser tab tends not to produce.

The Catalogue holds 60,648 objects, and 55,073 of them are sprites. You search it by name and see a picture of each result, which is the only kind of search that works for art. That is the honest first answer to where the sprites come from, and it beats generating them for a reason nobody enjoys admitting: a library drawn as a library already matches itself.

They go into the project by hand. Pick one, put it at an exact position, turn and size with the mouse. A picture sits on its own drawn bottom-centre rather than the middle of its file, so a lamp post stands on the ground instead of floating by however much transparent margin the file carries, and draw order follows that same point, so the thing lower down the screen is in front. Those two behaviours are the difference between placing art and arguing with it.

You can bring your own too. It is a normal Godot project, so anything Godot imports works, and drawing your own is still the route that produces a game only you could have made.

Director 1 will generate a single flat picture when you ask for one, and it arrives inside the project, next to the assets you already have, in a scene you can look at it in. You see the mismatch straight away rather than three exports later.

It will not generate an animated one. No frames, no sprite sheet, no walk cycle for a character you invented. If your protagonist has to move through drawn poses, that art comes from you, from an artist, or from the web. This is a real gap rather than something we are being careful about the wording of, and it is better read here than discovered on the day you need it.

Pixel art is a style with strong conventions and an audience that reads them closely. The tile grid suits it, which is an observation and not a recommendation — your style is yours. Whether a generated picture passes as pixel art rather than as a picture of pixel art is a call you are qualified to make, and we would rather say that plainly than promise a finished sprite sheet.

In a standalone generator, getting the picture is the short half. Then you import it, set it up, hook it to a controller and write the code that makes it do something. That tail is longer than the generation and no generator advertises it.

Here the thing a sprite lands in is already a game. A new 2D project opens playable: sky, a band of scenery along the horizon, ground with a ledge in it, a floating platform, and a person who walks, falls and jumps. Ground is painted rather than assembled — you drag to lay cells and drag to erase them, and the tiles, the edges and the collision all fall out of which cells are ground, so a sprite you place has something to stand on a minute after it arrives.

The behaviour is a sentence. Director 1 writes the GDScript into your project: what the enemy does when it loses sight of you, what the pickup does, what happens to the save when somebody quits mid-level. You play it and say what is wrong, which is the normal loop rather than a sign of failure.

Flockbay is a desktop application for Mac and Windows. You download and install it, and Godot ships inside it so your game runs locally on your machine.

Building needs an internet connection, since Director 1, generation and world data all come over the network. Playing the game you built does not.

The download is free, and the builder is free to use with your own art. Indie at $10 a month unlocks Director 1 and generation, and the free plan carries a limited trial of it.

Settle the main character first and treat it as the reference for everything else. Every later asset gets compared to it: same light direction, same palette, same level of detail. Deciding that once, at the start, saves you from a library of pieces that individually look fine and collectively look like a pile.

Then get it moving in the game before you add anything more. An asset that looks good in isolation and reads badly at actual size, in motion, against your background is a very common outcome, and you want to discover it on asset one rather than asset thirty.

After that the rest is production and it goes quickly, because searching a catalogue that already matches itself is faster than asking twice for consistency and comparing the answers.