When a Player Chooses Silence: How an AI Character Can Keep the Scene Moving
When a player says nothing, an AI character should preserve what has already happened, let the silence register, and offer a clear next action the player can take—or leave untaken. It should not invent dialogue for the player, treat the pause as a timed failure, or claim to know what the player feels. This guide focuses on designing that response in a fictional game scene.
Treat silence as an authored state, not missing input
A silent response is still a scene state: the player has not supplied new dialogue, but everything established before the pause remains true. The character may still be waiting, the door may still be open, and the clue the player found remains in their possession. Keep those facts intact while deciding how the scene can continue.
This follows a broader principle of interactive narrative: a player's agency is shaped by the actions and story impacts a game makes available through its design. Silence need not create a new plot branch to be respected; it can leave the current situation open for the player to direct. Bettina Bodi and Jan-Noël Thon, “Playing stories? Narrative-dramatic agency in Disco Elysium (2019) and Astroneer (2019)” describe narrative agency in terms of the player's meaningful impact on the unfolding story.
For the writing or dialogue system, represent silence as a valid outcome that carries forward the existing scene state. It does not need to imply a motive such as disagreement, fear, confusion, or refusal. Those are possible interpretations in a human conversation, but the game cannot infer which one applies from silence alone.
Let the character acknowledge the pause without filling it
A character can respond to what is observable: the player has not answered. Keep the acknowledgment brief and grounded in the moment. For example, in a fictional scene where a ferry keeper asks which crossing the player wants, a suitable response might be: “The keeper rests a hand on the timetable. ‘Take your time. The east pier is open.’” The line acknowledges the pause and supplies a scene fact; it does not assign an emotion or put words in the player's mouth.
Avoid turning silence into an answer. “You nod, agreeing to help” changes the player's action. “You must be worried” assigns an inner state. Even a line such as “I see you don’t trust me” can impose a relationship judgment that the player never chose. If the character needs to interpret the lack of a reply, frame that as the character's uncertain perspective—“He glances toward the open gate, then waits”—and keep the interpretation reversible.
Offer one readable way forward
After a short acknowledgment, show what the player can do next. The scene can remain available for a reply, an observable action, or a decision to leave. Make the options fit the location and current story state, rather than presenting a generic prompt detached from the fiction.
In the ferry scene, a compact set of options might be:
Ask about the crossing.
Walk to the east pier.
Wait or say nothing.
Leave the landing.
The exact actions depend on what the game supports. If walking away is not possible in the scene, do not offer it as a fake option. Likewise, do not label “say nothing” as consent, refusal, or a relationship choice unless the player later makes that choice explicit.
Research on interactive story choices offers a useful design check: in a study of 88 participants, choices that differed in situational content were associated with a higher reported sense of agency than choices differing only in non-situational ways. Applied here, an optional action should describe a real difference in what the player can do or what situation they enter, not a cosmetic rewording of the same forced response. Cardona-Rivera et al., “Foreseeing Meaningful Choices”.
Preserve state before generating the next line
Before producing a response, identify the scene facts that silence must not erase: who is present, what each character knows, which options remain available, and whether any already-established event changes independently of the player. Then generate a line that fits those facts and returns control to the player.
A practical sequence is:
Read the current state. Retrieve the characters, location, known facts, unresolved question, and available actions already in the scene.
Record no new player action. Silence does not update the player's dialogue, commitment, inventory, relationship state, or intention.
Choose a proportionate response. Use a brief pause, a small character action, or an environmental detail. Avoid introducing a new event solely to force a reply.
Offer supported actions. Present only continuations the game can actually honor, and retain the option to remain silent where appropriate.
Wait for a new action. Continue from the same authored state until the player does something that changes it.
This sequence is a design recommendation derived from the statefulness of interactive narrative systems; it is not a claim that any particular engine enforces these rules. In ink, for example, authors can separate a displayed choice from the text that appears after it is selected, and its documentation discusses tracking story state to maintain continuity. That provides a concrete implementation model: keep the choice and its consequences explicit, so the continuation follows a recorded action rather than an assumption. inkle, “Writing web-based interactive fiction with ink” and inkle, “Writing With Ink”.
Keep authored consequences distinct from invented motives
Sometimes the world must change while the player is quiet: a scheduled train departs, a shop closes, or another character leaves because the scene established that event. If so, communicate the rule in context and apply it consistently. Do not smuggle in a consequence that the player could not reasonably understand from the scene, such as silently worsening a relationship or making an irreversible choice on their behalf.
Where time passing is not part of the established fiction, silence can remain a readable pause. Where time does matter, distinguish an event caused by the world from a choice attributed to the player. “The last ferry pulls away at dusk” describes the world. “You decide not to board” authors a player decision. Those sentences describe different causes and should not be treated as interchangeable.
Use a small continuation pattern
A useful authored pattern has three parts: acknowledge, preserve, offer. Acknowledge the observable pause; preserve the scene facts and the player's unmade choice; offer one or more supported next actions. For the ferry keeper, that could read: “The keeper checks the timetable. The east crossing is still running. You can ask about it, head to the pier, wait, or leave.”
This pattern is a practical synthesis, not a formula proven by a single study. Its value is that it gives writers and system designers a quick review question for each generated continuation: Did the response keep the scene coherent while leaving the next meaningful action with the player? If the line answers for them, assigns them a feeling, or removes options without an established cause, revise it.
Review the response against the scene
Before using a silent-state line, check it against four questions:
Does it preserve the current location, participants, knowledge, and unresolved choices?
Does it describe observable behavior rather than claim to know the player's feelings or intention?
Are the offered actions supported by the game and meaningfully distinct in the scene?
If the world changes during the pause, was that timing established and is its consequence clear?
A strong continuation does not need to make silence dramatic. It needs to make the pause legible, keep the authored state coherent, and leave the player's next action genuinely open.