A route lock in a visual novel is a condition that prevents a specific route from being accessible until certain requirements have been met. The locked route does not appear as an option, or appears greyed out, or simply cannot be reached through any combination of in-game choices, until the reader has satisfied whatever the developer specified as the unlock condition. Once those conditions are met, the route opens and becomes available to play.
Route locks are one of the most consequential structural decisions in visual novel design. They shape the order in which readers experience content, control when major narrative revelations become accessible, and determine whether certain routes feel like rewards for engagement or arbitrary obstacles. Understanding how they work and why they exist makes you a better informed reader and a more deliberate developer.
Why Route Locks Exist
The VNDev Wiki on branching structures explains that a developer may want the reader to experience routes in a predetermined order, and that any game with an unlockable true route has an enforced order. That sentence contains the most important reason route locks exist: narrative structure requires it.
Visual novels with multiple routes tell their stories across all routes collectively, not within any single one. Each route contributes information, emotional context, and character understanding that later routes depend on. A true route, the final route that reveals the full picture of the story’s central mystery or theme, only works if the reader arrives at it having already experienced what came before. If the true route were accessible from the beginning, the revelations it contains would arrive without the foundation that makes them land.
This is not a technical limitation or a commercial trick to extend playtime. It is a narrative design decision equivalent to a novelist choosing to reveal a crucial backstory only after the reader has spent two hundred pages with a character. The emotional payoff depends on the order of delivery.
Route locks also serve a second purpose. They introduce readers to simpler routes before more complex ones, using accessible entry points to build familiarity with the game’s world and characters before placing those characters in the more demanding context of a true route. The VNDev Wiki describes the true route as usually revealing important plot points that connect all the characters together, which means it can only function correctly if the reader already knows those characters.
The Types of Route Lock
Route locks come in several distinct varieties, each with different trigger conditions and different implications for the reader’s experience.
Completion-Based Locks
The most common type of route lock requires completing one or more other routes before a specific route becomes available. This may mean completing all other routes, completing a specific subset of routes, or completing any single route from a defined group.
Clannad requires completing all individual character routes before the After Story unlocks. This is one of the most celebrated examples of the completion-based lock as a narrative device: the After Story is not simply an extra chapter but the culmination of everything that came before it, and its emotional power depends entirely on the reader having spent time with each character in their own story. The emotional architecture of the After Story is built on foundations the individual routes lay, and experiencing it without those foundations produces a significantly diminished version of what it is designed to deliver.
Little Busters follows the same pattern. The Refrain route, which is considered the true ending of the game, only becomes accessible after all individual heroine routes have been completed. The Steam discussion thread on Clannad’s route structure notes that Air required all three routes before the next opened up and when that was finished the final route opened, confirming that Key’s pattern of using completion locks for true routes spans multiple titles and has been a deliberate structural choice throughout the studio’s history.
Fate/stay night gates its third route, Heaven’s Feel, behind completion of the first two routes, Fate and Unlimited Blade Works. Heaven’s Feel is the darkest and most demanding of the three routes, and the story’s escalating darkness across the three routes is itself a designed experience. Encountering Heaven’s Feel without the context established in the preceding routes would be a fundamentally different and lesser experience of the story.
Single Completion Locks
A lighter version of the completion-based lock requires only one route to have been completed, regardless of which one, before a secondary character’s route becomes accessible. This type of lock typically signals that the newly unlocked character is not the default entry point into the game’s world and that some familiarity with the setting and cast is assumed before their story begins.
The Dracu-Riot guide documents this type precisely: Nicola, one of the heroines, requires the completion of at least one other character’s full storyline before her path becomes available. The guide notes this serves a dual purpose, introducing players to the game’s choice system with more accessible characters first and positioning Nicola’s story as a narrative culmination that ties together elements from other storylines.
Flag-Based Locks
Some route locks do not depend on completing entire routes but on making specific choices at specific points in the story. These are flag-based locks, where a boolean variable is set by a key choice and checked at the route branch point. If the required flag is set, the route becomes accessible. If it is not, the story branches elsewhere.
Flag-based locks can be opaque, because the choices that set the required flags may not obviously connect to the route they unlock. The TV Tropes Guide Dang It page on visual novels documents a well-known example from Katawa Shoujo, where unlocking Rin’s route requires choices that seem disconnected from Rin herself. The page notes that none of the choices critical to unlocking Rin’s route are made in Rin’s presence, nor are they obviously related to anything Rin is interested in or any qualities Rin respects. A reader who does not know this will likely miss the route entirely on a first playthrough.
This opacity is sometimes intentional and sometimes a design flaw. When intentional, it is used to make certain routes feel like rewards for careful engagement with the story rather than accessible through obvious optimisation. When it functions as a design flaw, it creates frustration for readers who cannot understand why a route they are pursuing is not becoming available.
Affection Threshold Locks
Some routes become locked or inaccessible based on accumulated affection values falling below a required threshold rather than a simple flag condition. This overlaps with the affection system mechanics covered in our dedicated article on affection systems in visual novels, but it is worth noting specifically in the context of route locks.
An affection threshold lock means that a route requires not just engagement with a character but sufficient positive engagement. A reader who has made choices that actively reduced a character’s affection score may find themselves locked out of that character’s route entirely, or routed to a bad ending rather than the intended good ending. The Dracu-Riot guide notes that the game actively discourages a neutral or non-committal playstyle, and that consistently switching affection between characters will default the story to a normal ending that resolves the main plot without deepening any romantic relationship.
Information-Based Locks
The Zero Escape series uses a distinctive type of lock that requires obtaining specific information from other routes rather than simply completing them. In Zero Escape: Virtue’s Last Reward, certain routes display a lock indicator when they are reached from an uncompleted direction, and the path forward requires entering a password or code that can only be found in a different route. The reader must explore other branches to gather the information that unlocks the blocked path.
This is a more active form of route lock than simple completion requirements. The reader is not just told to go and complete other content before returning. They are given a specific problem and must find its solution elsewhere in the story’s branching structure. The Zero Escape Wiki describes the flow chart as marking in-game locks and indicating which requirements for unlocking endings are or are not met, making the lock conditions visible rather than hidden. This transparent approach to route locks treats the navigation of the story’s structure as an active puzzle rather than a series of completion prerequisites.
How Route Locks Work Technically
In Ren’Py, the most widely used visual novel engine, route locks are implemented through persistent variables. A persistent variable differs from a regular game variable in that it survives across individual game sessions and save files. When a route is completed, the script sets a persistent flag to true. When the locked route’s access point is reached in a subsequent playthrough, the script checks whether the required persistent flag or flags are true and makes the route available or unavailable accordingly.
The Lemma Soft Forums thread on unlocking secret routes shows the essential structure. A simple persistent route cleared variable is set to true at the end of each required route. At the beginning of the locked route’s access point, a conditional check reads these persistent variables and routes the story accordingly. The forum solution confirms that the approach uses persistent variables rather than regular session variables, specifically because the unlock condition spans multiple separate playthroughs rather than existing within a single game session.
The Visual Novel Maker documentation on variables lists route unlocking as one of the primary uses of persistent variables, alongside affection points and passwords, confirming that this is a standard implementation across the major visual novel development tools.
Route Locks and Reading Order
Route locks impose reading order, which means they have direct implications for how readers should approach multi-route visual novels. Understanding that locks exist and what they require changes the practical experience of working through a title completely.
For a reader’s first playthrough, this rarely matters. The first playthrough of any route should be experienced without guidance, allowing the story to unfold naturally and the route lock structure to reveal itself organically. Most locked routes are locked precisely because they require context that the first available routes provide, so the natural order of a first playthrough already builds toward what the locked route needs.
For subsequent playthroughs aimed at completing the full catalogue of routes and endings, understanding the lock conditions becomes practical. A reader who completes routes in an order that delays the unlock conditions for the true route will have to complete more content before accessing it. A reader who understands the conditions can plan their reading order to reach the true route as efficiently as possible while still seeing all required prerequisite content.
Our article on whether to use walkthroughs for visual novels covers the specific case of unlock conditions in detail, noting that checking a walkthrough for the conditions specifically without reading the route content itself is a reasonable approach when lock conditions are opaque and would otherwise require trial and error across a fifty-hour title.
Route Locks as Narrative Design
The most important thing to understand about route locks is that they are narrative decisions, not merely technical ones. A well-designed route lock shapes the reader’s experience of the story in ways that would be impossible without the enforced order it creates.
When Clannad locks the After Story behind completion of all character routes, it is not withholding content arbitrarily. It is ensuring that every reader arrives at the After Story with the same foundation of understanding, the same emotional investment in the characters, and the same accumulated warmth toward the world the story has built. A reader who reached the After Story on their first playthrough without having experienced Kotomi’s route, or Tomoyo’s, or Kyou’s, would encounter a story that assumes connections they have not built.
The VNDev Wiki states that the true route is usually the canon ending of the visual novel and is considered to be the main story, and that if the visual novel has a sequel, this is typically where it continues from. This status means that the true route must work as a culmination, and culmination by definition requires that everything leading to it has been experienced. Route locks are the mechanism that ensures this requirement is met by every reader who reaches the true route, regardless of how they discovered the game or in what order they might otherwise have explored it.
For developers, this means that route lock design is inseparable from story structure. Deciding which routes require which prerequisites is a question about narrative order, about when information should be revealed, and about what emotional understanding the reader needs before specific content can do its intended work. The lock conditions should reflect the narrative logic of the story rather than being applied arbitrarily.
For readers, route locks are a signal that the story’s architecture has been deliberately designed and that the order of reading matters. When a route is locked, it is almost always locked for a reason that will become clear once the required routes have been completed. Treating the lock as a navigational puzzle to solve reveals the order the story was built to be experienced in.
For practical guidance on reading specific titles with route locks, our visual novel walkthroughs cover individual titles with route order guidance and unlock condition information. The visual novels glossary defines route locks, true routes, flags, persistent variables, and the other terms that come up in discussions of visual novel structure.
