# Story to game: what survives the translation and what does not

A story and a game are made of different material. Some of what you have written will transfer almost intact, and some of it will resist for reasons worth understanding before you start. Flockbay is free, AI included: free hosted AI every day, or your own Claude, ChatGPT, agent or API key. It runs on Windows, macOS and Linux, on the official Godot engine.

Source: https://flockbay.com/story-to-game/ · Updated 2026-10-01

## What transfers cleanly

Place transfers. A described location becomes a built location with very little loss, and it is the part of your writing Flockbay's world tools handle best — a 3D coast you walk down, or a flat one painted a cell at a time. If you have written a coastal town at dusk, that is a thing you can stand in.

Rules transfer. Anything in your story that works like a law — the dead do not speak after sunrise, iron burns the visitors, the bridge only holds one person — is already a game mechanic wearing a coat. Those are the most valuable lines in your notes.

[Characters transfer as behaviour](/ai-npc-generator/) rather than as people. A guard who is bored, a merchant who overcharges strangers, a dog that follows you: each is describable as what it does, and what it does is code.

## What resists

Interiority. Prose can say what someone is thinking. A game usually cannot, and the workarounds — journals, voiceover, a diary screen — are how the medium admits the loss rather than how it solves it.

Pacing. In a story you control exactly when the reader learns something. In a game the player might walk the other way for an hour. Any beat that depends on precise ordering needs either a gate or a rewrite, and gates are how a game starts to feel like a corridor.

The ending. Endings in prose land because everything before them was under your control. In a game they land when [the player feels responsible for arriving there](/blog/the-power-of-invisible-choices/), which is a different craft and usually the hardest part to get right.

## Your notes become the brief, and the brief becomes the build

Flockbay starts by asking about the story, one round at a time, each question with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. For a story the right first version is one location, not the novel. Nothing is built until you approve it.

Then it builds the place, with your descriptions as the reference. In 3D that is terrain, water, weather, time of day, buildings and characters. In 2D it is tile ground, with the tiles, the edges and the collision all falling out of which cells are covered, and sprites at an exact position, rotation and scale. When the harbour ends up on the wrong side of the bay, the same world tools are buttons in the Godot editor, so you can move it yourself, and Godot's undo takes it back.

Then you convert the rules. Each becomes a request to Flockbay, which writes GDScript inside your project: the door that only opens at low tide, the character who will not follow you past the treeline, the item you cannot drop. Flockbay runs each one itself first; then you play the result and say what is wrong.

That loop is the method. Describe, play, judge, revise. You are not asked to read the code and you are very much asked to have an opinion about [whether the scene works](/blog/how-to-judge-a-game-you-did-not-code/).

## A practical order of operations

Start with one location and one rule. A single place you can walk through, and a single thing that behaves strangely in it, tells you within an evening whether the story survives being stood in. It very often does not, and that is a cheap thing to learn early.

Then add the second location and [the way you move between them](/adventure-game-maker/). Travel is where most story games either become alive or become a menu.

Only then worry about dialogue, quests and sequence. Those are the parts most writers want to do first and they are the parts that are worthless if the place is dull.

## Dialogue, and the temptation to write more

Writers reach for dialogue first because it is the part they are already good at. It is also the part most likely to go unread, because a player who came to explore a coast will skip a screen of text to get back to the coast.

The usual fix is to cut dialogue by half and put the same information somewhere the player will meet it anyway: a room that is obviously abandoned, a boat with the name scratched off, a light that is on when it should not be. [Environmental storytelling is not a technique](/blog/how-level-design-can-tell-a-story/), it is what the medium is good at.

Keep the lines you cannot express any other way. Those will land, and they will land harder for being rare.

## The practical facts

Flockbay is a desktop app for Windows, macOS and Linux. It ships with Godot inside it, so your game runs locally at your machine's framerate. Your project is an ordinary Godot project on your disk, and Godot is open source.

Building needs an internet connection, because the chat, asset generation and world data come over the network. Playing what you built does not.

The platform is free. [Flockbay is free, AI included](/answers/what-does-flockbay-cost/): free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key. Flockbay builds from a library of ready-made objects, or with Godot's own shapes.

## Questions

### Can I paste my whole story in and get a game?

Not in one go, and any tool claiming otherwise is selling something. Paste it in and Flockbay turns it into a brief: what gets built first, what comes after, what is not in this version. Then it builds the place and converts the rules one at a time, and you play each step. That is slower than one prompt and produces a game rather than an outline.

### Is this good for visual novels?

The reason to say no is shape rather than dimension. A pure branching-text visual novel is a script and a choice tree, and a tool designed for that will serve it better. What you build here is a place you move through, 2D or 3D, and if your story wants one of those it is the right way round.

### How is dialogue handled?

Dialogue is code and content. Flockbay writes the system; the lines are yours, because that is the part you actually came here with.

### Do I need to write code?

No. Flockbay writes GDScript into your project. You judge the result by playing it.

### Does it run in a browser?

No. It is a desktop app for Windows, macOS and Linux, and the game runs locally on the bundled Godot.

Download Flockbay free: Flockbay is free to download for Windows, macOS and Linux. https://flockbay.com/

Related: [Text to game](/text-to-game/), [Idea to game](/idea-to-game/), [Describe a game](/describe-a-game/), [AI visual novel maker](/ai-visual-novel-maker/), [AI adventure game maker](/ai-adventure-game-maker/)