Version tracker · checked August 12, 2026

ReStory updates and known issues

The first post-launch update, v1.0.009r, went live on August 11. The official note lists shipped fixes; it does not prove that every player-side symptom is gone on every setup.

Current release notev1.0.009r shipped August 11, 2026

Official launch timeline

DateOfficial itemWhat it establishes
August 4, 2026Prices & Launch TimesMac at launch; Steam Deck Playable, not Verified; post-launch improvement intent
August 6, 2026Launch announcementThe full game launched
August 7, 2026Sales milestone and issue noticePublisher-reported known issues; first update in progress
August 11, 2026First Update is Live (1.0.009r)First numbered post-launch patch and its official fix list

Fixes listed for v1.0.009r

The August 11 patch note lists these shipped fixes, paraphrased to keep this tracker concise:

What the August 7 notice established

Before the patch shipped, the publisher identified the same main issue areas and said the first update was in progress. That earlier notice remains useful for the timeline, but S13 now supersedes its “not yet shipped” boundary for the listed fixes.

What is still not proved by the patch note

“Fixed” here means the developer included the item in v1.0.009r. Evidence Arcade has not performed a versioned first-hand retest across ultrawide displays, competition mode, every named gadget, or achievement state. If a symptom persists after updating, report the current build and reproduction steps through the official Steam discussion channels.

What is not the current release patch

The December 23, 2025 post titled “Major Performance Playtest Patch Version: #0.1.018” belongs to the playtest period. It is useful development history, but it must not be mislabeled as the current full-release version or a post-launch hotfix.

If your question is specifically about Steam Deck, use the current official Deck status page. For achievement boundaries, see the achievement total and known-issue note.

Update trigger

Check the official feed for the next numbered release. Keep developer-listed fixes distinct from first-hand regression tests and revise if the publisher publishes a follow-up or rollback.