CONTACT & CORRECTIONS
Contact ScrapMech Wiki
Send corrections, accessibility feedback, privacy questions, rights requests, or other site-specific enquiries to the editorial team.
- Published:
- Last updated:
What to contact us about
The contact address is for ScrapMech Wiki content and operation. For game support, purchases, accounts, or bug reports, use the official Scrap Mechanic channels instead.
- Incorrect item, recipe, quest, raid, blueprint, or calculation data.
- Broken links, missing images, accessibility problems, or localization errors.
- Privacy questions, copyright or trademark concerns, and rights-holder requests.
What to include
Include the page URL, the language you were viewing, what appears incorrect, and the current game version when relevant. Screenshots are useful, but never send save files or personal information unless it is necessary for your request.
Privacy and response scope
This page does not submit or store a form. Selecting the email link opens your own mail application. Messages are used only to review and respond to the enquiry, subject to the Privacy Policy.
CORRECTION GUIDE
How to report a data error or rights concern effectively
A concise, reproducible report is easier to verify and safer to act on than a general statement that a page is wrong. Choose the relevant contact category, include only necessary information, and identify the exact public page or asset involved.
For a game-data correction, describe the mismatch
Include the page URL, displayed field, value you expected, value you observed, and the game version or branch. For a recipe, add the station and quantities; for a quest, add the visible tracker state; for a raid result, include crops, players, and whether groups had already generated.
A screenshot can show the mismatch, but a current released definition, official announcement, or reproducible sequence is stronger evidence. Do not send an entire save, installation folder, or private account data unless it is specifically requested after the initial report.
For a site bug, include the smallest reproduction
State the route, language, device or browser, action taken, and visible result. If the problem is intermittent, note whether a refresh changes it and whether the same issue occurs without search parameters.
Copy the exact error text when it is visible, but remove email addresses, local file paths, account names, or other personal details that are not needed to reproduce the interface problem.
Privacy, copyright, and attribution requests need a precise target
Identify the page, image, text, or processing concern and explain the relationship to your request. Rights notices should include enough information to locate the material and understand the claimed ownership without publishing unnecessary personal documentation.
The public contact route uses an email link rather than a hosted form. Opening that link transfers the message to the user’s chosen email service; no message body is submitted through ScrapMech Wiki itself.
What happens after a useful correction arrives
A report is checked against the accepted evidence boundary and current public snapshot. A confirmed source-data change may require updating the extraction pipeline and regenerating related pages rather than editing one visible sentence by hand.
Not every disagreement can produce a precise value. If the game leaves a result to engine behavior, random state, or live world conditions, the responsible correction may be a clearer limitation instead of a new number.
Review the relevant policy before writing
For safety, begin with the minimum information needed to identify and reproduce the issue; additional files or personal details are not required for an initial report.