- 01Name the symptom precisely
- 02Understand the limited explanation
- 03Check whether the overlay was involved
- 04Compare devices one at a time
Based on the linked sources and original analysis. No first-hand playtesting is claimed.
The verified first step
If left and right suddenly rotate the character instead of moving sideways, press and release Shift once, then test movement again. In a September 6 Steam reply, developer Danga explained that holding Shift changes this behavior and that opening the Steam overlay can reportedly leave the modifier logically stuck. The thread was marked answered. This is a developer-recommended workaround for the reported symptom, not evidence that every movement problem has the same cause.
The player who opened the thread was using an Xbox One controller and said the behavior also persisted with a keyboard. That context makes the report useful to controller users, but it does not establish a special controller button combination. The documented suggestion is the keyboard Shift press. This page does not invent an equivalent binding for every gamepad configuration.
Make the test in a position where a small movement will not disrupt a complicated puzzle setup. Release the key fully before trying the direction again. If normal movement returns, note whether the problem began after using the overlay. If it does not, move to the focused checks below rather than pressing random modifiers or rebuilding all your controls.
Name the symptom precisely
A turn instead of a sideways step is different from a missed input, continuous movement, a camera drift, or a long pause before movement occurs. These problems can feel similar when you are trying to navigate quickly, but they point toward different investigations. Describe what the character actually does when you press one direction once.
Try the same brief input twice from a stable position. Does it produce the same kind of turn both times? Does the opposite direction behave symmetrically? Is the issue present with one device or with both keyboard and controller? The goal is a short description of the behavior, not a long stress test that scrambles your room state.
Avoid describing the problem only as controls broken. A useful statement is that a left input changes the facing direction after the overlay closes, while forward movement still behaves normally. The more exact description lets you compare the known report with your own case and helps the developer decide what information to request next.
Understand the limited explanation
A modifier changes the meaning of another input while it is held. The developer's reply identifies Shift as relevant to this rotation behavior. If a modifier's release is not reflected in the game's state, later direction inputs can behave as if the modifier remains active. Pressing and releasing it again is a simple way to refresh that state.
That explanation fits the reported workaround, but it is not a source-code diagnosis. This article has not inspected the game's input implementation or reproduced the issue. Do not infer that a particular library, operating system service, or controller driver is defective from this one public exchange. The useful verified fact is the action the developer suggested for the observed symptom.
The distinction also sets expectations. A workaround can restore normal play without explaining every condition that triggers the problem. If it happens again, documenting the transition that preceded it may help the developer investigate. You do not need to solve the internal cause before sending a useful report.
Check whether the overlay was involved
Recall what happened immediately before the behavior changed. Did you open the Steam overlay, switch windows, return from another application, or change input devices? Record the sequence in plain language. Do not claim the overlay caused the issue unless the relationship is repeatable; one event occurring before another is only a lead.
If the Shift press restores movement, you can make a brief note that the developer's workaround helped in that session. That is a useful result even if you do not attempt to reproduce the problem. Repeatedly forcing an issue is unnecessary when your main goal is to continue playing and you already have a practical recovery step.
If you choose to investigate further, keep the test small and reversible. Use a stable location, perform one transition, and check a single movement. Stop if the result becomes unclear or the game state is no longer easy to compare. A clean observation is more valuable than a long sequence of transitions that leaves several possible triggers mixed together.
Compare devices one at a time
If you use both a keyboard and a controller, test them separately. Set one aside while checking the other so that accidental input from a resting stick or a held key does not complicate the result. This is general input diagnosis, not a confirmed repair for the reported Shift issue.
Record whether the same directional action produces the same wrong behavior on both devices. A problem that follows the game state across devices may need a different investigation from a problem confined to one device. The distinction does not prove the cause, but it narrows the evidence you can provide.
Do not immediately replace a controller or reset all its settings because a keyboard workaround was suggested. The original report itself involved a controller and persistence on keyboard. Start with the small known action, then compare the devices deliberately. Hardware replacement is not supported by this thread as a first response.
Inspect your actual bindings
The official retail listing describes configurable controls and support for several input types. That does not establish the exact binding on your installation. Open the relevant control settings and inspect what is currently assigned if your behavior differs from the reported case. Record any custom mapping you intentionally use.
A remapping layer can also change which physical key reaches the game as Shift or as a direction. If you have created a custom layout, identify that fact in your notes. Do not assume that a physical button's label tells you the action the game receives. The useful comparison is between the configured action and the observed result.
Avoid changing several assignments while trying to diagnose one symptom. First document the existing mapping. Then, if you make a reversible change, note exactly what changed and what happened afterward. A full reset may remove the symptom but also erase the information needed to understand whether the mapping was involved.
Distinguish a stuck modifier from a held key
If Shift is physically held down, rotation behavior may be expected according to the developer's explanation. Check that no key is being pressed by your hand or an object on the desk. This simple observation is different from assuming a keyboard fault. It eliminates an immediate cause without changing software or puzzle progress.
If the key appears free but the game still behaves as though it is held, the press-and-release workaround is the relevant next check. If the issue occurs outside the game as well, that is additional context for a broader input investigation. Do not use a game-specific forum reply as proof that every system-wide modifier problem originates in the game.
Keep the description factual. Say that the behavior continued after your hand left the key, or that tapping Shift restored ordinary movement. Those statements are observable. Saying that the keyboard buffer is corrupted claims an internal mechanism that the available evidence does not establish.
Separate movement logic from frame pacing
A delayed or jerky movement can look like the wrong action when frames are missed. Watch whether the final facing direction changes or whether the character ends in an unexpected position without turning. The known Shift report concerns rotation replacing sideways movement, not every animation that looks abrupt.
If the problem appears only in a large hub and comes with visible stutters, consult performance guidance as a separate line of investigation. Do not assume that the Shift workaround addresses it. Conversely, a consistent clean turn after a directional input is not the same as a low frame rate merely because both disrupt navigation.
A short recording can help distinguish the cases if you choose to submit feedback. Capture the input description and the resulting motion in a quiet scene. Avoid adding a long route that obscures the single action under discussion. The developer needs to see the difference between expected and actual behavior clearly.
Recover the session conservatively
If tapping Shift works, continue from a state you understand. Check your immediate surroundings before resuming a complex sequence, since an unexpected turn may have changed your view of the room. The control issue may be resolved while your mental orientation still needs a moment to catch up.
If the workaround fails, pause and document the state before making larger changes. You can try ordinary session recovery, such as returning focus to the game or restarting it after using its normal save options, but these are general steps rather than a demonstrated fix for this title. Do not promise that a restart will restore every affected state.
There is no verified need here to delete configuration files, remove saves, or use undocumented console commands. Those actions would add risk and make the original symptom harder to compare. Keep recovery proportionate to the narrow input problem and use the game's supported menus where possible.
Make a useful reproduction note
Write the starting condition, the transition, the input, and the result. For example, describe that you were using a particular controller, opened and closed the overlay, then pressed left and saw a turn instead of a step. Add whether Shift restored normal behavior. This is a report format, not a claim that the sequence will reproduce on every machine.
Include whether custom bindings or other input software are involved. You do not need to list unrelated applications, but anything intentionally remapping the device is relevant context. Mention the operating system, storefront, and game update information you can find without guessing.
Separate results you observed from causes you suspect. You may observe that the issue followed the overlay and suspect that the modifier remained active. Labeling the suspicion as such helps the developer use the observation without inheriting an unsupported diagnosis. It also keeps other players from treating your theory as a confirmed fix for different symptoms.
Use Give Feedback when the issue persists
The publisher has directed players with problems to the in-game Give Feedback option because it sends logs that can help investigation. For this movement issue, include the exact symptom and the small sequence that preceded it. If you want the developer to follow up, provide a contact address in the report as requested by the publisher's support guidance.
Keep one report centered on one behavior. A concise account of rotation replacing strafing is easier to investigate than a bundle of unrelated graphics, puzzle, and controller complaints. You can mention another symptom if it occurs at the same moment, but explain the connection rather than assuming they share a cause.
If you post publicly, link the September 6 developer answer and say whether its workaround helped. That lets the next reader distinguish a matching case from an unresolved variation. Do not title the post as a universal fix unless the evidence actually supports that scope.
If the problem returns
Note how often it recurs and whether the same transition appears before it. A single successful recovery is useful, but recurring behavior may reveal an additional pattern. Keep the notes brief enough that you will actually maintain them: date, input device, preceding transition, symptom, and result of the Shift press.
Do not repeatedly reconfigure controls between occurrences unless you are testing a specific mapping hypothesis. Otherwise each recurrence happens under a new setup and becomes harder to compare. A stable configuration produces more useful evidence than a series of unrecorded attempts to improve everything at once.
If a later official update mentions input handling, check whether it addresses this specific issue before assuming it has been fixed. An update existing is not evidence that every reported bug was resolved. Until a confirmed fix or your own consistent observations establish otherwise, describe tapping Shift as a workaround rather than a permanent repair.
Help another player without overgeneralizing
When sharing the advice, lead with the exact symptom: left and right rotate instead of moving sideways, especially after the overlay. Then give the developer's suggested Shift press and link the source. That short scope helps someone decide whether the advice fits their case before changing anything.
If the other player describes drift, no input, or a crash, do not force the same answer onto it. Ask what the character does after one deliberate input and whether the final orientation changes. A careful distinction can save them time and produce a better report than a collection of unrelated tricks.
You can also explain that the source involved a controller user without claiming that every controller has an equivalent shortcut. Encourage them to check their actual mapping and use the documented keyboard action where available. Preserving the source's limits makes the workaround more trustworthy, not less useful.
Return to the puzzle with a clear state
Once movement behaves normally, take a moment to identify your standing surface, facing direction, and the objects involved in the next move. An input disruption can break your mental plan even if it changes little in the room. Rebuilding that local understanding is often enough to continue without restarting the puzzle.
Keep the support problem separate from the puzzle's logic. A turn caused by a modifier does not prove that the room requires a hidden movement technique. Likewise, a difficult route does not prove the controls are malfunctioning. Compare a simple deliberate action with the configured behavior before deciding which problem you need to solve.
The verified action here is small and specific. Use it first when the symptom matches, then gather precise evidence if it does not. That approach preserves your setup and gives the developer information that can support a real investigation instead of replacing one uncertain input state with several untracked configuration changes.
Classify the result of the Shift test
There are several useful outcomes from the first test. If a single press and release restores sideways movement immediately, record that result and the transition that preceded the issue. The observation supports using the documented workaround in that session. It does not tell you whether the overlay, a remapping layer, or another transition produced the original input state.
If nothing changes and the character still turns cleanly on every left or right input, inspect the actual mapping and the state of the modifier before moving to unrelated graphics changes. Your case may still concern input interpretation, but it has not responded to the known recovery step. That distinction belongs in the report.
If the result changes only on one device, record which device and how you isolated it. Avoid describing the test as a complete fix if the other device still behaves differently. A device-specific result is valuable because it narrows the comparison, even though it does not identify the cause by itself.
If the movement is irregular rather than a consistent turn, return to the symptom description. You may be observing a timing problem or two overlapping issues. State the final position and facing direction after a deliberate input. That simple observation is more useful than forcing every awkward motion into the Shift explanation.
If the test is inconclusive because the room state changed or another input occurred, say so and repeat only a small clean check if practical. Do not count an unclear attempt as evidence for or against the workaround. A report can honestly include that you tried it but could not determine the result under the circumstances.
These outcome categories let you stop at the right point. A successful recovery can return you to play, a clear failure can go into feedback, and an ambiguous result can prompt a narrower observation. None requires a full reset of your controls or a speculative claim about the game's internal input code.