Unshine Arcade Patch 1.0.33

Version 1.0.33 at a glance

The September 29 update addresses a crash when Steam is set to Chinese, a final-boss reset issue, missing or incorrect upgrade descriptions, two attack behaviors, and enemies spawning too close during a secret mission. These are the first release fixes covered in our patch directory. This page explains which symptom belongs to which note, and what information to collect if it remains on a later build.

The update is historical. Current official notes checked on October 8 reach version 1.0.36. Read this page when identifying an old issue or understanding an ability change; use the later pages for hidden-gacha display, microwave rewards, and gamepad safe controls. A newer version number does not prove that a particular old save was automatically repaired, so record both your installed build and when the problematic state first appeared.

Crash when Steam is set to Chinese

The note explicitly fixes a crash associated with Steam being set to Chinese. That is more specific than saying every Chinese translation problem was fixed. It identifies the client-language condition for a crash, while the separate localization note concerns text. If you saw a crash on launch or during use with that setting, update the game before treating it as a hardware or save failure.

For a continuing crash, write down the Steam language setting, game version, operating system, and the last visible screen. Say whether the game closes completely, freezes, or remains open with an error. These are different symptoms. Avoid deleting progress as a first step: the patch note does not say a corrupted save causes this crash, nor does it prescribe removing save files.

If you changed the language while diagnosing the problem, include the before-and-after observation. A change in behavior is useful evidence, but it does not establish that every crash has the same cause. The official statement covers one reported case. A current-build crash under another language or at another point should be reported with its own reproduction details rather than forced into that explanation.

Final-boss death and the reset issue

The developer describes a problem where dying at the wrong moment during the final boss could cause the game to reset, and directs players to a spoiler discussion for more context. This page does not expand that brief note into an invented ending walkthrough. Its practical value is identifying a state-reset symptom that was acknowledged in the release update.

If it happened to you, preserve the existing save and record the sequence you remember: the encounter state, whether death occurred, what the game showed afterward, and which progress appeared changed. Do not describe an ordinary failed run as the documented reset without checking what actually changed. Losing the current run and losing broader arcade progress are not automatically the same event.

The note gives no public universal repair steps or promise that an already-reset state can be restored by updating. If your save is still affected, ask the developer with the version and observed state. Keep ending details behind an appropriate spoiler warning in a public discussion. You can provide a narrow technical description first and supply a private save only if the developer requests it.

Chain Lightning Shot: once-only application

The note makes Chain Lightning Shot apply only once. This is not a fix for an ability failing to trigger a second time; the developer names a once-only application rule. The announcement does not explain every interaction or publish timing and damage values. Avoid turning that terse wording into a guarantee about every repeated attack.

A developer reply in the community says some effects stack and gives Bullet Bounce as an example: another copy adds another bounce, and copies can be upgraded. That example should not be turned into a rule that all gachas stack identically. Use the description of the actual ability you have and observe its behavior in the relevant game mode. The gacha guide keeps those pieces of evidence separate.

If Chain Lightning behaves differently from an older video, record the exact effect name, number of copies and current version. Keep the observed result separate from your expectation. The developer’s once-only application wording does not establish an undocumented cooldown or a promise that duplicate copies multiply the effect. A focused comparison is more useful than a complaint that the build feels weak.

Laser kills and multiple targets

The laser fix changes the issue where enemies were killed one at a time rather than all being killed instantly. The wording establishes the corrected attack behavior in the reported case, but gives no numerical damage table, upgrade cost, or complete list of eligible targets. Avoid importing those details from another game's laser system or an unsupported community estimate.

When checking the fix, note the targets you were attacking and the visible sequence of deaths. Were several enemies in the same attack area, or did they enter it at different times? That observation helps distinguish the reported sequential-kill problem from separate attacks against separate targets. If you cannot tell from a single screenshot, describe the uncertainty rather than claiming a regression.

For a loadout choice, read the current item description and compare the result in your own run. The fact that a bug was fixed does not prove that the laser is universally the best weapon. Your current encounter, unlocked options, and ability interactions still matter. Use the beginner guide for choosing a next experiment without relying on an unsupported tier list.

Enemies spawning too close in a secret mission

The update also fixes enemies spawning close to the player during a Space Frog secret mission. This is a location-and-state-specific correction. It does not publish the route to the mission or identify every possible close spawn in an ordinary generated level. Keeping that boundary matters if you are trying to report the same issue without accidentally presenting an unverified secret route.

If the symptom remains, include whether you were in the named type of mission, how the encounter began, and whether enemies appeared immediately beside the player. Record the installed version and whether the run started before or after updating. Those details help the developer distinguish a saved state from generation behavior in a fresh run. Do not start a replacement save merely to test one spawn.

For ordinary survival, observe the room before committing to an attack and note where pressure comes from. This is a practical learning step rather than a new game mechanic promised by the patch. If the problem is a visibly glitched active map point instead of enemy placement, see 1.0.34, which contains the separate rare-generation fix.

Language and missing upgrade descriptions

The remaining text changes are described as minor language fixes and missing upgrade descriptions. They can affect your understanding of a purchase even if they do not change the underlying effect. A clearer description should be checked before spending based on an old screenshot. The announcement does not enumerate every revised string, so this page cannot offer a full old-versus-new translation table.

If an upgrade still has no useful description, record the exact displayed name, language, menu, and version. Say whether the field is blank, truncated, or present but unclear. These are different problems. A screenshot of the menu can show both the selected entry and adjacent context without requiring you to expose save files or guess an internal item identifier.

Do not assume that a missing description means the upgrade has no effect. Equally, do not invent the effect from its name. Delay a purchase you cannot evaluate, or ask for clarification with the item details. This is particularly useful for duplicates: the confirmed Bullet Bounce example does not fill every missing description in the pool.

Checking this patch against your current game

1. Record the installed version rather than relying on the date of a guide.
2. Choose the specific symptom above: language crash, state reset, Chain Lightning application, sequential laser kills, close mission spawn, or missing text.
3. Note whether the save or run already existed before the update.
4. Repeat only an ordinary, safe interaction needed to observe the symptom. Avoid deliberately recreating a progress reset.
5. Keep the save and submit a focused report if the problem persists on the current build.

The next patch page covers different failures, not extra steps for all of these. For microwave reward state and unfinished dialogue, go to 1.0.35. For controller number selection and microwave or safe softlocks, go to 1.0.36. A dated patch directory is most useful when it lets you identify the right report quickly and stops historical advice being mistaken for a current universal fix.