A Spatial Puzzle Notebook: Record What Changes, Not Every Move

Keep the smallest note that changes your next attempt

A useful puzzle notebook records observations, conditions, and questions. It does not need to reproduce every movement or draw the whole chamber accurately. In He Who Watches, changing orientation and environmental interactions can make remembered relationships difficult to track. A compact record helps you preserve what you learned while allowing the room to look different from another position. The best note is one that prevents an uninformative repetition or identifies a specific next test.

This guide presents an original note-taking system for spatial reasoning. It is optional and adaptable; you can use paper, a text file, or a few remembered sentences. It does not assume a built-in notebook feature, screenshot binding, reset key, or manual undo. The examples are hypothetical and contain no named-level solutions. The purpose is to externalize the parts of a problem that are difficult to hold in memory while leaving the actual reasoning and discovery to you. Notes should reduce effort, not turn play into an administrative task.

Begin with identity and purpose

At the top of a room entry, write the room name if known, your chosen landmark, and the immediate question. The landmark anchors descriptions when the view changes. The question gives the notes a purpose. “How can I preserve the approach after this object changes?” is more useful than a heading that simply says “hard room.” It tells you what evidence belongs in the entry and what can remain outside it for now.

Use neutral names for important elements. “Entrance object” or “target beside the arch” is safer than a role such as “exit key” that you have not verified. Keep the name consistent even if the element changes position. Add a brief identifying feature if two objects are similar. Stable identity is the notebook's foundation: if the same word refers to different things across attempts, the record will create confusion instead of resolving it. You do not need many names. Start with the elements involved in the current question and add others only when their relationships matter.

Use three kinds of entry

An observation records something you saw under stated conditions. A hypothesis predicts a relationship you have not yet established. A task identifies the next test or inspection. Mark these categories visibly, perhaps with O, H, and T. The notation itself is unimportant; the distinction is crucial. Repeated hypotheses can become familiar enough to feel like facts, especially across several sessions. Labels prevent that drift and make it easier to revise an idea without discarding genuine evidence.

For example, an observation might say that a particular approach became unavailable after an action. A hypothesis might say that the approach must be used earlier. A task might ask whether another route reaches the same useful position. These are related but different statements. The observation can remain true even if the hypothesis fails. This structure preserves partial knowledge and makes failure productive. Instead of crossing out the whole attempt, you update the hypothesis and select a new task while keeping the conditional result that the experiment actually demonstrated.

Record states instead of input strings

A string of directions or buttons is fragile. It may depend on a starting view you forgot, a configuration you changed, or an intermediate state you did not record. A state description is more robust. Write where you stand relative to a landmark, the important object relationship, and the access currently available. Then record the meaningful change that leads to the next state. This captures the logic of a route without pretending that a button sequence is universally applicable.

You can still include a short action note when it helps, but connect it to purpose. “Reach the marked face to inspect the target” says why the movement matters. If you later find another route to the same position, the note remains useful. If a game update changes a local arrangement, you can compare the intended state rather than mechanically replaying outdated directions. State-based notes are particularly valuable in first-person spatial puzzles because the same room relationship can appear through several different camera views while remaining logically the same.

Choose a reference orientation for drawings

If you draw, label the reference orientation explicitly. Use the entrance or another stable feature to distinguish faces. A rough diagram that identifies connections is often more useful than a perspective sketch that looks convincing but hides ambiguity. You are not producing architectural documentation. You are preserving the relationships needed for a question. Use arrows for verified connections and a different mark for speculative ones so that the drawing does not imply certainty you do not have.

Do not redraw the entire room after every turn. Instead, record your current supporting surface beside the stable diagram or make a small local sketch of the relevant relationship. Redrawing everything can accidentally change the model and introduce inconsistencies. A stable reference lets you compare views rather than replacing one with another. If the room is too complex for a clear drawing, switch to an adjacency list: which named surface connects to which other surface under the observed conditions. The notebook format should serve the problem, not become a constraint on how you must think.

Write conditions into observations

“The target is reachable” is incomplete if reachability depends on an object arrangement. A stronger note says “with the passage clear, I can reach the target's approach.” The condition identifies what a later action must preserve. It also explains why a previously successful route might fail after the room changes. Conditional notes are less dramatic than universal rules, but they are much more reliable foundations for planning.

When recording a failed attempt, include the same conditions. “From this surface, with this object here, the intended effect did not occur” is useful evidence. “The idea does not work” may eliminate too much. A later change in approach could make the idea viable, and your notebook should leave that possibility open unless the evidence rules it out. This is one of the most important habits in puzzle note-taking: record the boundary of what you learned. Precision about limits protects you from both repeating known failures and dismissing untested alternatives prematurely.

Build a dependency page when sequences fail

If individual interactions are understood but the order remains difficult, write each action with its prerequisites and consequences. You can use simple sentences rather than a formal graph. One action may create a needed position while removing another approach. Another may require a condition that your first action changes. Seeing these relationships together can reveal the shared obstacle behind several failed sequences.

Mark conflicts explicitly. If action A removes something B requires, write that relationship and investigate whether B belongs earlier, another approach exists, or your interpretation is incomplete. Do not assume the first alternative is correct. The notebook's job is to reveal the question, not answer it by notation. A dependency page is especially useful when you feel that you have tried every order. It may show that all your attempts share an untested premise, such as placing an object in its final state too early. That premise becomes a concrete target for the next experiment.

Keep a failed-attempt log that remains useful

A failed-attempt entry should contain the intended result, the actual result, and the lesson. Limit it to a few sentences. Long narratives of frustration are understandable but rarely help the next session. If the lesson is still unclear, write the unresolved distinction: perhaps you do not know whether the problem was approach or target state. That uncertainty can guide a smaller test. An attempt does not need to produce a rule to deserve a useful entry.

Periodically combine repeated failures that share the same cause. If three sequences all lose the same access, replace the separate stories with one conditional finding and a note of the unresolved alternatives. This keeps the notebook from becoming a cemetery of moves. Its purpose is current understanding, not a complete historical archive. Preserve an old detail only if it helps distinguish conditions or reproduce a suspected issue. The more concise the active record, the easier it becomes to notice what is genuinely new in the next attempt.

Record contradictions instead of explaining them away

If two observations appear inconsistent, place them beside each other and list the differences in starting conditions. Do not invent a hidden rule just to make the contradiction disappear. You may have missed a relevant state change, misidentified an object, or remembered the earlier attempt imperfectly. A contradiction is a useful signal that the model needs inspection. The notebook can preserve both observations while you investigate, rather than forcing an immediate choice between them.

Use a comparison format with conditions, action, and result for each case. Mark unknown details honestly. Then choose a test that isolates one difference. If the conditions cannot be reconstructed, downgrade the older observation rather than treating memory as equally strong evidence. This is not excessive skepticism; it is practical quality control. Puzzle notes are only useful if you know how much confidence to place in them. A clearly labeled uncertain memory can still inspire an experiment without misleading you into treating it as an established constraint.

Create a hint-transfer entry

Before using guidance, record the obstacle in the main room. Afterward, write the interaction or dependency you learned and the role it might play in the larger arrangement. Keep the lesson separate from the exact sequence in the simplified situation. A sequence may not transfer, but a relationship can. This entry helps you return with a focused question rather than a vague feeling that you should now understand everything.

Use two columns if helpful: lesson role and possible main-room counterpart. Leave blanks where the correspondence is unclear. A blank identifies the next inspection; it is not evidence that the guidance failed. You may understand the interaction while still needing to establish its prerequisites through a more complicated route. Write that distinction explicitly. “Rule clearer, approach unresolved” is a productive result. It tells you to work on access planning instead of repeatedly reviewing the same lesson with no change in what you are asking it to explain.

Separate secrets from the active route

If you notice an unexplained detail while solving a main room, place it in a curiosity section. Record where it is and what made it notable, without assigning a meaning prematurely. The official game description promises hidden material, but that does not turn every visual pattern into a confirmed clue. A separate section lets you preserve the observation while returning to the immediate prerequisite you were working on.

Later, revisit the curiosity list with newly learned mechanics and spatial knowledge. Some details may connect; others may remain unexplained. Keep the evidence distinct from the interpretation. A useful entry might say that a symbol appears near two named places, while a hypothesis proposes a relationship. Do not convert the hypothesis into a code solution without testing. This approach protects optional exploration from both forgetfulness and overinterpretation. It also prevents the main notebook from filling with speculative connections that make ordinary room planning harder to read.

Add dates when information may change

Record the game version or observation date when available, especially if you are comparing external guidance. The September 4 update changed puzzle details and progression requirements, so a note from an older arrangement may need review. A date helps distinguish outdated instructions from a current misunderstanding. You do not need a version field beside every sentence; one field at the room entry or session level can be enough.

When a guide and your scene disagree, note the exact mismatch and the guide date. Preserve the intended purpose of the old step separately from its route. The concept may still be useful even if the sequence no longer applies. If you seek help, this record makes your question much clearer. You can explain what you see, what the source describes, and where they diverge. That is more effective than reporting only that a walkthrough does not work, and it avoids treating an obsolete arrangement as proof that your current game state is broken.

Finish each session with a resumption card

A resumption card contains the current recognizable state, the most important verified relationship, and the next question. It should be short enough to read before touching the controls. This is the highest-value note for many players because returning to a spatial puzzle after a break often requires rebuilding orientation. The card gives you a starting point without requiring you to reread the entire room history.

On returning, compare the card with the actual scene. If they differ, resolve the difference before continuing. Your memory of where you stopped may be imperfect, and the game's save behavior should be understood through its own interface. Do not assume a particular recovery state from this guide. Once the scene and note agree, perform the planned test or revise it based on what you now notice. A good resumption card preserves momentum while leaving space for a fresh perspective, which can reveal an assumption that was difficult to see during the previous session.

A complete hypothetical entry

Imagine a room entry titled with its name and an entrance landmark. The goal line says that you want a useful approach to the destination. Observation one records a route available while a passage is clear. Observation two records that an object change blocks that approach. The hypothesis says the interaction might belong later. The next task asks whether another action can be completed before the passage changes. This is already enough for a productive notebook entry without a detailed map.

After the test, suppose you discover that the earlier action is available but does not establish the expected condition. Preserve the route observations and revise the hypothesis. Add a new task focused on the missing condition. The entry evolves through evidence instead of accumulating disconnected attempts. If you later use guidance, add the learned dependency and compare it with the missing condition. The notebook becomes a working explanation of the room: compact, conditional, and easy to update. That is far more valuable than a long list of inputs whose starting assumptions are no longer clear.

Know when to stop writing

If note-taking interrupts every small action, simplify the system. Record only meaningful state changes, surprising results, and the next unresolved question. Familiar routes and repeated confirmations can remain unrecorded unless their conditions matter. The notebook should free attention for play, not demand constant supervision. A single sentence can be enough when it captures the dependency you kept forgetting. More detail is useful only when it improves your ability to compare or resume.

Likewise, avoid polishing diagrams or prose while the relevant question is already clear. The record is for reasoning, not presentation. You can reorganize an entry after a discovery if it has become cluttered, but do not let organization substitute for testing an idea. A useful balance is to observe, test, summarize, and continue. Write at the boundaries where understanding changes. This makes the notebook feel like a memory aid rather than a parallel project, and it keeps the satisfaction of solving the chamber centered on the game itself.

The notebook's real job

A good record distinguishes what you saw, what you believe, and what you will test. It keeps identities stable while positions change, records the conditions of success and failure, and preserves the first point where a plan diverged from observation. It also makes outside help more precise and returning after a break less demanding. None of this requires a formal notation or extensive documentation. Consistency matters more than sophistication.

Use the smallest system that solves your actual memory problem. If you forget orientation, emphasize landmarks. If you repeat failed orders, emphasize dependencies. If hypotheses become confused with facts, emphasize labels. If sessions are far apart, emphasize resumption cards. The notebook succeeds when your next attempt begins with a clearer question and ends with a clearer account of the result. That clarity turns experimentation into accumulated knowledge, allowing a difficult spatial room to become understandable through a sequence of discoveries rather than a single moment of perfect visualization.

Sources and evidence

1. He Who Watches official press kit ↗
2. Official community hub and September 4 patch notes ↗