Home / Glossary / Pacing

Concept

Pacing

The rhythm of a scene: how fast beats land, when tension rises, when to linger and when to skip. Almost always worse by default than it should be.

Every model is trained to be helpful, and helpfulness often manifests as rushing toward a resolution. The result: scenes pay off their tension three messages after it's established. First-time AI roleplayers complain about this constantly: "we were flirting and then suddenly we were having sex and it didn't feel earned."

Fix it by instructing the model to match your pace. If you write 3 lines, write 3-5 back. Don't escalate unless I escalate. Let tension build. Don't rush to payoff. These instructions are simple and they work.

Time jumps are the other pacing tool. Explicit "skip to next morning" beats trying to roleplay through hours of small talk. Most models handle explicit time jumps cleanly. They fail only when left to implicit ones.

Prompts that use this concept

Pacing controller

Every model is trained to be helpful, which manifests as rushing scenes toward their payoff. Explicitly instructing the model to match pace prevents the classic 'we were arguing and now we're making out three sentences later' failure.

Long roleplay suffers from pacing issues: every beat gets dramatized. Explicit time jumps let you move through uninteresting periods. Most models handle this cleanly if you tell them explicitly rather than fading to black and hoping.

Length controller

Default assistant behavior is verbose because RLHF rewards longer responses. Instructing length-matching overrides this and produces the call-and-response rhythm that real roleplay needs. Padded responses are the #1 complaint in Janitor/SillyTavern communities.

Quiet-beat pivot

Every model over-dramatizes because drama correlates with engagement in training. Quiet beats are where intimacy lives but models skip past them. Explicitly mandating a quiet beat, with a word limit, produces the slow-scene texture long roleplay desperately needs.

Intimacy-build tension

Models rush to resolution because payoff is rewarded in training. Explicit 'build one notch, don't resolve' instructions counteract this and produce the slow-build texture that defines good intimacy scenes. The 'give me the next move' hand-off also re-establishes the user's turn, preventing model-drives-everything drift.

Related concepts

Roleplay framing Scene priming

Put this into practice

Our prompt library shows these techniques in real, copy-ready prompts, tested across 22 AI companion apps.

Browse prompts →