- 01Read the missing hints correctly
- 02Separate three reasons for being stuck
- 03Prepare for Gemini by recovering a causal explanation
- 04Prepare for Mercury by auditing the opening
Based on the linked sources and original analysis. No first-hand playtesting is claimed.
Hint levels
01You do not need wisps or gardens first
The developer explicitly says that solving Gemini, Mercury and Apollo does not require learning their solutions through wisps or gardens. In the same Steam reply, the developer acknowledges that the trio lacks in-game hints and offers references to earlier mechanics. Preparation should therefore focus on refreshing those ideas, not on assuming an undiscovered collectible has locked the puzzles.
The references are specific. Gemini connects to Gravity Storage in the Chamber of Transport, with the added need to ride the block to the exit. Mercury centers on the hookshot block used at the beginning, with a comparison to a Rigidity wisp interaction. Apollo resembles Elevator III in the Chamber of Perpetuity. These are developer clues, not complete routes or claims that every preliminary movement repeats.
This article is a preparation framework based on that discussion. It was not written from an independent completion run. It helps you choose what to revisit, organize observations and separate a genuine knowledge gap from a misleading assumption about prerequisites. It does not supply a fabricated map of the chamber or an unsupported order in which the three puzzles must be solved.
02Read the missing hints correctly
The absence of an in-game hint in these rooms is acknowledged by the developer. If you cannot find a smaller teaching version, that does not by itself mean you have failed to activate it. Avoid spending a long session searching menus or nearby scenery on the assumption that the usual hint structure must exist everywhere.
Elsewhere, a separate developer answer explains that Pray for guidance rooms are hints and can be omitted when completing the main room. That establishes their optional role, but it should not be stretched into a claim about every achievement or every future update. The narrower practical point is that the Imprisonment discussion supplies external nudges for puzzles whose ordinary in-game guidance is absent.
Adjust your preparation accordingly. Instead of looking for a hidden hint chamber, identify the mechanic you cannot currently explain. The developer's references give you a way to study an earlier example. This preserves the satisfaction of making the adaptation yourself while avoiding a search for guidance that the source says these rooms do not have.
03Separate three reasons for being stuck
A mechanical gap means you do not understand how a relevant interaction works. A construction gap means you understand the interaction but cannot arrange the current room to use it. A navigation gap means a promising construction changes the scene but you cannot yet complete the player's route. These categories are reasoning aids rather than game terminology.
They suggest different next actions. Revisit an earlier example for a mechanical gap. Inspect local object roles and preparation for a construction gap. Study the destination state and player relationship for a navigation gap. Treating all three as a general lack of knowledge can lead to an unnecessary tour of secrets when the unresolved problem is actually quite local.
Before leaving a room, name which gap best describes the latest attempt. You can change the diagnosis when new evidence appears. The value lies in making a deliberate choice about what to learn next. A short, accurate description such as mechanism works but arrival unusable is more actionable than concluding that the whole chamber is beyond you.
Open the guide · contains spoilers
Prepare for Gemini by recovering a causal explanation
For Gemini, the most grounded revisit is Gravity Storage. Your objective is to recover why its construction works, not merely its appearance. Record what is prepared, what changes at the decisive moment, and what motion follows. Then ask how the player could remain part of a comparable mechanism through a useful arrival.
The extra riding requirement is important for preparation because it changes what counts as understanding. An explanation that tracks only the objects is incomplete for the comparison. Include the player's starting relationship and intended endpoint. Do not assume that a mechanism which moves correctly automatically transports you in the required way.
When you return, compare roles before attempting precise placements. You are adapting an idea to Gemini, not entering a memorized code from Gravity Storage. The local setup may require its own reasoning even after the earlier principle is clear. That distinction lets you recognize progress: understanding the shared mechanism can be a real gain while the new arrangement remains unresolved.
Prepare for Mercury by auditing the opening
Mercury's developer clue points to the initial hookshot block. A useful preparation step can therefore happen without leaving the room: review the role you assigned to that object after the opening interaction. If your plan treats it as finished with, revise the plan so that its possible contribution to reaching the exit is explicitly considered.
The Rigidity wisp comparison is helpful if you already know the relevant interaction, but it is not a mandatory detour. The developer's statement about wisps and gardens rules out treating optional exploration as required preparation for these solutions. If visiting the comparison would involve a separate uncertain search, the starting-block clue remains available to investigate directly.
Write a simple inventory of continuing roles. Which objects does your plan need at the end, and how do they remain available? A plan that appears to need extra material may have assigned separate objects to jobs that occur at different moments. That is a hypothesis to examine, not proof of a particular Mercury construction. Keep the known hookshot block in the accounting.
Prepare for Apollo by changing the description
For Apollo, revisit Elevator III and describe its important relationships without relying on screen directions. The player follow-up in the source reports that a different orientation made a similar construction feel unfamiliar. That suggests a study method focused on roles, support and transitions rather than a screenshot of blocks against a remembered wall.
A quick drawing can help. Label what each part does, rotate the page, and see whether the explanation still makes sense. This is a perception exercise, not a simulation of every rule in the game. It can reveal whether you have confused the orientation of a familiar construction with the conditions that make it work.
Back in Apollo, map the roles to candidates in the current scene. Leave uncertain matches provisional. If the central interaction is now clear but a local preparation is not, you have reduced the problem. Continue with that narrower question rather than assuming the earlier-room reference failed because it did not instantly provide every move.
Choose your own working order honestly
The available discussion does not establish a mandatory order among Gemini, Mercury and Apollo. One player's experience of finding one easier does not create a universal difficulty ranking. The developer suggests Gemini may be the hardest of the three, but individual familiarity with the referenced mechanics can change which room feels most approachable.
Choose a working order based on the question you can currently investigate. If Elevator III is fresh in memory, Apollo may offer a clear comparison. If the opening hookshot interaction has just prompted a new idea, Mercury may deserve another attempt. If Gravity Storage is the missing piece you can study directly, revisiting it may be the most productive next step.
This approach avoids turning preparation into a checklist that must be completed before any progress is allowed. You do not need perfect understanding of all three to work on one. Use the developer's references as targeted resources, and update your plan when an observation makes a different room more promising.
Keep an evidence notebook, not a theory archive
A useful note has three parts: what you observed, what you expected, and what question remains. For example, a moving object may have behaved as predicted while the player stayed behind. That distinguishes the observed mechanism from the unresolved transportation relationship. It tells you more than a page of increasingly complicated speculative diagrams.
Mark ideas as hypotheses until you see them work. A plausible construction is not a verified route simply because you can narrate it fluently. Likewise, one failure does not necessarily disprove the entire idea if the intended setup was not achieved. Record the narrow result and the reason you think it matters.
The notebook can be tiny. Its purpose is to preserve the current boundary between known and unknown, especially if you switch rooms or take a break. Long notes that reproduce every movement can become difficult to interpret after a changed orientation. A few role-based observations usually provide a stronger starting point for the next session.
Build a useful stopping rule
Stop an experiment when it has answered its question, even if the room is not complete. If you were testing whether a prepared relationship survives a movement, observe that result before improvising several additional actions. Otherwise you may lose track of which part of the final state came from the test and which came from the improvisation.
Stop a line of experimentation when repeated attempts differ only in small unexamined adjustments. At that point, return to the causal explanation. What are you expecting to happen, and which condition is supposed to cause it? If the answer is vague, a revisit to the referenced puzzle may be more productive than another nearly identical attempt.
These stopping rules are about learning efficiency, not a claim that the game enforces a time limit or a fixed number of retries. They help preserve attention for meaningful differences. The final trio can demand sustained reasoning; making each attempt legible reduces the chance that a long session ends with less clarity than it began.
Optional secrets remain a separate choice
Wisps and gardens may still interest you for their own sake. The developer's prerequisite statement does not reduce them to irrelevant content; it simply says they are unnecessary for learning these three solutions. Decide whether to explore them because you want that experience, not because you have inferred an invisible requirement from being stuck.
That separation also helps control spoilers. A guide to a late secret may reveal information far beyond the mechanic you needed to refresh. Before opening it, ask whether the Imprisonment clue already points to a main puzzle or a specific object you can study. A targeted revisit may preserve more discovery than a broad search for endgame answers.
If you choose exploration as a break, leave a note that identifies the current puzzle question. Returning from optional content should not require reconstructing an entire failed session from memory. The note can preserve the developer reference, the strongest observed behavior, and the one relationship you still cannot explain.
How to use a community answer without overreading it
A developer reply, a player's successful follow-up and an unanswered guess are different kinds of evidence. The developer can identify the intended analogy. A successful follow-up can show that the analogy was useful to someone. A detailed player description may help with a specific construction, but it still needs careful translation to your viewpoint.
The original questions in the Imprisonment thread include failed attempts and hypotheses about what might be required. Do not treat those passages as instructions. A concrete description can sound authoritative even when it was written to explain a dead end. Read the reply context and distinguish the problem statement from the answer.
When you consult a more explicit solution, first extract the object roles and decisive transition. Only then interpret directions. This reduces the risk of applying a correct idea from an incompatible camera frame. It also helps you understand why the solution works, so a small execution error does not force you to begin copying the entire account again.
A preparation session with a clear objective
Choose one puzzle and one uncertainty. For Gemini, it might be the underlying Gravity Storage interaction. For Mercury, it might be how the starting block remains relevant. For Apollo, it might be recognizing the earlier construction under rotation. State the objective before you begin the revisit or experiment.
At the end, record a sentence explaining what changed in your understanding. Perhaps you now know why a restraint matters, which object role was omitted, or why a screen direction was misleading. If nothing changed, record that honestly and reconsider the method of investigation. Time spent is not the same as evidence gained.
Then return to the current room with one concrete question. Avoid trying to solve the entire chamber in a single mental leap. A well-chosen preparation session should make the next local decision clearer, even if it does not immediately finish the level. That is a realistic measure of whether the developer's reference is helping.
Avoid turning frustration into a rules claim
After many attempts, it is tempting to conclude that a room must require a hidden unlock, an unmentioned technique or a bug workaround. Those claims need evidence. In this case, the developer supplies a more ordinary explanation: difficult applications of existing ideas, without the usual in-game hints. Start there before expanding the problem into a search for missing content.
Similarly, another player's quick success after reading a hint does not establish how long your solution should take. Their familiarity, prior attempts and moment of recognition may differ. Use their report as support for the clue's relevance, not as a benchmark against which to judge your own progress.
The practical alternative is to name the failed prediction. What exactly did you believe would happen, and what happened instead? That question moves the discussion from a global judgment about the game or your ability back to a relationship that can be inspected. It is also the information most useful if you later ask another player for a targeted nudge.
Ask for a narrower hint when you need one
If you seek help, identify the room and the part of the process you understand. Mention the relevant developer comparison and describe where your adaptation stops working. Avoid claiming a complete setup unless you can state it clearly. A question about a specific relationship is easier to answer without revealing the whole route.
You can also state your spoiler preference. Asking whether a proposed object role is relevant may be enough; asking for every movement invites a different response. The purpose is not to make requesting help complicated. It is to give the other person a clear boundary so that the answer addresses the actual uncertainty.
This guide does not send messages or request help on your behalf. It supplies a way to formulate the problem if you choose to do so. The same formulation is useful privately: often writing the question exposes an assumption that was hidden while you were manipulating the scene.
What readiness looks like
You are prepared when you can explain the relevant earlier idea, name the current room's unresolved adaptation, and distinguish required knowledge from optional exploration. You do not need a memorized route through all three puzzles before beginning. The developer's references support targeted study and experimentation rather than an exhaustive completion checklist. Keep the notes specific enough that another session can resume from them, but short enough that reading them restores the puzzle's central question instead of recreating every unsuccessful action.
The known facts remain narrow and useful: no wisp or garden prerequisite for these solutions, no in-game hints for the trio as discussed, and specific references for each room. All the worksheets and diagnostic categories here are original planning tools. They should help you make better observations without pretending that the missing spatial details have already been verified.
Carry one clear question into the next attempt. For Gemini, account for the complete ride. For Mercury, account for the starting hookshot block. For Apollo, account for the familiar construction beneath the changed orientation. Those questions keep your preparation connected to the puzzles the developer actually described.