Undo in AI Story Games Is Really Four Buttons

Undo in AI story games is not one action wearing one name. At least four things hide behind that button: stepping back to a scene you already read, asking the narrator to retell the scene it just wrote, editing the text by hand, and abandoning the branch to start over. Each does something different to the story’s memory, and the memory is what decides whether the story still makes sense when you go forward again.

• Stepping back returns you to a scene you have already read, and the story continues from there.
• Retelling discards the newest scene and asks for a different one from the same moment.
• An undo is only clean if the story’s memory rolls back with the text; otherwise the record keeps facts the page has retracted.
• Classic interactive fiction implements undo down in the virtual machine: the glulxe interpreter lists @hasundo and @discardundo among its opcodes.
• In Fabledrift, stepping back is free, always; retelling is free on the Apprentice and once a day on the other two narrators.

What does undo in AI story games actually do?

It depends which of four operations the button is wired to. The labels vary between apps — undo, rewind, retry, erase, alter — but the operations underneath are stable, and they are not interchangeable. What separates them is not how far back you travel. It is what the story is permitted to remember once you arrive.

Action	What changes on the page	What should change in memory	What it costs you
Step back	You return to an earlier scene you read	Everything after that scene is forgotten	Nothing; those words were already yours
Retell	The newest scene is replaced	That scene’s events drop out, earlier ones stay	A scene you will never read again
Edit	You rewrite part of the text yourself	Facts must be re-derived from your wording	Authority; the prose is now partly yours
Restart	The branch ends and a new story begins	The record is cleared	The whole story

The grid is the whole argument in one picture. Two of these actions move the boundary of the story backward. Two of them leave the boundary alone and change what sits at its edge. An interface that spells them all “undo” is asking you to guess which one you just pressed.

Why stepping back is not the same as retelling

One is a bookmark; the other is a second draft. Step back and you land on a scene you have already read, so the story goes forward from words you recognize. Retell and you throw away the scene you just finished to ask for a different one from the same moment. The text that comes back has never existed before, in your story or anywhere else.

That is where a generated story parts company with a saved game. A save restores a state and the world plays forward the same way. Ink, inkle’s scripting language for interactive narrative, shows the clean version: a story’s state is written out with state.ToJson() and restored with state.LoadJson(savedJson). Restore the state, get the same story.

A narrator that composes each scene at the moment you act cannot promise that. You can return to the same state and still receive a different next scene, because the scene is written after you arrive rather than retrieved from a file. The snapshot is the easy half of the problem.

Classic interactive fiction has had the easy half solved for decades, and solved it below the story entirely. Glulxe, an interpreter for the Glulx virtual machine, lists @hasundo and @discardundo among its opcodes, and its release notes record fixing a memory leak of undo states. The interpreter keeps whole machine snapshots and hands one back on request. Nothing is regenerated, because there is nothing to regenerate.

What happens to your story’s memory when you undo a scene

The record has to roll back with the text, or the story keeps facts the page has retracted. This is the failure that makes an undo feel broken even when the button itself works perfectly.

Say you retell a scene in which you told a ferryman your name, and the second telling has you keep it to yourself. If the memory still holds she gave the ferryman her name, he will use it three scenes later, and there will be no line anywhere in your story where you said it. Nothing crashed. The story simply knows something it was never told.

The two ways it goes wrong

• The record runs ahead of the text. Events from discarded scenes stay on file. Characters remember conversations you did not have; objects you never picked up show up in your hands.
• The record falls behind the text. The rollback overshoots and drops facts established before the point you returned to. The narrator suddenly cannot name the person you have traveled with since the opening.

Both are bookkeeping failures, not writing failures, which is why undo belongs to the memory layer rather than the interface. In Fabledrift, an interactive fiction app for Android, every scene is composed live from a structured record of what has happened so far, so stepping back means rewinding that record to the exact state it held when you first read the scene you returned to. The mechanics of a single turn are in how an AI narrator writes a scene.

Is undo just save scumming for readers?

Not really, because there is nothing to reroll. Undo in AI story games has no fixed outcome waiting behind it. Save scumming in a role-playing game means reloading until a fixed system — a lock pick, a speech check, a loot table — lands the way you want. The outcome exists before you reload, and you are buying attempts at it. A generated scene has no dice underneath it.

So what comes back the second time is not a better roll. It is different prose about the same moment, drawn from the same record, and it may well be worse. That makes retelling a poor instrument for getting your way and a good one for fixing an error. The distinction is worth holding on to, because it decides how often you should reach for the button.

There is still a cost, and it is not measured in credits. Consequence is the only thing that makes a choice weigh anything, and a story you can revise indefinitely stops asking you to decide. Readers who come from tabletop play know this tension already; we sorted through it in solo RPGs versus AI story apps.

Which button to reach for

Match the action to what actually went wrong.

What went wrong	What to press	Why
The scene contradicts something established	Retell	The error is inside that one scene
The narrator misread your move	Retell, then rewrite the move plainly	The scene answered a different question
Your own decision was the mistake	Step back	The error is upstream of the newest scene
The scene is fine but not what you pictured	Leave it	Surprise is most of what you came for
You want a different story altogether	Restart	Nothing smaller will fix it

The fourth row is the one readers skip. A scene that is merely unfamiliar is usually the story working, and retelling it trains you to file down every edge until the whole thing is smooth and forgettable.

In Fabledrift, stepping back to your own earlier scene is free, always, because returning to something you have read should never be a purchase. Retelling is free on the Apprentice and once a day on the Chronicler and the Oracle; beyond that a retell costs that narrator’s price, shown on the button before you tap it. The arithmetic behind those numbers is in what a story credit actually buys.

A reader’s rule for the back button

Use step back for your own mistakes and retell for the narrator’s. Your move was the thing you controlled, so an error there is upstream and wants distance; the scene was the thing the narrator controlled, so an error there wants a second attempt in place. Almost every confused use of undo in AI story games comes from applying one remedy to the other’s problem.

Then leave the button alone. A story that remembers what you did is only interesting if what you did was allowed to stand, and the reader who retells every scene until it flatters them ends up holding a very smooth story about nobody in particular.