Writing Low-Spoiler Notes for Interactive Works: How to Answer Player Questions Without Revealing Route Answers?

Split the notes into three layers, and each layer only answers the questions that layer is allowed to answer: before-entry notes only cover "can I play it, is it for me," in-progress hints only cover "what do I do now that I'm stuck," and after-completion recap only covers "what did that part just mean." Each layer is also marked with a hint level, letting readers decide for themselves when to look. Below, the fictional teaching example Night Tide Signal is used to demonstrate how to write the three layers, how to mark the levels, and why some titles are themselves spoilers.

The three layers are not divided by how much content they contain, but by "the moment when the reader needs them." Before-entry notes are written near the work's introduction, before the reader has started; in-progress hints are placed where the reader may get stuck; after-completion recap is placed after finishing. The same matter can appear once in each of the three layers, but with different depth.

For hint levels, it is recommended to use four words with fixed meanings, so readers can remember them after seeing them once:

The level should be written at the beginning of each paragraph, not hidden at the end. Readers can glance at it and decide whether to skip or expand.

The questions this layer answers are: what equipment is needed, roughly how long it is, whether there is content that makes people uncomfortable, and whether prior knowledge of previous works is required. It does not answer "who to choose" or "which route to take."

The before-entry notes for Night Tide Signal can be written like this (fictional teaching example):

No hint | Duration: A single playthrough is about two hours, including three main branch points. No hint | Content: Includes nighttime at-sea scenes and descriptions of lost contact communications, and does not contain bloody images. Light hint | Pacing: Chapter 2 has a relatively long dialogue, and the choices do not affect whether you can continue. Medium hint | Structure: The choice at the end of Chapter 3 will change the characters you can encounter later, but will not cause an early ending.

Note the last item: it says "will change the characters you can encounter," but does not say which option changes it to whom. This counts as a medium hint; readers know there is weight here, but still have to decide for themselves.

The easiest thing to spoil in before-entry notes is a "recommended route." For example, writing "it is suggested to choose to stay on the boat first, so you can see the complete truth" directly gives away the answer to one route. If you really want to give advice, you can change it to "both main routes can reach the ending; the order only affects the order in which you understand the information." This is a structural explanation, not an answer.

This layer is placed where readers may stop. It answers operational-level questions: cannot find the entrance, does not know whether a certain section can be skipped, worried about choosing wrong. It does not explain the meaning of the plot.

In Chapter 2 of Night Tide Signal, there is a section where the player has to listen to recordings repeatedly in the communications room. The in-progress hints can be written like this:

Light hint | Operation: Recordings can be played repeatedly, and clips already listened to will remain in the list. Medium hint | Branch: This chapter has two options that will record your attitude, and later someone will mention it, but you will not be punished for it. Heavy hint | Condition: If you want to get extra information in this chapter, you need to leave the room after listening to all three recordings.

The third item is a heavy hint, because it gives a specific condition. Whether to give it depends on whether the author thinks "missing this section" would make readers too frustrated. If given, readers will follow it; if not given, readers may miss it. Either is fine, but the level must be marked clearly so readers can choose for themselves.

There is a common mistake in in-progress hints: treating "stuck" as "does not know how to choose." Readers are often stuck because they do not know the operation rules, not because they do not know which one to choose. So operational hints should be given as fully as possible, and plot hints should be given as little as possible.

This layer is placed after finishing, when readers have already made their choices, so explanation at this point will not ruin the experience. It can clarify which choices affected which results, and can also list branches that were not taken.

The recap for Night Tide Signal can be written like this:

No hint | The ending you reached: You chose to return to port, so you did not meet the lighthouse keeper. Medium hint | Branch not taken: If you choose to continue sailing in Chapter 3, you will enter another route, which contains two extra dialogues. Heavy hint | Complete conditions: To see the key information of both routes at the same time, you need to keep the recording in Chapter 2, choose to continue sailing in Chapter 3, and refuse a communication request at the end.

The recap layer can be heavy, because readers have already completed one playthrough. But if the work encourages multiple playthroughs, directly writing the conditions for the "best route" in the recap may turn the second playthrough into simply following instructions. You can write only "another route exists" and leave the specific conditions for readers to try themselves.

No matter how restrained the body text of the notes is, the title may still spoil. The following are all counterexamples from the fictional teaching example Night Tide Signal:

• Night Tide Signal All Endings Unlock Conditions Overview — the title promises to give all the answers, and readers already know before clicking in that they can get the answers here.
• Why the Lighthouse Keeper Actually Did Not Die — puts the key twist of one route into the title.
• Chapter 3 Must Choose to Continue Sailing — turns a specific option into the title, equivalent to making the decision for the reader.
• How to Trigger the Hidden Ending — if the work indeed has a hidden ending, this title makes "hidden" meaningless.

The corresponding low-spoiler titles can be written as: Night Tide Signal Three-Layer Notes and Hint Levels, A Few Notes on the Branch Structure of Night Tide Signal, Night Tide Signal: Which Hints Are Safe to Read. They do not promise answers, only notes.

Combining the three layers and the levels, you can make the following fill-in table. Fill in one sentence per row, with the level written at the beginning of the sentence.

When filling it in, write the "Question answered" column first, then write the example. If a sentence cannot answer the question in this column, it means it has been placed in the wrong layer.

After writing the three-layer notes, check item by item:

1. Does each paragraph begin with a level word, and do the four levels have consistent meanings.
2. Do the before-entry notes only answer "can I play it, is it for me," without specific option names appearing.
3. Do the in-progress hints give operation rules first, then plot hints.
4. Is the after-completion recap placed after finishing, and does it avoid writing the "best route" as the only recommendation.
5. Does the title promise answers, or write out twists, must-choose options, or hidden endings.
6. Cover the title and read the notes alone; can readers still decide for themselves when to look at which layer.

If item 5 does not pass, change the title first, then change the body text. Title spoilers are harder to remedy than body-text spoilers, because readers have already seen them before clicking open.

Finally, do one small action: copy out each sentence in the three-layer notes for Night Tide Signal, and ask sentence by sentence, "Which decision does this sentence make the reader make less?" If the answer is "less choosing which option," then lower it by one level or move it to the next layer.