Metlivi Blog

How to Check Dialogue Reading Controls Before You Buy a Story Game

If you want to read at your own pace, check whether you can advance each line manually, whether text can appear instantly, and whether auto-advance can be turned off. Verify story dialogue and cutscenes separately, then confirm that the instructions apply to your exact platform, edition, and language. Subtitles alone tell you that text is displayed; they do not establish who controls when it moves on.

September 30, 20264 min readLeisure, Travel & City ExperiencesBy Metlivi Editorial Team
Section 1

Separate the controls that affect reading pace

Games may offer several controls that sound similar but solve different problems:

The distinctions are practical, not just labels. Ren’Py’s official documentation treats text speed, auto-forward behavior, and dialogue history as separate features: its [preference documentation](https://www.renpy.org/doc/html/preferences.html) describes text speed and whether a click continues auto-forward, while its [dialogue history documentation](https://www.renpy.org/doc/html/history.html) explains the history screen. These document engine capabilities; an individual game may configure or omit them.

**Text reveal speed** sets how quickly characters appear on screen. Instant or “complete text” display can remove the typewriter effect, but it does not necessarily advance to the next line.
**Manual advance** means a button press displays or moves past the current line. Check whether the same input first completes a partially revealed line and only then advances; those are two separate actions.
**Auto-advance** moves dialogue forward without a new press. Look for an off setting, and check whether it can be limited to voiced lines or adjusted for unvoiced text.
**Timed choices** may close or select an option after a countdown. That timer is different from the pace of ordinary dialogue, so look for evidence about both if pausing to read choices matters to you.
**Dialogue history** can let you reread recent lines, but it does not slow the scene or guarantee that every line is retained.
**Scene replay** revisits a complete scene or cutscene. It may be useful for a missed moment, but it is not the same as a line-by-line history log.
Section 2

Check story dialogue and cutscenes independently

A general settings menu may govern ordinary conversations but not cinematic scenes. Search the game’s official manual, support site, or developer FAQ for both “dialogue” and “cutscene,” then note which feature each page actually describes. Do not infer that one control applies everywhere.

Final Fantasy XIV offers a useful example of why this matters. Its official UI guide has a page specifically on [toggling text auto-advance during cutscenes](https://na.finalfantasyxiv.com/uiguide/faq/faq-other/setting_cs_av1.html), with separate instructions for keyboard and controller. A second page explains how to [enable auto-advance for voiced dialogue only](https://na.finalfantasyxiv.com/uiguide/faq/faq-other/setting_cs_av2.html); the guide also describes adjusting the speed for unvoiced dialogue. This is evidence for the features and inputs documented for FFXIV, not proof that another game—or another platform version—works the same way.

For the game you are considering, make a small checklist: ordinary conversations, voiced cutscenes, unvoiced scenes, and choice prompts. For each, record whether you found evidence for manual advance, instant reveal, auto-advance control, and a timer. Mark anything undocumented as unknown rather than assuming the setting carries over.

Section 3

Verify the exact release and input method

Controls can vary across PC, console, handheld, remaster, and regional release. Prefer instructions that name your platform and edition. If the source lists keyboard and controller inputs separately, use the directions for your device; FFXIV’s guide, for instance, gives different input directions for keyboard and console controls on its cutscene settings page.

Section 4

Check language-specific documentation and unresolved questions

Localization can matter too. A feature described in one language’s guide is not automatically confirmed for every localized edition. Search the publisher’s page for the language you plan to play, and check whether the relevant menu label appears in that version. If there is no matching documentation, treat localization-specific labels and availability as unverified.

When official material is silent, ask a focused question in a publisher or developer support channel: “On [platform], in [edition/language], can I turn off auto-advance and manually advance every dialogue line during both voiced cutscenes and regular conversations?” This prompts a specific answer instead of a broad “Does it have subtitles?” If only a store description or user comment is available, it may help you find a lead, but it does not confirm a control for your exact release.

Section 5

Use a purchase decision rule

Write down the feature you actually need before researching. For example: “I need to stop every scene and advance each line manually, and I want text to appear instantly.” Then accept only evidence that answers both parts and covers the relevant scene type and platform.

If manual control is essential and official documentation does not address cutscenes or your platform, treat that point as unknown before buying. If instant text is the only requirement, search specifically for a text reveal or text speed setting; evidence of manual next-line input does not answer it. Keep timed choices separate in your decision: a game may let you control dialogue pace while still placing a countdown on choices.

Related reading

Keep exploring this topic