- 01Check the source of an older instruction
- 02Carry: compare the room before copying a sequence
- 03Shear Strength: an old success may no longer reproduce
- 04Release: location and difficulty are different questions
Based on the linked sources and original analysis. No first-hand playtesting is claimed.
The changes that affect a current playthrough
The September 4 announcement changes five puzzle or progression details: Carry was reworked for a more direct solution; an unintended Shear Strength solution was fixed; Release moved to the bonus area in the Chamber of Duality; and Duality and Transport each need one fewer completed level to open their porthole. The update also adds displayed numbers beside menu sliders and corrects missing playtester credits. These are the published changes, not an inferred list of every alteration in the build.
The practical consequence is that a launch recording may differ from what you see now. A room may be reached from another place, an old shortcut may fail, or a hub opening may become available sooner. None of those observations alone indicates a damaged installation. Compare the specific difference with the announcement before treating it as a technical fault.
No public version number accompanies the patch text used here. This page therefore identifies it by date rather than assigning a number. September 4 is the newest official patch announcement found in the checked feed as of September 8. That statement concerns the public announcement record; it does not prove that no unannounced build change has occurred.
Check the source of an older instruction
When a guide stops matching your game, first identify what the guide actually covers. Look for its publication date, any revision date, and whether it says demo or full game. A recent edit can update a title or add a link without replacing an older recording. Conversely, an old page may contain a new correction that is easy to miss if you only watch its embedded video.
Then identify the exact claim you are trying to follow. Is it a room location, a required completion count, or a particular interaction? The September 4 changes do not affect all three in every chamber. A location mismatch for Release is different from a failed technique in Shear Strength. Matching the category of change narrows the explanation.
Keep the guide link in your notes alongside the room name. If you later ask for help, another player can inspect the same instruction rather than guessing which video or comment you mean. The phrase an online guide says so is too vague to diagnose a version difference, especially during the first week after release.
Carry: compare the room before copying a sequence
Carry is explicitly named as reworked, so exact step-by-step instructions deserve a fresh comparison. Look at the arrangement of surfaces and movable objects before repeating the recorded solution. If the starting geometry differs, an old sequence may no longer be a useful input script even when its underlying idea remains relevant.
A more direct solution does not tell us which individual move changed. The announcement does not provide a replacement route. This article therefore avoids filling that gap with a guessed setup. If you need a current walkthrough, choose a source whose visible starting state matches yours and whose author explains the relevant interaction rather than relying only on a long chain of inputs.
When an older approach still appears possible, you can examine it as an idea without treating it as the intended route. Ask what it accomplishes and whether the current layout offers another way to achieve the same state. This turns the patch note into a reason to re-observe the room instead of a reason to force a familiar solution into new geometry.
Shear Strength: an old success may no longer reproduce
The announcement says an unintended solution was fixed in Shear Strength. That means a previously successful technique can stop working without the puzzle becoming unsolvable. It does not identify every invalidated move or describe the replacement method. Avoid labeling a particular player route as the removed solution unless you have evidence connecting it to the change.
If a video reaches the exit through an interaction you cannot reproduce, compare the earliest divergent state. Are the same objects in the same positions? Does the interaction fail at a specific moment? A precise comparison can show whether you are encountering a likely version difference or simply starting from another arrangement.
Do not spend repeated attempts trying to reproduce an old shortcut solely because the recording proves it once worked. Return to the room's current constraints and look for a route that uses them consistently. If you cannot tell whether the source is outdated, ask that question directly with the video link and a description of the first mismatch.
Release: location and difficulty are different questions
Release has moved to the Duality bonus area. A player following a launch route may therefore look for it in the wrong place. Before searching for an installation problem, check the current chamber and the game's own visible entrances. The patch changes placement; it does not establish that the room has vanished or that your progress has been reset.
The stated purpose is to better match the room's difficulty. That is useful context for a player who found it much harder than neighboring content. It does not tell us an exact ranking of every room or guarantee that every player will find the new order comfortable. Puzzle difficulty depends in part on which interaction a person notices first.
If you want to continue without solving Release immediately, use the current game's available routes and requirements rather than an older mandatory-looking walkthrough order. Do not infer that every bonus room is optional for every possible goal, or that all chambers use the same structure. The announcement gives a specific placement change, not a complete progression manual.
Duality and Transport: read the current opening state
Each of these chambers now requires one fewer completed level for its porthole to open. The patch note states the reduction, not the new absolute totals. This page does not invent those totals. Use the current game's feedback to determine whether you have met the requirement in your own playthrough.
If an older guide tells you to finish one more room before leaving, check whether the opening is already available. You may be able to move on without following the creator's full sequence. A walkthrough often presents one person's route, which can include more completed rooms than the minimum even before a patch changes the threshold.
An opening that remains unavailable still needs a specific investigation. Record the chamber, the completed rooms you can identify, and the visible state of the porthole. Avoid concluding that the patch failed based only on a remembered number from a guide. You need a comparison between current evidence and a current requirement, not between two uncertain counts.
Use hints without confusing them with progression
The developer separately confirmed on September 6 that guidance rooms are hints and that completing a main room without using its guidance does not omit separate content. That answer can help if you are unsure whether a missing hint-room visit explains a progression mismatch. It should not be expanded into unverified claims about every menu counter or every optional area.
When comparing your progress with a guide, distinguish main rooms, hint visits, and optional exploration in your own notes. A creator may show all three in one continuous recording. Without that distinction, it is easy to mistake a teaching detour for a mandatory completion step. The current opening state is more informative than the length of the recorded route.
If you use a guidance room after the patch, focus on the interaction it teaches rather than expecting identical geometry in the main puzzle. A hint and a main room can present different layouts while sharing an idea. A visual mismatch alone is not evidence that the guidance failed to update.
Numeric sliders help make comparisons precise
The patch adds displayed values beside sliders. This makes it easier to record a setting exactly when comparing comfort or performance choices. Instead of describing a slider as near the middle, write the value shown in your menu. That gives another player or the developer a clearer description of the state you used.
The announcement does not name every slider or add a list of new settings. Do not infer a new field of view option, a new graphics control, or a particular numerical range from this change alone. Use the labels and values actually visible in your copy. The improvement is in how values are displayed, not a documented expansion of every menu.
If you are testing a setting change, record the old and new values along with the scene. A precise number is most useful when the rest of the comparison is stable. Changing several settings at once can show that a combination feels better, but it cannot tell you which setting caused the difference.
Distinguish an announcement date from a local update
A public patch announcement and the update installed on your machine are related but separate records. To compare them, check your storefront's current update state rather than assuming that opening this article changes your installation. If the client is still downloading or applying files, wait for that operation to finish before testing a changed room.
This is general update hygiene, not a game-specific repair procedure. There is no need to delete a save or start over merely to check a patch. First establish whether the game has an update waiting and whether you are launching the expected full-game entry. A demo installation can coexist with the retail game and lead to an entirely different comparison.
If your storefront exposes a build identifier, include it in a support report. If it does not, give the date of the most recent update you can see and the storefront you used. Do not manufacture a version number from the announcement date. Accurate incomplete information is more useful than a confident label that the developer cannot match to a build.
A short mismatch investigation
Start by naming the changed item. For Carry, compare geometry. For Shear Strength, compare the specific interaction that fails. For Release, compare its location. For Duality or Transport, compare the opening state and the rooms you have completed. This first classification keeps the investigation tied to the published changes.
Next, compare your initial state with the source. A different block position or standing surface can make a correct route look incompatible with the patch. Identify the first point where the source and your game disagree. That point is the most useful evidence to capture because later differences may simply follow from it.
Finally, choose a proportionate next step. If the source is clearly older and the layout differs, find a current reference or solve from the current constraints. If the states match but a reproducible interaction differs, document it. If you cannot establish the starting state, ask for a clarification rather than claiming the patch introduced a bug.
What this patch does not establish
The announcement does not document a universal performance fix, a new platform release, a public level editor, or a revised solution for every secret. Those subjects need their own evidence. A short set of patch notes should not become a catch-all explanation for every improvement or problem reported during launch week.
It also does not guarantee that every old recording is useless. Some may still show the same room and interaction. The right question is whether the particular content you need matches the current state. Evaluate a source at the point of use rather than discarding or trusting an entire channel because of its publication date.
Likewise, a change to one unintended solution does not establish a general rule that all surprising techniques are bugs. Puzzle games often invite unexpected uses of their mechanics. Without developer confirmation or a reproducible contradiction, describe the behavior you observed rather than assigning it a status the evidence does not support.
Report a discrepancy with enough context
A useful report includes the game entry you launched, the storefront, the chamber and room name, the local update information you can find, and the exact action that differs from the reference. Add the reference link and, if you viewed it yourself, a checked timestamp. Explain whether the difference is location, geometry, progression, or interaction.
Describe the expected result and why you expected it. The expectation may come from the patch announcement, a creator's video, or your own earlier play. Those sources carry different weight. Naming the source helps the developer decide whether the problem is a bug, an outdated instruction, or a misunderstanding of the current state.
Keep the report focused on one reproducible discrepancy where possible. A list of unrelated frustrations makes it harder to identify the necessary follow-up. If the report concerns a late-game puzzle, mark the content as a spoiler when posting publicly. You can be precise without putting a full solution in a thread title.
Keep a dated personal route note
If you use walkthrough notes, add a short update line to the affected entries. For Release, note that its placement changed. For Carry or Shear Strength, mark any untested old sequence as needing a current comparison. For the two changed hub thresholds, remove an unsupported claim that a particular extra room must always be completed before leaving.
Do not rewrite your entire play record merely to make it look current. Older observations can remain useful when clearly dated. A note that a technique worked before September 4 has a different role from an instruction offered to a new player today. Preserving that difference makes your record more informative.
When a later patch appears, review only the affected assumptions first. This keeps maintenance practical and avoids changing correct information without a reason. The useful habit is to connect each instruction with the state and source that support it, so that a small official update leads to a small, understandable revision in your own plan.
Compare three kinds of evidence without merging them
Consider a hypothetical player who cannot find Release where a launch video shows it. The video establishes where that recording encountered the room. The September 4 announcement establishes a placement change. The player's current view establishes what is visible now. Together those observations justify checking the bonus area; they do not justify claiming that the save is corrupt or that the video creator made a mistake when recording it.
Now consider a different player whose current Carry room appears identical to an old recording but whose attempt fails halfway through. The patch is relevant context, yet the visible match means the player should still compare the starting state and first divergent action. A patch note should not become an excuse to skip that local check. The failure could involve an unnoticed setup difference rather than the changed portion of the room.
A third case is a player who can leave a hub earlier than the guide does. The reduced opening requirement is a plausible explanation in the two named chambers. Even there, the guide may also have chosen to solve additional rooms voluntarily. The exact causal account remains narrower than the practical advice: check the current opening instead of treating a creator's route as the minimum requirement.
These comparisons show why the same update can matter in different ways. It can explain a location mismatch, prompt a closer interaction check, or remove an unnecessary progression assumption. Identifying which role it plays is more useful than attaching the phrase outdated guide to every disagreement.
Keep the evidence linked in your notes. A patch date, a recording link, and a current screenshot form a small comparison that another player can understand. A remembered statement that something changed does not. When you later revise your route, update the precise claim affected by that evidence and leave unrelated instructions alone.
If the comparison remains unresolved, say what would settle it. You may need a current view of the room entrance, a developer clarification of an interaction, or the actual completion state in the hub. Naming the missing observation turns an uncertain discussion into a practical next step instead of a debate about which source deserves blanket trust.