Unshine Arcade Patch 1.0.36

The current gamepad interaction update

Version 1.0.36, announced October 5, fixes dialogue softlocks involving the microwave and safes when using a gamepad. It also changes door and safe number pads so the joystick selects numbers instead of relying on fixed button bindings. These are the latest official release notes checked on October 8. The two changes belong together in troubleshooting because a blocked conversation and an unfamiliar number-selection method can feel similar to the player.

The announcement is brief. It does not publish safe combinations, a complete controller binding diagram, or a guarantee that every previously stuck save repairs automatically. This guide explains the confirmed scope, a practical observation sequence, and how to report a remaining issue. We do not fill those gaps with invented button names or secret puzzle answers.

Joystick number selection replaces fixed bindings

The door and safe number-pad change means old instructions based on fixed controller buttons may no longer describe the current interface. On a gamepad, check how the selection responds to the joystick and follow the prompts the installed game displays. The patch note does not name a universal confirmation button, so this page cannot safely tell every controller user to press the same labeled key.

Observe one ordinary selection before entering a whole answer. Does the selected number change when you move the joystick? Does the interface show which entry is active? Can you carry out the action indicated by the on-screen prompt? These checks establish whether you understand the selection method. They do not test whether a particular combination is correct.

If selection responds but your old memorized button sequence fails, update the procedure you are following. If selection never responds, record the controller model, game version, and screen. If selection works but submitting an answer does not, describe that later failure separately. This gives the developer the stage where input stops, rather than a vague claim that the safe is broken.

Microwave and safe dialogue softlocks

The first note explicitly identifies gamepad use in microwave and safe dialogue softlocks. A softlock is a state where the game remains running but the interaction prevents further progress. The announcement does not describe every trigger, so this page uses observable symptoms instead of claiming that one exact sequence reproduces the problem on all devices.

When you reach the interaction, check whether the current conversation can finish and whether the next expected action becomes available. If the screen remains on dialogue and ordinary prompted input does nothing, record that state. Include whether you began the interaction with the gamepad and whether any other dialogue remained visible. Do not deliberately force a progress-blocking state while testing.

If the interaction now completes, check its result in the relevant place rather than assuming a missing item from an empty nearby surface. For microwave rewards, the developer describes automatic receipt after dialogue, with a green disc and 360 Shot unlocked at the Datamachine next to the skill tree. Our 1.0.35 guide explains those reward checks in more detail.

How this differs from the previous patch

Version 1.0.35 fixes the microwave being saved as open before collecting its reward and a final-safe softlock where the previous dialogue remained open and the next did not start. Version 1.0.36 adds gamepad-specific dialogue fixes and changes number selection. The notes describe related interactions, but not identical symptoms. A saved-open microwave and a joystick that does not select numbers need different evidence.

If your microwave is already open without the expected rewards, use the saved-state checks from 1.0.35. If you cannot finish a conversation while using a gamepad, note the dialogue state for 1.0.36. If a door or safe accepts input but rejects an answer, look at the puzzle information rather than treating the rejection as proof of either softlock. More than one observation can belong in a report, but keep them distinct.

Neither note states that installing a later patch retroactively grants every missing reward or reconstructs every blocked save. Record whether the state existed before updating. A fresh interaction that works after the update is encouraging, while an older blocked state may still require developer help. That difference is the reason to preserve your save instead of assuming a restart is the only solution.

A safe check for an existing controller save

1. Record the installed game version and controller model. If an update is available, install it before comparing behavior with these notes.
2. Keep the current save intact. Do not overwrite it with a new game or an unverified repair file.
3. Identify the exact interface: microwave dialogue, safe dialogue, door number pad, or safe number pad.
4. Observe the current prompt and selection state. For number pads, check joystick selection with an ordinary input rather than an old fixed-button sequence.
5. If dialogue completes, check the resulting progression or reward. If it remains blocked, capture the screen and last successful action.
6. Report a persistent problem with the version where it began and the version currently installed.

This sequence avoids changing several variables at once. Switching controllers, starting another save, and guessing new codes simultaneously would make any improvement hard to explain. The aim is to determine whether the corrected interaction works in your current state, not to manufacture a risky reproduction of a bug that may already be resolved.

When a code is rejected but controls work

A responsive number pad can still reject an incorrect code. That response does not establish a control regression. Check where the code came from and whether it belongs to this playthrough and this interface. A historical demo discussion says PINs are randomly generated and can be obtained from a red gacha in the claw. It does not establish a universal numeric code for every released-game safe.

Likewise, console cheat codes are a separate subject. The developer's earlier demo announcement says the console displays available cheat codes, but we have not verified a complete current full-game string list. Do not enter a console instruction into a door number pad or treat a trainer website's download as a developer-provided code. Our codes guide explains which evidence supports which action.

For a rejected answer, record the prompt, source of the answer, and feedback. For a control failure, record which input does not respond. This distinction makes the report useful even if you have not solved the puzzle. It also prevents a troubleshooting page from spoiling an answer that the source material has not actually confirmed.

What to include in a remaining gamepad report

Start with the controller model, platform, installed version, and interface name. State whether joystick selection works, whether the prompted action works, and whether dialogue is visible when input stops. Include the last successful action and the first failure. If you changed input devices while testing, explain when; otherwise the reader may assume the same device was used throughout.

Say whether the save was already stuck before the update. A report about an older persistent state is different from a new interaction failing on 1.0.36. Where possible, attach a screenshot showing the prompt and active selection, or a short clip of the nonresponsive input. Avoid uploading save contents publicly. The developer can request a specific file privately if the visible evidence is insufficient.

If you are unsure whether progress advanced, name the reward or task you expected. For microwave rewards, distinguish the green disc from the Datamachine unlock. For a safe, distinguish opening behavior from the answer you entered. A report grounded in these observable details is easier to investigate than a claim that all controller controls are broken.

Continue with the right task after the fix

Once the interaction works, return to the task that brought you there. The tickets guide helps identify a next spending or progression question, and the machine guide separates machine roles from puzzle interfaces. If a hidden gacha is absent from the Datamachine, that display behavior belongs to 1.0.34 rather than this controller patch.

Use the guide directory to compare the four release patches without treating the newest page as a complete changelog for every system. This page will be updated when there is verified information about its specific interactions. A new version number alone is not a reason to rewrite the evidence or claim that an unresolved puzzle has been solved.