The route guide should allow readers with the same version and the same starting state to reproduce the steps. First, write the scope of application and prerequisites, then select according to the order in which they appear, separating verification results from plot explanation.
Necessary information
- Full title, platform, version, and text language of the work.
- New saves or inherited saves, and which routes have been completed.
- The chapter or date where the option appears, the original text of the option, and the selection result.
- Verification date and scope.
Record format
| node | Choice | The result |
|---|---|---|
| Chapter/Date | The original text of this version of the option | The route you enter or the next node |
Revised
Steps without prior play confirmation are marked as "Pending Verification." The recommended reading order is a suggestion, while the unlocking conditions are based on game mechanics; each is explained separately. Other versions may have different translations; supplementary comparisons can be made under the original steps.
Clearly state the scope of application
At the beginning, record the full name of the work, platform, updated version, and text language, and explain the goal of the strategy: enter a certain route, reach a certain ending, or collect specific content. Trial versions, originals, and expanded versions should each have clear boundaries.
The recommended reading order is based on the author's suggestion; If you must complete a certain route before you can continue, this is a requirement for unlocking with evidence. If only one order succeeds, it cannot be concluded that other sequences will inevitably fail.
Prerequisites include system progress
Explain which routes you completed before starting from the new game or the designated save file, and whether you will carry over the system progress after clearing the game. If necessary, record relevant settings and triggered events, rather than writing just one slot number that cannot be corresponded to.
Public guides should not require readers to cover all their progress to imitate the author's status. First, explain which states are related to the target, then provide operational suggestions to keep the original archive; Uncertain conditions are marked as pending verification.
Select by node record
Each step should include at least a chapter or date, the option text for that version, and the selection result. Repeated identical options are supplemented with scenes or their order of appearance; Don't just write "choose the first one," because different translations or interfaces may make it hard for readers to respond.
You can use a table with "Node/Options/Next Node/Suggested Archive". When translation differences arise, the text of each version is listed separately; If it is unclear whether two sentences are equity, the difference should be kept for now and not forcibly merged.
Specify where the actual verification has reached
Record the reproduction date, the version used, and the final target reached. Only confirm the entry route, then write the entry route; Hidden events, additional endings, or complete collections that have not been confirmed without further confirmation should not be marked as complete together.
When modifying the guide, explain the reason for the changes. If the steps come from someone else's hands-on record, provide the original link and scope of application, and do not write the repost as your own test. The ending content and route significance should be clearly marked in the spoiler analysis sections, and the operation chart should be kept as concise as possible.
Clearly define the starting point
At the top of the guide, indicate the full version, platform, route name, as well as conditions such as new games, inheriting save files, or starting after clearing the game. The prerequisite route and the features that must be opened are listed separately so readers can judge whether they meet the criteria.
Record according to the operation sequence
For each step, write the chapter or date, the original text of the options, the selected answer, and the suggested archive slot. Skipped repeated paragraphs indicate that reads can be fast-forwarded, and after reaching the route or ending, write down the observable confirmed position.
Maintain inspection records
Only the steps actually taken are marked as the clearance route. Source should be indicated separately for inferences, publisher statements, and citations from others' guides; When differences are found between versions, separate branches are used instead of overriding the original steps.
Published on Fantasy Encyclopedia
Use the entry template to create a strategy outline, and submit revisions along with the main text and data card. New users usually need to be reviewed; When encountering a conflict with the latest version, the main text should be more public, and valid steps should be reserved before submitting. Ending analysis includes spoilers and folds by chapter.
Related entries
- Game System:The starting point and steps of the route guide
- Specify applicable versions:Galgame version identification
- Steps for Strategy Save:Archive management
- Route spoilers:Help: spoiler annotation
- Save the guide source:Help: Indicate the source
- Related works:Archive management
- Related works:Help: spoiler annotation
- Save and describe the starting state of the guide:Archive management
- Spoiler scope indicated for plot explanation:Help: spoiler annotation
- Indicate the source of the gameplay record and retelling:Help: Indicate the source
References
Data compiled on: 2026-10-07.