Here’s a pattern I bet a lot of you know. Your character finds out their closest ally has been lying to them. Huge moment. And by the end of that same scene, they’ve confronted the ally, had the tearful conversation, forgiven each other, and moved on. Three sessions’ worth of story, squashed into fifteen lines.
I’ve been roleplaying with AI pretty much daily for about three years, and for a long time this was my biggest frustration. It wasn’t memory or prose. It was pacing. Everything got introduced and resolved in the same breath.
The reason is pretty simple once you see it. These models are trained to be helpful, and helpful means solving problems. In a coding task, that’s great. In a story, it means every conflict gets fixed the moment it shows up, so nothing ever builds.
Here’s what fixed it for me, roughly in order of how much it helped.
1. Name the threads that stay open
This one surprised me most, because it’s so simple. Before a scene (or as a standing note), say out loud which threads are supposed to stay messy:
The tension between Mira and Kael stays unresolved in this scene. They're still circling the issue. The mystery of the missing letters should deepen, not get answered. This scene is about suspicion growing. The confrontation comes later. If you don’t tell the model to leave threads open, it’ll tie them all up. When you do tell it, it respects that surprisingly well. I think of it as a short list of things that should stay unfinished.
A standing version I keep in my main prompt:
Unresolved tensions carry over between scenes. A scene should usually end with more tension than it started with, not less. 2. Complicate instead of resolve
This one comes from screenwriting and transfers perfectly. Every scene should make things worse or make them different. The question you ask changes from “how does this get fixed?” to “how does this get more complicated?”
When a problem comes up, add a complication rather than a solution. If my character tries to fix something, it partly works but creates a new problem. After I added this, problems stopped evaporating. They evolved, and that’s where the story lives.
3. “Yes, but” and “No, and”
Stolen from improv and tabletop games. When your character attempts something:
- Yes, but: it works, but something goes wrong or something new surfaces.
- No, and: it fails, and something else gets worse too.
Plain “yes” and plain “no” are dead ends. These two generate the next scene for you.
When my character takes action, respond with "yes, but" or "no, and" consequences. Clean success or clean failure should be rare. If you only add one line from this post, make it this one. It’s done more for my pacing than anything else.
4. Tell the AI what phase of the story you’re in
The model has no idea whether you’re in act one or act three. Every scene starts at the same emotional baseline, which is why stories feel flat even when individual scenes are good. You have to be the architect here. AI is a great builder and a terrible planner.
It doesn’t need a full outline, just the temperature of the story right now:
We're in the early phase. Conflicts are emerging but nobody confronts them yet. Keep things simmering. We're near the midpoint. Tensions surface and alliances get tested. We're building to the climax. Everything should feel like it's converging. I keep one line like this as a persistent note and update it whenever the story moves. That’s why I put a “story state” note into Tale Companion (the platform I built) that the AI reads before every reply, and the phase line lives there for me. But you can do exactly the same thing in an author’s note, a pinned message, or just at the top of your next message in any app.
5. Plant seeds, pay them off later
Good writers set things up long before they pay off. AI almost never does this on its own, but it’s happy to when you ask:
Include a small detail in this scene that could matter later. Have someone mention something offhand that connects to the bigger plot. Then, chapters later: “Remember the broken clock in the tower from the first chapter? It matters now.” Suddenly the story feels like it was planned all along, even though it wasn’t. Write the seeds down somewhere outside the chat, because they won’t survive a long context on their own.
6. Vary the tempo
Pacing is about variation as much as speed. All fast is exhausting, all slow is boring. Tension is the inhale and release is the exhale, and you need both.
This scene is a breather. Slow, character-focused, no plot movement. Now things speed up. Short sentences, quick cuts. This conversation should feel long and uncomfortable. Don't rush to the point. The rhythm I use in a lot of my setups is one quiet character moment for every loud action one. After a big fight, I’ll ask for a campfire scene. After a calm stretch, I let things ramp up again. The contrast makes both land.
Bonus: protect the scenes you’re actually here for
Pet peeve of mine: AI loves cutting away from bonding moments to get back to “the plot.” If those moments are the point for you, guard them:
Stay in character bonding moments until I move us to the next story beat. A quick test
Look back at your last few scenes and count how many conflicts were introduced and resolved in the same scene. If it’s most of them, the story is sprinting when it should be jogging.
Next session, protect just one thread. Let it sit. Let your characters carry it into the next scene without talking about it. That alone changes how the whole story feels.
Curious what others do here. Does anyone have a good way to stop the model from rushing slow-burn romance or mystery plots? Those are the two where I still have to keep my hand on the brakes the most.
submitted by /u/Pastrugnozzo
[link] [comments]