Blog · Editorial note

How we keep Scritchy Scratchy guides current

Published August 27, 2026 · Updated August 27, 2026

A guide is more useful when readers can tell which facts are official, which advice is editorial, and which details need checking after an update.

Start with the primary source

For platform, developer, publisher, release, demo, and feature claims, we start with the official game pages and store listings. The official itch.io page is especially important for the browser demo boundary; the official Steam page is the reference for the full release listing and public achievement wording.

A source link is not a substitute for reading the current page. Prices, review counts, inventories, rankings, and version numbers can change, so those details are either dated or left out of evergreen advice.

Separate facts from route advice

“Scratch Bot scratches a ticket placed in it” is a mechanic claim sourced from the game description and developer explanation. “Add it after one stable ticket” is strategy advice based on how a player can reduce risk. They belong together for usefulness, but they should not be presented as the same kind of fact.

This distinction is why the focused pages use cautious language around exact values and prompts. A guide can explain a decision without inventing a fixed percentage or promising that every build behaves identically.

Recheck screenshots and version-sensitive systems

Screenshots are interface evidence, not permanent specifications. When a patch changes a panel, adds cosmetics, or fixes a result, the current game and official update notes outrank an older image. This matters most for Night Market inventory, Final Chance claiming, achievement cleanup, and mobile behavior.

If a page depends on a precise current-build observation, the observation should include enough context to reproduce it. Unsupported “I tested this” language is not added simply to make a guide sound more authoritative.

Corrections stay reachable

Readers can use the broken links and corrections page to report a dead source, stale sentence, missing image, or wrong internal destination. We check the narrow issue first, then search for duplicate copies across the site.

The update log records changes that affect more than one page. The full editorial policy explains the source hierarchy and how version-sensitive claims are handled.