Broken links and corrections

What counts as a broken link

A broken link can be a page that returns an error, an image that no longer loads, an official store URL that moved, or an internal link that lands on the wrong topic. A guide can also need correction when its source still loads but the current game no longer supports the claim.

We treat version-sensitive facts separately from link failures. An exact ticket value changing is a content update; a missing official page is a link issue; a claim that cannot be supported by either the source or the current build is a correction regardless of whether the URL still returns 200.

Legacy URLs that redirect

Some older search-facing paths remain available as permanent redirects so players do not hit a dead end. For example, the former controls page points to the controls section of the beginner guide, and the old Prestige guide path points to the current Prestige and Jack Points coverage.

The redirect is intentional when the destination contains the same answer with better version context. The canonical destination belongs in the sitemap; the legacy path should not be treated as a second copy of the article.

• /scritchy-scratchy-controls redirects to the controls section of the beginner guide.
• /scritchy-scratchy-faqs redirects to the current FAQ.
• /what-is-scritchy-scratchy redirects to the wiki overview.

How to send a useful report

Email contact@scritchyscratchy.cc with the page URL, the exact link or sentence, what you expected to happen, and the official source or current-build observation that supports the correction. A screenshot is useful when the problem is visual, but a source URL is best for changing game facts.

Please do not send passwords, payment details, private account information, or a copied comment thread. We only need the public page and enough context to reproduce the issue. Corrections are reviewed under the editorial policy and may be noted on the update log.

What happens after a report

We check the internal route first, then test the linked public source and inspect the affected page in the current build when the report concerns a mechanic. If a source is unavailable, the claim is rewritten conservatively or removed until it can be verified.

A reported issue is not automatically proof that every related page is wrong. We update the narrowest affected page, then search the site for the same link or claim so the correction does not leave a contradictory copy elsewhere.