Scrap Mechanic Database

Search by an official item name when you already know the target. Use category filters when the decision is broader—for example, comparing interactive parts rather than looking for one specific controller. Each result opens a stable detail page, so a filtered list is the starting point and not the final evidence.

On a detail page, read game modes and category before recipes. A similarly named object may be a Creative-only building part, a Survival resource, a tool, or a quest reward. That availability changes whether a crafting route is relevant to your current world.

A production recipe explains how an output is obtained. A reverse-use relationship explains which other recipes consume the item. Keeping those directions separate prevents a common planning error: treating an ingredient use as if it were an alternative way to create the ingredient.

When several methods produce the same output, compare the station, output quantity, ingredient quantities, craft time, trade route, and schematic flag. They are separate current methods, not ingredients that should be merged into one imaginary recipe.

The accepted 1.0.0.867 snapshot exposes 992 public entities and 736 validated production or trade records for 666 outputs. Properties are shown only when the released object definition publishes them; an omitted value means the site has no supported public value, not that the property is zero.

Names, descriptions, modes, explicit variants, icons, and recipe relationships come from the same normalized identity graph. This is important after a major release because an old name or screenshot can look correct while its recipe, station, or progression requirement has changed.

First identify the exact item and verify that it exists in your game mode. Next inspect every acquisition method and choose the route available at your current progression. Then follow reverse uses to discover shared intermediate materials. Finally send craftable goals to the planner instead of multiplying a long dependency chain by hand.

This order keeps reference facts and planning assumptions visible. It also makes corrections easier: if a route changes in a later game build, you can replace that one method without rewriting the identity or every downstream use.