# Keep a scene moving without forcing the player

**Scene motion** means a relevant change in a task, conversation, choice, information, or consequence. It does not require a crisis, constant conflict, a new NPC, or a relationship increase. A calm scene can remain useful while someone reads, works, rests, reflects, or shares a silence.

Use a practice chat and keep the last accepted scene available. Mira is the adult archivist; Rowan is an adult courier. Decide whether one narrator portrays both or they are separate native group respondents. That choice affects how you provide cast records and select who answers.

## Plan a small situation

Copy this into local notes and replace the brackets. It is a worksheet, not a native import or executable engine.

```text
Current place and established time: [replace; leave unknowns unspecified]
Present cast and communication channels: [replace with actual scene facts]
Current task or open question: [replace with one useful issue]
Character's own goal: [replace with an established motive or task]
Available information or objects: [replace with what actually exists]
Relevant obligation or consequence: [replace, or omit]
What the character can do independently: [replace with a plausible option]
Which player decision remains open: [replace without completing it]
If repetition develops: [replace with one existing thread to revisit]
```

Choose a small number of relevant pressures. An unfinished address check is enough for a first scene. Do not add a deadline, hidden room, phone call, or stranger solely because the worksheet has room for one.

## Copy only the relevant block

The following original practice setup belongs in **Scenario**. It describes an opening; it is not a permanent instruction to restart every scene there.

```text
Late afternoon at the archive. Mira is comparing two street names on parcel A17's
address card. A17 remains sealed on the counter. No delivery has been accepted
and no receipt has been issued. Rowan is expected but has not arrived.
The traveler may investigate, ask questions, decline the delivery, or suggest
another approach. Mira can consult available records and explain uncertainty
without deciding the traveler's response.
```

These short continuation rules belong in **ED**, or in that chat's **Custom Instructions** for a trial. Choose one maintained destination and merge with an existing behavior base instead of stacking engines.

These destinations follow the documented [character-field roles](https://guide.ourdream.ai/characters/story-and-personality) and [persistent versus temporary instructions](https://guide.ourdream.ai/chat/personas-and-instructions). The scene-motion wording below is an original suggestion to test, not a documented native control.

```text
Continue from the latest accepted scene and preserve compatible earlier facts.
A quiet or slow scene is valid; a short user reply alone does not require escalation.
If the exchange repeats without useful change, pursue one plausible existing task,
question, obligation, or consequence. If none fits, allow a pause or natural ending.
Leave the player's choices, movement, dialogue, and private state to the player.
Keep each person's knowledge tied to what they actually learned.
```

Distinguish an invitation from acceptance and a journey's start from arrival. A call or message does not put its sender physically in the room. An offscreen plan is not a completed background simulation. Preserve relevant object locations, elapsed time, and unresolved consequences; recover unknown state explicitly rather than guessing.

These are writing requirements to inspect. A source label such as “resolver” or “LAW” does not install a scheduler, native transaction, or private memory. If using actual State Trackers, configure and inspect their real controls separately.

## Replace compulsory escalation with a bounded next step

`Always advance the plot and never let the scene stop` can conflict with a scene that must wait for the traveler's choice. A more specific original ED or Custom Instructions trial is:

```text
If the address discussion repeats, Mira may inspect an available register entry
or explain which evidence is missing. Describe that step and its actual result.
Stop before choosing the traveler's route or completing the delivery for them.
```

After the user replies `Okay.`, inspect whether the model uses an established resource without inventing the user's departure. A useful next step can end with an observation rather than a compulsory question.

For a one-reply change, an available command could be `/direct Have Mira compare the two existing street names aloud, then leave the route choice open.` Do not save that single comparison as an instruction to repeat indefinitely. The persistent/temporary distinction is documented in [Personas and instructions](https://guide.ourdream.ai/chat/personas-and-instructions).

## Four proposed checks

All four are **not run**. Keep the same setup and record actual outcomes.

| Input or fixture | Observable criterion |
| --- | --- |
| `I read the index in silence.` | Quiet work remains valid without an unrelated emergency, forced praise, or invented player action. |
| After two replies repeat the same address question: `We have discussed the address twice. What can you check next?` | Mira can use one established source or explain the missing information, rather than spawn random drama or complete the delivery. |
| `I start walking toward the records office.` | Starting travel does not silently complete arrival, entry, handover, and receipt; time and choices remain coherent. |
| Establish that Rowan is absent and sends only `The bridge is closed.` Then ask `What can Mira know from that message?` | Mira has the report, not Rowan's unseen observations, private thoughts, or physical presence; uncertain information remains qualified. |

A question is one possible reply ending. An observation, action, offered object, or unresolved situation can also leave room to respond. If the model loops, revise one cause and retest instead of adding a compulsory event every turn.

Continue with [Scenarios and greetings](../tutorials/09_Scenarios_Greetings_and_Worldbuilding.html), [NPCs](../tutorials/26_NPCs_and_Supporting_Cast.html), or [Testing](../tutorials/23_Testing_and_Troubleshooting.html).