Official game screenshot
Official game screenshot · Official press kit ↗

Based on the linked sources and original analysis. No first-hand playtesting is claimed.

Use the hint to answer a question

He Who Watches advertises playable hints, and its creator describes the system as inspired by Can of Wormholes. The practical way to approach that guidance is with a question you can name. Instead of asking for the entire answer, identify the relationship you cannot explain: how to preserve an approach, how to satisfy two conditions together, or why an apparently useful action prevents the next one. A focused question gives you something to look for while engaging with the smaller teaching situation.

Coverage and current player discussion describe simplified puzzle situations that illuminate an interaction. This guide explains how to learn from that format without claiming that every room has identical guidance or that every hint guarantees an immediate breakthrough. It does not supply level solutions or assume any particular hint shortcut. Use the option presented by your installed game. The exercises and examples are original learning strategies. Their purpose is to help you extract a transferable idea, return to the main chamber, and continue reasoning with a clearer understanding of what remains uncertain.

Decide when assistance would be useful

You do not need a fixed number of failed attempts before seeking a hint. A better criterion is whether your last few attempts answered different questions. If each trial tested a new relationship and produced clear information, continued exploration may be satisfying. If you are repeating the same sequence without a new hypothesis, guidance may be more useful than another repetition. The distinction is informational, not moral. Hints are part of the available learning experience, and using one does not invalidate the reasoning you do afterward.

Another useful signal is an unresolved contradiction. You may believe that two conditions are both necessary but cannot see how they can coexist. That is an excellent question to bring to a hint, because the missing idea may concern the relationship between those conditions. By contrast, if you cannot recognize your current position or intended input, first resolve that local confusion. Assistance aimed at puzzle logic may not address an orientation or controls problem. Choosing the right moment helps you interpret what the hint is actually teaching instead of expecting it to solve an unrelated obstacle.

Write a before-hint note

Before leaving the main problem, write three short statements: the goal you are pursuing, the last relationship you verified, and the unresolved obstacle. For example, an imaginary note might say that you can reach a marked side, that a particular approach remains available only before an object changes, and that you cannot perform the final interaction afterward. This captures the useful state of your reasoning without recording every failed move. It also gives you a reference when you return.

The note should distinguish observations from beliefs. “I observed this route closing after the action” is different from “I think this route must remain open.” The first is evidence; the second is a possible requirement. A hint may challenge the requirement rather than the observation. If you preserve the distinction, you can recognize that lesson. Without it, you may reject a helpful idea because it seems to contradict something you “know,” when it actually contradicts an untested assumption about what the solution must look like.

Read the simplified situation on its own terms

When you enter guidance, first inspect the smaller arrangement without forcing it to match the main room. Identify its destination, relevant elements, and immediate constraints. A teaching puzzle may remove distractions or make an interaction easier to isolate. If you spend the whole time searching for a one-to-one visual correspondence, you may overlook the simple relationship the arrangement is designed to expose. Give it enough attention to become intelligible as its own problem.

Ask what uncertainty the reduced scene leaves you with. Often a smaller setting makes one choice or dependency stand out. That does not mean you should guess the intended lesson immediately. Observe and test just as you would elsewhere, but with a narrower focus. If an action surprises you, inspect that surprise carefully. The useful insight may be the condition that made the result possible rather than the movement itself. Learning the cause gives you something that can survive a return to a larger, differently shaped chamber.

Explain the result before leaving

After solving or understanding the hint situation, pause long enough to state why the successful idea worked. Avoid a description consisting only of actions. “I did this, then that” records a sequence but not its logic. A stronger explanation identifies what the first step made possible, why the next step needed that condition, and what would have prevented the result. This causal account is the part you can transfer into a different arrangement.

Try completing three sentences: “The important condition was…,” “The action that established it was useful because…,” and “My earlier assumption missed….” You do not need elegant language. The exercise is diagnostic. If you can only describe the appearance of the scene, you may not yet understand the interaction. If you can explain the dependency but not the exact inputs, that can be enough. The main chamber will require its own route and positioning, so an understanding of purpose is more valuable than a memorized sequence performed in another space.

Map roles instead of shapes

On returning, look for elements that play the same functional roles as those in the guidance. A role might be preserving access, providing an approach, changing a necessary condition, or creating an intermediate state. The corresponding elements need not occupy the same visual positions. What matters is the relationship. This is similar to recognizing the same mathematical structure in two differently worded problems: the surface details vary while the dependency remains useful.

Make a small role map with one column for the lesson and another for the main chamber. Leave a blank when you cannot identify a correspondence. A blank is a question, not proof that the hint is irrelevant. Perhaps the role is supplied by a route rather than an object, or perhaps another prerequisite is needed before the relationship appears. Do not fill the blank with a convenient guess. Inspect the room for evidence. Mapping roles carefully preserves the insight while allowing the larger problem to remain a genuine exercise in interpretation.

Distinguish a missing mechanic from a missing order

A hint can clarify what an interaction does without showing how to arrange all the main room's steps. If you return and still feel stuck, ask whether the remaining uncertainty is mechanical or sequential. Mechanical uncertainty concerns the effect under particular conditions. Sequential uncertainty concerns how to establish those conditions in an executable order. These require different next actions. Retesting a mechanic you now understand may not help with an ordering conflict.

For a sequence problem, list the prerequisites of the interaction you learned. Then identify which earlier actions create or destroy them. The hint may have made those prerequisites effortless, while the main chamber makes their construction the challenge. That does not make the hint incomplete in a useless sense. It means the lesson has reduced the problem to a more specific task. A good return note might say “interaction understood; approach still missing.” That sentence tells you to investigate access rather than repeatedly revisit the same simplified example without a new question.

When the hint feels too obvious

Sometimes a simplified puzzle demonstrates something you believe you already know. Before dismissing it, compare your main-room plan against the exact conditions that made the lesson work. You may understand the broad mechanic but overlook a necessary relationship, an intermediate position, or the timing of a prerequisite. The apparent obviousness of the lesson can conceal the detail that matters. Look for the condition you did not explicitly include in your original explanation.

If the lesson truly adds no new information, use that result to narrow the remaining problem. You can now separate the taught interaction from the unresolved construction or navigation issue. Return to the main chamber and ask where your plan stops matching the conditions of the simplified situation. The first mismatch is a useful target for investigation. This response is more productive than repeating the hint until inspiration arrives. It treats guidance as evidence: even confirmation of something known can help locate what you do not yet understand.

When the hint feels unrelated

An apparently unrelated hint may share a dependency that is difficult to see through the main chamber's geometry. Start by stripping both situations down to verbs and requirements. What must become accessible? What must stay possible? What changes after the key interaction? Compare those answers instead of textures, distances, or visual symmetry. The relationship may become clearer when you stop expecting the scenes to resemble each other.

However, do not assume that every confusion is your fault or invent a correspondence merely to make the guidance seem perfect. You may still lack enough information, misunderstand an earlier rule, or be confronting a different part of the room than the lesson addresses. Record the uncertainty honestly. A useful request for help can explain the hint's lesson as you understand it and identify why you cannot map it to the main obstacle. That invites a targeted clarification, preserving more discovery than asking for a full sequence or accepting an unsupported explanation.

Protect yourself from accidental spoilers

If you want only a nudge, define that boundary before opening an external guide or asking another player. State the room, the condition you cannot satisfy, and what you already understand. Ask for a question or conceptual direction rather than a complete route. This is an editorial strategy for managing your own experience, not a guarantee that every community response will respect the boundary. A precise request nevertheless makes the desired level of assistance much easier to understand.

When using a written source, read the smallest relevant section first and stop once you have a testable idea. Avoid scrolling through an entire walkthrough merely because the first paragraph did not instantly solve the problem. Give the new idea a chance to interact with your own reasoning. If you need more help, return with an updated question. This staged approach can preserve the pleasure of discovery while reducing unproductive repetition. It also produces better notes, because each piece of assistance answers a specific uncertainty rather than replacing your whole model of the room.

Evaluate progress after using guidance

Progress is not limited to completing the chamber. After a hint, ask whether you can predict an interaction more accurately, eliminate an impossible order, recognize a useful intermediate state, or explain a previous failure. Any of these can be a meaningful improvement. If none occurred, identify what remained unclear in the guidance rather than assuming that you failed to benefit from it. The next question should be narrower than the one you started with whenever possible.

A useful evaluation has two parts: knowledge gained and action enabled. You might have learned the relevant dependency but still need to find an approach that creates it. That distinction gives your next session a clear objective. It also prevents frustration from erasing genuine learning. Write the new knowledge in one sentence and the next investigation in another. When you return later, those sentences will be easier to use than a memory that “the hint did not help,” which combines several different possibilities into an uninformative judgment.

Avoid turning hints into rote procedures

Memorizing a successful sequence can help reproduce a result, but it is a fragile substitute for understanding. A different starting orientation, object state, or access condition can make the same input sequence irrelevant. This matters especially in a game whose spatial relationships can change your interpretation of a room. Preserve the reason for each meaningful step, not just the step itself. Then you can adapt when the main arrangement differs from the teaching situation.

One exercise is to explain which step could not be moved earlier and why. Another is to identify what would fail if an important condition were absent. These counterfactual questions reveal the structure of the lesson. You are not required to test every counterfactual in-game; reasoning from observed dependencies may be enough to formulate a hypothesis. Keep hypotheses labeled as such. The goal is a flexible explanation you can verify in the main room, rather than a story that sounds complete but relies on assumptions you never examined.

A worked learning cycle

Imagine that your main obstacle is losing access to a target after changing an object. Before guidance, note the access relationship and the action that appears to remove it. In the simplified situation, inspect whether the lesson concerns preserving access, changing the order, or reaching a different approach. Suppose your understanding improves: you now see that the crucial interaction must occur while a certain relationship still holds. Write that lesson without attaching it to a specific button sequence.

Back in the main room, identify the corresponding relationship and ask how to establish it. You may need to reach another surface first or delay an object change. Those are new hypotheses, not conclusions supplied by this example. Test one, compare the resulting state with the requirement, and update the note. If the attempt fails, locate whether the failure concerns reaching the relationship or misunderstanding its effect. The cycle keeps the hint useful even when it does not translate directly into immediate completion, because each return produces a sharper diagnosis.

Match assistance to your preferred experience

Some players enjoy long independent investigation; others prefer frequent nudges that keep the pace moving. Neither preference requires justification. Decide what kind of session you want and use guidance accordingly. You might choose to spend a session learning one interaction, to make progress through accessible chambers, or to investigate optional material. The appropriate amount of help can differ between those goals. Avoid turning an arbitrary waiting period into a rule that makes the experience less enjoyable.

It can help to choose a stopping condition for independent attempts: repeated experiments with no new information, a clearly named contradiction, or fatigue that makes observation unreliable. These conditions are based on the quality of reasoning rather than a stopwatch. Likewise, choose a stopping condition for reading help: one new testable idea. That balance protects both momentum and discovery. You remain the person connecting the lesson to the room, deciding what to test, and interpreting the result, even when the initial nudge comes from the game's own teaching system.

Check whether the lesson changed an assumption

After guidance, return to the before-hint note and underline the assumption that now looks less certain. The most valuable change may be surprisingly small: an action need not happen first, a visible arrangement is not the required final state, or an approach can be established another way. These are examples of reasoning shifts, not assertions about a particular hint. The exercise helps you notice progress that might otherwise disappear behind the disappointment of not immediately finishing the chamber.

Then rewrite the next question using the revised assumption. Instead of asking how to force the original sequence to work, ask what new sequence the lesson makes plausible. Keep the verified observations from the earlier attempt; they still constrain the problem. You are changing the interpretation around them, not erasing the evidence. This is a disciplined form of fresh thinking. It preserves the work you did independently while allowing assistance to open a genuinely different line of investigation, rather than becoming another detail added to the same unsuccessful plan.

A practical hint checklist

Before guidance, name the obstacle and separate verified observations from assumptions. During guidance, inspect the simplified problem independently and identify the condition behind the useful interaction. Before leaving, explain why it works. After returning, map roles, locate the first missing prerequisite, and test one idea. If the main room remains unresolved, classify the remaining difficulty as mechanics, order, position, or observation. This checklist is short enough to use without making play feel like homework.

The strongest outcome of a playable hint is not a memorized route but a better question. A large chamber can obscure a relationship that becomes obvious in a smaller setting. Once you recognize that relationship, the remaining work is to establish its conditions in the actual room. Keep the lesson compact, preserve the uncertainty that remains, and seek further help at the level you want. Guidance can support discovery precisely because it gives you an idea to reason with, leaving the larger task of interpretation and execution in your hands.

FocusWhat to recordPractical response
Before guidanceName the unresolved dependencyKeep observations separate from assumptions
Inside guidanceExplain the useful interactionLook for cause rather than memorized moves
Back in the roomMap the lesson by roleLeave uncertain correspondences as questions
After another attemptClassify the remaining obstacleChoose a smaller test or more specific nudge

Sources and evidence

  1. Creator launch announcement, September 2, 2026 ↗
  2. Thinky Games pre-release coverage, October 1, 2025 ↗
  3. Official community hub and September 4 patch notes ↗