Scrap Mechanic 1.0 Returning Player Guide

Scrap Mechanic 1.0 world overhaul scene — The 1.0 Survival route is built around reworked terrain, story progression, new locations, mining, and new bot families—not only balance changes to the Early Access world.

Schematic Box icon from Scrap Mechanic — Schematics now gate parts of the Craftbot list. A collected box and a registered recipe are separate states, so check the Schematicbot before assuming a Craftbot bug.

World and mod compatibility boundary

Existing content	1.0 handling	Safe test
Old Creative world	Can load in 1.0	Back up, disable suspect mods, open a copy
Old Survival world	Requires an older Steam branch	Keep legacy and 1.0 saves in separate dated backups
Saved creations	Back up important builds	Open a simple unmodded copy first
Parts mods	Most likely to need updates	Verify every interactive part before saving
Custom Games	May need an updated package	Test menu load and a throwaway world
Multiplayer world	Host owns progression state	Let the host perform the final quest interaction

Public 1.0 patch checkpoints

Version	Relevant fixes	What to retest
1.0	Full story, world overhaul, schematics, Garage, mining	Start a new Survival world for the complete route
1.0.1	Schematic unlocks, recipe display, multiplayer steering, Pizzaburger	Re-register a box and recheck the Craftbot list
1.0.2	Quest progression, challenge chest items, mod menu, crashes	Retry the objective as host on a backed-up save
1.0.3	Raids, Vault quests, underground events, Thruster UI, older CPUs	Confirm the patch before rebuilding or abandoning the save

Old expectation versus current 1.0 system

System	Old habit	Current decision
Recipes	Expect Craftbot list immediately	Register Schematic Boxes with the Schematicbot
Survival map	Reuse an old route or coordinate map	Start from generated roads and current quest markers
Creative tools	Treat terrain as fixed	Use Claygun shaping and 1.0.3 Creative commands
Food	Carry any meal	Use Cookbot health and perk effects for the job
Garage	Rebuild a creation manually	Load a supported blueprint and pay its exact material bill
Bots	Prepare for the old roster	Plan for new colored, digging, mining, and boss behaviors

Back Up the Whole World Before Changing a Branch

Close the game so the save is not being written.
Copy the complete world to a dated folder outside the active save directory.
Record the game version, branch, host, and enabled mod list beside it.
Open a copied world first after changing branch or mod configuration.
Keep the untouched backup until quests, creations, and storage have all been checked.

Do Not Use a Legacy Survival World to Judge 1.0

The complete story, reworked world generation, Growlabs, Excavation Island, new bots, Schematicbot progression, and Scrap City Garage belong to the new Survival baseline. A legacy branch is for preserving an old world, not for sampling the complete 1.0 progression.

Separate Schematic Failure From Crafting Failure

Confirm the box entered the inventory.
Take it to the Schematicbot and register the matching recipe.
Check the Craftbot for the exact item rather than only the schematic icon.
If no recipe appears, update past 1.0.1 and repeat on the host.
Preserve the save before removing mods or changing branches.

Multiplayer Retest Order

Host loads the backed-up world and performs the final quest or unlock interaction.
Clients rejoin only after the objective state is visible to the host.
Steering is tested on a simple vehicle before a complex bearing creation.
One mod category is restored at a time so a failing package has a name.

When the Current Patch Still Does Not Fix the Save

A patched engine condition does not always repair state already written into a world. Keep the affected copy, record the objective and the action immediately before it stopped, and retry from the last clean backup. Repeatedly overwriting the only world removes the evidence needed to distinguish a current bug from damaged legacy state.