How to Make a Visual Novel With AI Without Losing the Plot
A visual novel is a story you read and steer by choosing, with character pictures and backgrounds, so the real work for your AI is keeping that story straight. Write one scene with one choice that changes a later line, and keep a record of who knows what.
Why do the branches get out of hand?
Start with some simple maths. If every choice split the story for good, six choices would leave you with 64 different stories. Nobody writes that, and an AI would write all of them slightly wrong.
So nearly every choice should branch and come back. The story splits for a scene and rejoins, and the game remembers what you did. Later, one line changes or one door closes. The reader feels the choice, and you still write one story with a few side rooms. This page shows the shape.
What does the smallest version look like?
Ilse is an apprentice violin maker with seven days until a concert and two teachers who disagree about everything. On day 2 she either tells Marek about the crack in the violin, or hides it. On day 6 Marek says one of two lines.
That is your whole first build: one choice, one memory, one payoff. If that line on day 6 gives you a small shiver, you are ready to write day 3.
What is really hard here?
Who knows what. In a film, everyone sees events in one order. Here, Marek might mention the crack on a route where Ilse hid it. The reader catches a character knowing something impossible, and trust is gone.
Your AI is prone to this, because it sees the whole script at once. Keeping characters consistent helps with the rest.
Which piece comes after which?
- Pick a format where each scene is plain text you can read and change. Ren'Py is a visual novel engine that builds for computers and phones. A plain web page also works for a short story.
- Write day 2 and day 6, with stand-in pictures.
- Add the dialogue system rules: what the game remembers, and when an answer appears.
- Add saving and stepping back a line, because readers expect both.
- Write the other days, one at a time.
- Make the final art last, and count it first. Three characters with six moods each is 18 pictures.
What is the mistake that sinks a visual novel?
Asking for the whole script in one go. It reads beautifully on the main route and falls apart on the second. Write one day, read every route through it, then move on.
Paste this to your AI
I am making a visual novel. Do not write the whole story. Start with two scenes: an early one with one choice, and a later one where a single line changes depending on that choice. Stand-in pictures, every scene as plain text I can edit.
Step one is a state machine in a Mermaid diagram of the reading loop: read, choose, remember, rejoin, payoff. Make sure every branch comes back or ends on purpose, and build from that.
Keep story-bible.md with characters and events. Model the story as facts (who is alive, who knows what, who is where, what has happened), scenes and choices as steps with what they need and change, and rules such as "nobody mentions a secret they never learned". Run every route through TLA+ and the TLC model checker, or through get_recipe story-model-check on Spielerando if it is connected. When a rule breaks, show me the exact order of scenes. I never want to read the model.
When a line depends on something earlier, quote the scene it rests on. If you cannot find where it was set up, say you do not know. Never write it as if it had happened.
Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP
A well-worded prompt alone would not save you here, because the AI would simply say the routes fit. This way it writes the story down as facts, scenes and rules, and a program reads every route. What reaches you is one short chain of scenes that shows where a character knows too much. That recipe comes through an MCP connection with a free account (Google or e-mail), and your script stays on your side.
How to check it worked
- Read both routes back to back. Take each option and read day 6. One line should change, and both should make sense.
- Hunt for leaks. On the route where Ilse hides the crack, search the text for any sign that Marek knows.
- Ask where a line comes from. In a new chat, ask why a character is angry. It should quote a scene. If it cannot, it is guessing.