Cómo leer la base de objetos y recetas de Scrap Mechanic

Search by item name when you need identity, category, recipe, or use information. Browse categories when you are comparing alternatives and do not yet know the exact name. The accepted snapshot resolves 992 public entities, 736 recipes, and 666 distinct recipe outputs, so search and filters are faster than scanning one long list.

An item page is a junction between data types. Identity and description explain what the record represents; acquisition methods explain how to obtain it; uses show which other recipes consume it. Keeping those layers separate prevents a use from being mistaken for a recipe that produces the item.

A recipe should name the station or route, input quantities, output quantity, batch time when applicable, and any schematic requirement. Compare complete methods rather than only their first ingredient. A trade route and a timed crafting route can have different currencies, unlocks, and logistical costs.

If an item has no listed recipe, that does not prove it is unobtainable. It may be found, rewarded, spawned by progression, packaged in the world, or absent from the current recipe source. A high-quality page states what the dataset supports and avoids turning “no recipe record” into a universal acquisition claim.

A use is a recipe that consumes the current item. This view answers whether an apparently minor component is needed later and helps prioritize storage. It is also the fastest way to trace a dependency chain forward when a large project suddenly requires an unfamiliar intermediate.

Use count should not be interpreted as strategic importance by itself. One use can be a critical progression recipe, while many decorative uses may be optional. Open the consuming outputs and evaluate them in the context of your save.

Two records can share a similar display name while representing different upgrade levels, modes, or internal identities. Use the item page, category, icon, and route together. When a blueprint or script supplies a UUID, identity resolution is stronger than matching text alone.

Localization can also change the visible name without changing the underlying item. A database should resolve the official localized label where available and keep a stable slug or identity underneath, so shared links do not break when display text changes.

Every material claim is attached to a game snapshot. This site's current accepted content version is 1.0.0.867, dated July 25, 2026. A later patch may change a recipe while leaving an old article indexed, so compare version and update date when two sources disagree.

Use database facts for deterministic questions and calculators for derived totals. For random drops, physics, pathfinding, or behavior that is not fully represented in the data, look for a stated test method and uncertainty. The absence of false precision is a quality signal, not a missing feature.

• Confirm the exact item and current version.
• Read production recipes separately from downstream uses.
• Compare complete acquisition routes and prerequisites.
• Follow dependencies in both directions before spending scarce inputs.
• Treat unsupported behavior as a test question, not a guessed fact.