Scrap Mechanic 1.0: What Actually Changed

Scrap Mechanic 1.0, released as Drilling Thunder, completes the Survival story and rebuilds much of the progression around it. The official release material highlights new NPCs, Miner Island, more than twice as many enemy types, the Clay Gun, achievements, garments, a health-point system, world changes, and broad resource and crafting balance work. Those systems touch exploration, combat, production, and the order in which a new save unlocks capabilities.

That scope creates a version boundary for guides. A pre-1.0 route can still sound plausible while using a removed world location, an old recipe quantity, yesterday's raid timing, or a station that now depends on a schematic. The useful question is no longer only “does this item exist?” but “does this acquisition path still exist in the current build?”

Crafting and acquisition advice ages fastest because one output may now have several legitimate routes. A component can be produced by a timed station, traded at the Mining Hub, or locked behind a schematic. Combining those routes into one imaginary ingredient list produces a neat-looking answer that cannot be executed in game.

Raid advice also needs a reset. Version 1.0 starts the threat sequence shortly after crops are detected rather than preserving the familiar overnight waiting model, and the current logic applies crop values, threshold bands, multiplayer scaling, weighted group selection, and live timing rules. Historical calculators remain useful for understanding the old system, but they are not evidence for 1.0.

• Re-check recipe quantities and station names instead of trusting an old screenshot.
• Treat schematic requirements as progression gates, not as extra ingredients.
• Do not convert internal blueprint shape counts into Survival crafting cost.
• Separate a documented rule from a random outcome such as the exact next raid wave.

Start by rebuilding your information map. Identify the current quest objective, note which workstations are available, and check the exact route for the next required item before collecting a large stockpile. This keeps early gathering tied to an immediate unlock instead of an obsolete progression checklist.

When a recipe is schematic-gated, plan around what you can produce now. A schematic flag does not mean the item is impossible; it means the chosen production method is not yet available. Search for an alternate station or trade route, then compare that route with the cost of pursuing the unlock.

Deterministic records are good calculator inputs. Recipe quantities, per-batch output, crafter speed, slot count, quest successor links, crop values, and raid thresholds can be traced and tested. A planner can therefore round batches, carry surplus, expand dependencies, and report the remaining base materials without inventing missing rules.

Random selection, physical simulation, pathfinding, spawn placement, and undocumented engine behavior need a different standard. For example, current raid data can calculate the budget band and multiplayer modifier, but not guarantee the exact enemies or spawn positions in a future wave. Reporting that boundary is more useful than presenting false precision.

Use the item database when the question is factual: what an item is, where it is produced, which recipes consume it, or whether a route requires a schematic. Use the crafting planner for a concrete build quantity, the raid calculator for threshold and budget analysis, and the quest index when you need the next objective or reward structure.

For a discovery-focused playthrough, search only when a decision has a meaningful cost. Verifying a 200-unit material plan prevents busywork without revealing every story beat. The result is a current, evidence-led playthrough that still leaves room for exploration.