Making a game from a picture: what a reference image can and cannot do

An image carries an enormous amount about mood, palette, scale and light, and almost nothing about rules. Look at a screenshot of a game you love and try to work out from the pixels alone how far the character jumps, what happens when you run out of stamina, or whether the doors need keys. You cannot. That information is not in the picture.

Which is why "upload an image, get a game" is a claim worth being sceptical of. What you can honestly get from an image is a look: the colour of the light, the density of the trees, the silhouette of the buildings, the general sense of what kind of place this is.

That is genuinely useful. It is just not the same thing as a game, and treating it as one is how people end up with a pretty scene and nothing to do in it.

More on this: What generated pixel art is actually good for

Keep the picture open beside you and read it in order. In a 3D world it is the terrain shape first, then the light, then the density of what is on the ground. In a flat one the order is different: the sky colour and the band of scenery along the horizon carry the mood, then the shape of the tile ground, then what stands on it. Three things either way, and each one becomes a line in the brief Flockbay writes with you before it builds anything.

Then Flockbay builds it with its world tools, as real nodes in the scene tree, and you hold the result up against the picture. Most of what is off is a sentence: the fog is too thick, the trees are too sparse. Some of it is pure taste, like exactly where the ridge sits against the sky. For that, the same tools are buttons around the Godot editor's own view, so you can drag the ridge yourself, and Godot's undo takes it back.

Assets that need to match the reference come from a library of ready-made objects, from Godot's own shapes, from generated pictures, or from your own files. Which of those makes sense depends on the picture. A stylised low-poly reference is often quickest built from simple shapes; a dense photographic one usually is not.

Then stop matching and start playing. The picture got you the atmosphere. From there the reference stops being useful, because a still image has no opinion about what the fifth minute of your game should be.

More on this: AI low poly game maker: a style that a small project can actually finish

You describe them, they go into the brief, and Flockbay writes them as GDScript in your project, then runs the game to check they work. This is the part of the game the picture could never have told you, and it is the part where plain language works well, because rules are naturally sentences.

The loop is: say what should happen, play it, say what is wrong. You do not read the code unless you want to. You do judge the result, every time, because you are the only one who knows what the picture meant to you.

Flockbay is a desktop app for Windows and Linux. It installs, it bundles Godot, and your game runs locally on your own machine when you press play.

Building is online. The chat, asset generation and world data come over the network. Playing what you built does not need a connection.

The download is free, and so is every world tool. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

Pick the one thing in the picture that made you want to make a game. Usually it is not the whole image. It is the light, or a single structure, or the emptiness.

Make that one thing the whole first version in the brief. Build that one thing first, badly, and go and stand in it. If the feeling survives being playable in a space you can walk around, you have a game to make. If it does not, you have learned that in an hour instead of a month.

The usual way it fails points at a decision made before anything else. Some images only hold up from the angle they were painted at, and being able to walk round them is what kills them — which is an argument for making the game 2D rather than an argument against the reference. A composition that dies in three dimensions is often perfectly sound held flat, with the scenery along the horizon doing the work the painting was doing.

The two things that carry a visual style are colour and silhouette. Get the palette approximately right and the outlines approximately right and most people will read your scene as belonging to the same family as the reference, even if the details differ completely.

Detail is much less important than it feels. Reference images are usually final art from a finished production, and chasing that level of finish on a first project is how projects stop.

It is also worth checking whether the picture is achievable in motion. A palette travels. A painted effect that only exists because someone rendered one frame by hand does not, and no amount of matching colours will get it. Building a rough version early is how you find out cheaply which of the two you are holding.