ABOUT THIS RESOURCE
About ScrapMech Wiki
ScrapMech Wiki is an independent, unofficial player resource maintained by the ScrapMech Wiki Editorial Team.
- Published:
- Last updated:
Who we are
We maintain a searchable Scrap Mechanic database, practical guides, and calculation tools for players. ScrapMech Wiki is not affiliated with, endorsed by, or operated by Axolot Games.
How content is produced
Pages are maintained against the current game version shown in the footer and are reviewed when the game changes.
- Game names and descriptions use the localized text released with the game.
- Rules and values are published only when supported by current game data, reproducible behavior, or official developer information.
- Unconfirmed behavior is omitted or clearly qualified instead of being presented as fact.
Editorial and correction standards
Database changes are regenerated and validated as a connected dataset. Guides distinguish verified facts from practical advice, and tools state where an exact result ends and an estimate begins.
- Corrections are checked against the affected entity, relationship, and calculation before publication.
- Material updates change the visible and machine-readable modification date.
- Players can report factual, accessibility, localization, or rights issues through the Contact page.
Ownership and independence
Scrap Mechanic, its names, artwork, icons, and game data belong to their respective rights holders. This site uses them for an unofficial informational player reference and does not imply ownership or endorsement.
EDITORIAL METHOD
How ScrapMech Wiki turns released game data into usable answers
This site is designed as a decision tool, not a dump of internal files. Public pages connect localized names, stable identities, recipes, properties, quests, blueprint structures, and raid rules while keeping unsupported engine behavior outside exact claims.
Collection, normalization, and publication are separate steps
The update pipeline first inventories released localization, object definitions, recipes, interfaces, scripts, icons, and supported blueprint examples. It then joins records by stable internal identity and validates references before generating public web data.
Publication applies a second boundary. Internal-only objects, placeholder titles, unresolved outputs, and fields without a clear player-facing meaning are not turned into indexable pages merely because they exist in a file.
Direct facts and calculated answers use different evidence
An official name, description, icon, explicit property, or recipe quantity can be displayed directly after validation. A planner total, blueprint unit count, or raid forecast is calculated only when the released rule and every required input are represented.
Calculated pages explain rounding, weighting, parallel work, random selection, or structural counting so the result can be audited. The method matters as much as the final number when a later release changes one input.
Unknown does not mean zero, impossible, or safe
An absent property is omitted rather than converted to zero. Engine physics, live pathfinding, runtime random state, opaque controller payloads, and unobserved save state are not reconstructed from suggestive names or community repetition.
This boundary prevents false precision. It also creates a useful correction target: new evidence can fill one explicit gap without forcing the site to defend an earlier guess.
Versioning keeps a current answer reviewable
Generated coverage and rule-based tools are tied to the accepted game version 1.0.0.867. Editorial dates show when a guide or policy was reviewed, while validation tests check relationship integrity, localization parity, calculations, and public route output.
A version label is not a claim that every live-game outcome is known. It identifies the evidence set behind the answer and gives maintainers a reproducible point of comparison after an update.
See the method in practice
The public methodology reflects the repository’s accepted 1.0.0.867 evidence, validation, localization, and update procedures.