Site update log
Scritchy Scratchy updates and patch notes
A small, dated changelog for this independent player guide. It explains what changed in the game sources we monitor and which pages should be checked when a new build changes a mechanic.
What this update page is for
This page records source checks and editorial changes for Scritchy Scratchy. It is not a replacement for the official Steam, itch.io, or developer pages. When a store page or current game build disagrees with an older guide sentence, the live official information takes priority.
The most useful reason to keep an update log is version context. Prices, exact odds, cosmetic inventories, and balance values can change without making the overall game loop different. We keep those volatile details out of broad evergreen advice and call out the pages that need a fresh look after a patch.
March 18, 2026: full release
The official Steam listing records Scritchy Scratchy as released on March 18, 2026. It lists Lunch Money Games as developer, Funday Games as publisher, and describes the game as a scratch-card incremental game built around tickets, automation, jackpots, and Prestige.
The official itch.io page separately identifies its playable HTML5 build as the free demo and points players to the paid downloadable version. Our ways to play guide keeps those products separate so a browser visitor is not promised content that belongs to the full release.
Patch 1.1: cosmetics and quality of life
Patch 1.1 added 12 Night Market cosmetics and quality-of-life changes including a Prestige confirmation, VSync and FPS cap settings, vibration settings, a Turkish fan translation, and a mobile performance improvement. It also addressed issues involving stuck coins, opened cards, upgraded ticket art, and Final Chance claiming.
The practical effect for this site is that an older screenshot or cosmetic count should not be treated as a permanent inventory. The Night Market guide and achievement guide therefore point back to the current game and official update history instead of freezing every number into the page title.
- Recheck Final Chance claiming before treating a missing result as a route failure.
- Use the current Night Market inventory when working toward Walk-in-closet.
- Treat mobile performance notes as platform-specific rather than proof that every browser device behaves identically.
How we handle future changes
A new patch should trigger a source pass, not a blind find-and-replace. We recheck official platform facts first, then inspect affected systems in the current build, update the focused guide, and leave a link to the relevant official source. Unsupported exact values are removed rather than guessed.
If you find a stale sentence, use the broken links and corrections page to report the URL and the source that contradicts it. That gives the editorial review a reproducible starting point and keeps corrections reachable after publication.