Unshine Arcade Patch 1.0.35

What version 1.0.35 fixes

The October 3 update fixes the microwave being saved as open before the reward was collected, a final-safe softlock where the previous dialogue remained open and the next dialogue did not start, and minor language issues. These changes concern saved interaction state and dialogue sequencing. They are not a new microwave code list, a safe combination guide, or a guarantee that every previously affected save repairs itself.

Version 1.0.36 followed on October 5 with additional microwave and safe dialogue fixes for gamepad users, plus joystick selection for number pads. If you are troubleshooting now, check that later version too. This page explains the specific 1.0.35 problems and how to distinguish them from a wrong puzzle answer, a control issue, or an ordinary progression question.

The microwave saved as open before its reward

The first fix describes a mismatch between the saved microwave state and reward collection. The microwave could be recorded as open before the reward had been collected. A player might therefore see an already-open interaction without the expected result. That description is narrower than saying all microwave problems were fixed, and it does not tell us how every old save responds to the update.

Start by recording what you see. Has the relevant dialogue completed? Does the microwave appear open? Did you receive the reward associated with the interaction? Have you already closed and reopened the game since it happened? These observations separate an interrupted conversation from a saved state that persists across sessions. Do not try to force a reset by editing a file or deleting the save.

A developer reply in the community gives useful reward context: the items are received automatically after dialogue; the reward includes a green disc and unlocks 360 Shot at the Datamachine next to the skill tree. That reply addresses a specific microwave report. It supports checking both reward locations, rather than assuming that nothing happened because one item was not obvious on screen.

Check the reward in the right place

First check whether the dialogue finished normally. Then look for the green disc and, when you reach the relevant Datamachine skill tree, the 360 Shot unlock described by the developer. An immediate inventory check and a Datamachine unlock check answer different questions. Do not treat an unlock that appears in the Datamachine beside the skill tree as an item that must be lying beside the microwave.

If one reward is present and the other is not, report them separately. Say which menu or location you checked and whether that was before checking the Datamachine. This prevents a report about a delayed or overlooked unlock from being merged with a report where neither reward was received. Avoid treating the microwave reward as a randomly drawn hidden gacha without evidence; the developer describes a particular dialogue-linked reward.

If both are missing after the appropriate checks, preserve the save and ask for help. The developer offered a manual save repair for one reported case. That is evidence that a specific state could need individual assistance, not a public recipe for changing save values. Following an unrelated reset instruction may remove the evidence needed to repair your own state.

What updating can and cannot tell you

Updating lets you test the game with the corrected behavior installed. It does not, by itself, show that an older affected state has been reconstructed. The patch announcement does not state whether all existing microwave saves receive a migration or whether every missing reward is granted retroactively. This guide therefore avoids promising a recovery that the source does not describe.

Record whether the problem began before updating and whether the same state remains afterward. If the game now allows the interaction to finish, note what reward appears. If it still shows an open microwave with no completion path, describe that persistent state. Those are materially different results, even though both started with the same patch note.

Do not repeatedly start over to test whether a fresh save behaves differently. A new save may avoid the old state while sacrificing the progress you want to recover. If the developer asks for a fresh-save comparison, keep the original intact and make the comparison separately. For ordinary self-checking, your existing version and reward observations are enough to begin a useful report.

The final-safe dialogue softlock

The second fix concerns a final-safe state where the previous dialogue was still open and the next dialogue did not start. That state could leave the interaction stuck. That is a sequencing issue, rather than proof that the combination is wrong. A wrong answer that the game accepts and rejects is different from an interface that no longer accepts input or a conversation that never closes.

Check which part has stopped. Can you select a number? Can you submit an ordinary input? Is dialogue still visible? Did the previous conversation remain open while the next failed to start? Record the last successful action. The patch note does not provide the safe solution, so these checks should focus on whether the interaction works rather than on guessing a numerical answer.

Where possible, capture the screen showing the dialogue state. Include your input method and installed version. If you are using a gamepad on a current build, the additional changes in 1.0.36 are relevant. That later patch also changes how a joystick selects numbers, which can make an old control instruction misleading even if the dialogue bug has been fixed.

Control failure versus an incorrect answer

Before calling a safe interaction a softlock, distinguish a nonresponsive control from an answer the game rejects. If the number selection changes normally and the interaction gives feedback, the control path is functioning at least far enough to process input. If selection never moves or a dialogue layer blocks further action, you have a different symptom to report. Neither observation reveals the correct combination by itself.

The console and puzzle-code discussion contains historical demo information about randomly generated PINs and a red gacha from the claw. It is not a verified universal final-safe combination for the released game. Copying a number from another player's screenshot may fail for reasons unrelated to this patch. Our console and codes guide explains the evidence without publishing a fabricated master code.

Keep the exact interaction names separate in your report. A door number pad, a safe number pad, the console, and the microwave are not interchangeable interfaces. Saying that codes do not work leaves the developer guessing which system you used. Name the screen, describe the input response, and mention any active dialogue before proposing that a particular patch failed.

Minor language fixes and unclear prompts

The remaining note says minor language fixes were made, but lists no exact strings. A confusing prompt may be a text issue even when the interaction works. Record the selected language, exact displayed text, and screen where it appears. If you believe the prompt conflicts with the control behavior, include both the text and what the game actually does.

A screenshot is especially useful when multiple dialogue boxes are visible. It can show whether a prompt belongs to the current conversation or one that has not closed. Avoid translating an unclear line from memory and reporting that translation as the game's original wording. The original text, version, and input method give the developer a clearer starting point.

This page does not claim the update completes every localization. The note is limited to minor fixes. If the wording remains unclear but you can continue, describe it as a prompt problem rather than a progression lock. That distinction helps prioritize a report where the save is blocked versus one where the next instruction simply needs explanation.

A concise report for a remaining 1.0.35 symptom

For the microwave, include the version where the state began, current version, whether dialogue completed, whether the microwave is open, and the result of the green-disc and Datamachine unlock checks. For the final safe, include the last working input, visible dialogue state, and whether number selection still responds. In both cases, state whether you use a keyboard, mouse, or gamepad.

Keep the original save. Do not paste personal file contents into a public thread or follow a speculative edit based on another user's state. If the developer requests a save privately, provide the specific file through that agreed channel. Our progression guide helps separate a missing reward from uncertainty about the next task, while the patch directory in all guides keeps the historical changes easy to compare.