Every long story goes off the rails at some point. What decides whether it recovers is what you do in the next thirty seconds.

The one rule: fix it now, don't play past it

Everything the AI writes becomes part of what it reads next. A scene you didn't like is not a one-off — it goes into the story, gets summarised, and is fed back in on every following turn as an example of how this story goes.

So pressing Continue past a bad scene doesn't move on from it. It endorses it. The next scene is written by a model that has just been shown that this is the kind of thing you want, and the one after that is worse. Two hours later the story feels broken and the cause is fifteen scenes back.

Note: think of it as keeping the story clean. The text in your story is the instruction manual for everything that comes next, so anything you leave in there is something you're asking for more of.

What to do instead

In rough order of how much they cost you:

1. Redo the scene. Costs one generation. Fixes most things — a bad roll, an odd tone, a character acting out of character.
2. Edit the response. Free. Often better than a redo: trim the paragraph that went wrong, fix the name, cut the invented event. The edited version is what gets carried forward.
3. Redo with more direction. Add a line to your input saying what should happen, then regenerate.
4. Fix the summary. If the problem already made it into a summary, the scene isn't the issue any more — the memory is. See Memory & Summaries.

Repetition — the AI keeps restating the last scene

Easily the most-reported problem, and usually the same cause: the model has been given a stretch of story where not much changed, so the most probable next thing is more of the same.

• Give it something to react to. A blank Continue asks the AI to invent momentum from nothing. A sentence of input — a decision, a question, a movement — nearly always breaks the loop.
• Don't Continue through repetition. Each repeated scene makes repetition more likely next turn. Redo instead.
• Try a different model. Some models are far more prone to it than others.
• Check your recent scenes. If the last four all end on the same beat, the pattern is in the context and the model is copying it.

The story drifts, invents events, or jumps around in time

Usually a memory problem rather than a writing problem. The AI can only hold so much at once — recent scenes in full, older ones as summaries.

• Read your summaries. If they're wrong or vague, the AI is working from a bad record and nothing it writes will be consistent. Fix them.
• Raise Memory Length if you want more recent detail kept — bearing in mind it costs more per turn.
• Correct contradictions as they appear. Two conflicting facts in the context will keep producing conflicting scenes until one of them is removed.

Characters getting muddled together

If two characters have the same or similar names, the AI will merge them — attributing one's actions and history to the other. It has no way to keep them apart.

• Rename one of them. Make the names clearly distinct, not just different.
• Write the difference into their memories — who they are, and how they relate to each other.
• Watch for this with auto-generated characters especially, where names can collide.

The story switched language, or the style changed

Say so in your input and regenerate. If it keeps happening, put the instruction in your story prompt instead — that's read on every turn, so it holds where a one-off note won't.

When it's really tangled

If a story has drifted badly over many scenes, redoing the last one won't recover it, because the problem is spread through the context and the summaries. Two things actually work:

• Rewrite the summaries to describe the story you want to be in. That's the record the AI works from, and it's fully yours to edit.
• Export first, then experiment freely. A .drsf file means you can be bold about cutting things without risking the version you liked.