How to Hide a Visual Novel’s Dialogue Box Without Missing a Line
Before hiding the dialogue box, lock the current line and text progress, then set separate rules for voice playback, scene animation, and auto-read. A completed restoration card and an observatory walkthrough define what may continue while readers view the artwork—and why the input that restores the box must never advance the story as well.
Introduction
When hiding the dialogue box to view the artwork, it is advisable to pause line-by-line reading too: preserve the current line and visible text, suspend automatic advancement, and make the restoring input show the box only. Set separate rules for voice playback and background animation; neither should simply carry on because the text is hidden. Once the box returns, let readers recognize the original line before explicitly choosing whether to resume auto-read.
The observatory scene below is an original, fictional teaching example, not a real user case, a tested result, or a description of DramaFork features. Its buttons, states, and behaviors are design agreements awaiting implementation.
1. Treat Hiding, Pausing, and Restoring as Three Separate Decisions
Hiding removes an obstruction. Pausing protects the reading position. The restoring input determines what happens next. “Click an empty area to hide; click again to restore” says nothing about whether the story keeps moving.
In this example, a character is saying, “Once the clouds clear, you’ll see the brightest star beside the telescope.” Only “Once the clouds clear,” has appeared when the reader decides to view the whole night sky. Before hiding the box, auto-read is on, the voice is playing, thin clouds are drifting, and the character has yet to raise a hand to point out the star.
Set one firm boundary: while the artwork is being viewed, the story must neither enter the next line nor pass a key narrative action in the current line that has not yet been presented. Otherwise, even if the same text returns, the character may have finished pointing and the camera may have moved away. The reader has still missed the context needed to understand the line.
On entering artwork-viewing mode, first block advancement, then capture the line position, text progress, and playback states together, and finally hide the box. If automatic advancement and hiding arrive simultaneously, this design gives hiding priority. If the line change has already completed when the hide request arrives, record the new line. The saved line position and onscreen text must refer to the same line.
2. Fill Out a Dialogue Box Hide-and-Restore Card
The line position must distinguish the chapter, branch, and specific dialogue line. Saving only the text is insufficient: identical words can occur in different places. Text progress records how much has appeared, separately from whether the whole line has been read.
| Card field | Completed rule for the observatory |
|---|---|
| Line position before hiding | The star-pointing line in the observatory’s first observation sequence; restoration must return here |
| Text progress | “Once the clouds clear,” is visible; stop revealing text while hidden and initially preserve this progress when restored |
| Auto-read | Record that it was on; pause it when hiding and invalidate this line’s existing advancement countdown |
| Voice handling | Pause and record the playback position when hiding; remain paused after the box returns, awaiting a continue command |
| Scene animation handling | Continue non-narrative star twinkling; pause cloud movement and the hand gesture pointing out the star |
| Restoring input | Neither the press, release, nor hold-generated repeats may advance the story; accept fresh input only after release |
| Choice after restoration | “Continue this line” keeps reading manual; “Resume auto-read” explicitly enables automatic reading again |
Cloud movement counts as narrative animation here because whether the clouds have cleared matters to the dialogue. Being “part of the background” is not enough to justify letting it continue. Clouds that serve only as decorative loops unrelated to the plot in another scene may follow different rules.
When reusing the card, specify for every field what is recorded before hiding, what may change while hidden, and when it may continue afterward. Timed choices, camera cuts, and new dialogue triggers absent from the table also need explicit classification. Under this design, pause an unclassified event, complete its rules, and then decide how to handle it.
3. Handle Voice and Animation According to the Information They Convey
Pausing voice playback preserves the listening position, but resuming halfway through a word can sound awkward. If the project cannot reliably resume from the saved position, an alternative is to stop the voice and offer “Replay this line” after restoration while retaining the original text progress. Readers will hear the first part again; the restoration message should explain that trade-off.
Another option is to let the current voice line finish while keeping the line position locked. This suits a mode that explicitly allows listening while viewing the artwork. It no longer guarantees that voice playback remains at its pre-hide position, so restoration should indicate that the voice line has finished and allow replay. Voice completion must not authorize advancement to the next line while the box is hidden.
Background music and star-twinkling loops that convey no new information may continue to sustain the atmosphere. Character exits, appearing props, changes of expression, and camera movements that direct attention to clues should pause. Ask whether a reader who sees only the eventual state will still understand what just happened.
If voice, lip movement, and camera movement must follow the same timeline, pause or replay them together. Freezing them separately can leave the voice speaking while the character is motionless. For an indivisible scene sequence, artwork-viewing mode may instead remain unavailable until it ends, but the entry point should explain the wait.
4. Walk Through the Full Interaction to Check for Missed Lines
First, the reader hides the box after “Once the clouds clear,” appears. Follow the card: lock the star-pointing line, pause text reveal, voice playback, and thin clouds, and keep the stars twinkling. The fact that auto-read was previously on remains recorded, but it currently has no permission to advance.
Second, the reader stays to view the artwork. However long they remain, do not accumulate line-advance tasks to execute immediately on restoration. Catching up on advancement afterward would make the pause merely cosmetic.
Third, the reader clicks the night sky. The box returns with the original “Once the clouds clear,” and a “Reading paused” message. This click neither completes the text, starts the voice, nor moves to the next line. Even if the reader keeps holding, subsequent repeat inputs must not pass through the restoration process.
Fourth, after releasing the input, the reader selects “Continue this line.” Text resumes appearing from its saved position; the voice and thin clouds resume under this example’s rules, and the pointing gesture occurs only at its originally scheduled point. Auto-read stays off. Once the full line is visible, a fresh advance input takes the reader to the next line.
If the reader instead chooses “Resume auto-read” in step four, continue the current line first. Once it meets the original conditions for being finished, start a complete waiting interval anew. Do not reuse a countdown that was almost exhausted before hiding. That extra explicit choice lets readers confirm when they are handing advancement control back.
5. Test Against Failure Cases and Define the Scope
Acceptance checks should cover at least three moments for hiding: before all text appears, after all text appears but before the voice finishes, and just before auto-read advances. Each time, check the restored line position, text progress, voice state, and effect of the first fresh input. These are expected outcomes on paper, requiring verification after implementation; they are not passed test results.
Also hide and restore twice in succession. The second hide must capture the progress at that moment, not reuse the first snapshot. Then repeat the interaction with clicks, keyboard shortcuts, and touch, checking whether restoring accidentally completes the text or activates an underlying choice. If only mouse input can restore safely, the input rules are still incomplete.
Three common failures are hiding only the visuals while lines keep advancing, immediately catching up on the countdown when the box returns, and using one click both to restore and advance. They require line-position locking, correct handling of paused tasks, and isolation of the restoring input respectively. An extra explanatory message alone cannot fix them.
This card applies to scenes built around line-by-line reading that permit a temporary pause to view the artwork. Real-time, time-limited story sequences and continuous footage that cannot be paused need separate agreements about whether time keeps running; they cannot simply promise a return to the original progress. Deliver the completed card alongside the interaction expectations above so designers and implementers can check, item by item, what “continue reading the same line” actually entails.
