ReStory updates and known issues: Patch Notes

Direct answer

ReStory had a launch Known Issues list on August 8, 2026, followed by official patches v1.0.009r on August 11 and v1.0.010r on August 13 as displayed in the Steam Community feed. The first patch addressed the listed achievement, firmware, inventory, IDM, email, ultrawide, sonic-bath, and related device issues; the second addressed save performance and crashes, missing screws, and a Robby line issue. The patch notes confirm the developers’ stated fixes, while a current save still needs retesting before every symptom is called resolved.

What this update tracker records

This page separates an official issue report, an official fix statement, a current-build retest, and a community report. A patch note can state that a problem was fixed without proving that every old save or every reproduction path now works, so the official status and editorial retest status are kept in different fields.

The current timeline is source-dated: the launch issue record is August 8, v1.0.009r was announced on August 11, and the official Steam Community feed displays the v1.0.010r post as August 13. Future entries should name the source, version or date, and the exact claim that changed; the displayed feed date is kept as the project convention instead of silently converting time zones.

Issues named in the official launch record

The August 8 Known Issues announcement names early achievement unlocks, Guitar Legend and MyPod firmware, competition inventory, IDM disassembly, email prompts, ultrawide disassembly, and parts getting stuck in the sonic bath. The August 11 v1.0.009r announcement then states that these launch issue groups were fixed, including the Platinum Partner license achievement and related device issues.

The August 13 v1.0.010r announcement entry adds fixes for slow saves or saving crashes, devices missing screws, and a Robby-related line. These are official fix statements; the editorial retest column does not claim that the guide has independently reproduced every fix.

Patch timeline

August 8: the official launch record reports the first wave of issues and says a repair patch is being prepared. August 11: the official v1.0.009r announcement says the first patch is live and lists the launch fixes. August 13 in the Steam Community feed: the official v1.0.010r announcement says the second patch is live and lists three additional fixes. SteamDB records both named patch versions in a separate third-party index, which cross-checks the version labels and dates but not the full fix scope or current-save behavior.

As of August 19, the checked public records do not expose an auditable current Build ID. Therefore, v1.0.010r is the latest dated public patch record in this guide, not a claim about the build installed on every player’s machine. Use the Steam client’s local version when recording a retest.

The safest current wording is “officially reported and officially marked fixed in v1.0.009r/v1.0.010r; current-save retest pending.” It is no longer accurate to describe the firmware, inventory, IDM, email, ultrawide, or sonic-bath items as having no released fix.

Guitar Legend and MyPod firmware

The dedicated Guitar Legend firmware guide carries the detailed normal workflow, official bug evidence, and unofficial mod boundary. This tracker keeps the issue at the status level so the same fact is not duplicated into several competing repair pages.

The official v1.0.009r announcement says the Guitar Legend and MyPod firmware update bug was fixed. The remaining editorial question is whether the fix works on the affected current save, not whether an official fix was released. Do not promise retroactive order completion or treat an unofficial mod as necessary without a fresh reproduction.

How to verify a new patch safely

First, record the announcement date, the game version or Build ID, and the exact issue wording. Next, compare the public app record with the official note, then reproduce the affected order or device on a backed-up save. Finally, record whether the issue is fixed, still present, or needs a second retest.

Do not delete an affected save, sell a customer device, install an unknown DLL, or call a planned fix released without a dated public record. A failed retest is useful status information and should remain visible alongside the official fix statement.

What remains unconfirmed

The checked sources confirm the August 11 and August 13 Steam-feed patch releases, but they do not state a future update schedule, retroactive completion of overdue orders, compensation, achievement behavior after a mod, or compatibility of every community workaround with every build. Those claims stay marked as to be confirmed until a current source and reproducible test agree.