Troubleshooting & Bug Reporting

Before you troubleshoot

Most problems after the Drilling Thunder launch fall into a handful of categories: an outdated client, a pre-1.0 Survival save, a mod that has not been updated, or a bug that was already fixed in a hotfix. Start by confirming you are on the latest build.

Verify your game version

1. Open Steam and go to your Library.
2. Right-click Scrap Mechanic → Properties → Updates.
3. Make sure Automatic updates is enabled.
4. Launch the game. The version number appears on the main menu and in the bottom-right corner of the pause screen.

The current patch as of early August 2026 is 1.0.5. If you are still on 1.0.3 or 1.0.4, restart Steam or verify game files: right-click the game → Properties → Installed Files → Verify integrity of game files. Full changelog history lives on the updates page.

Patch 1.0.5 — welding fix

Patch 1.0.5 addressed a critical physics regression introduced during launch week. Welded joints on bearings, suspensions and pistons were detaching under load or after a reload, which broke vehicles, elevators and automated farms overnight.

If your creations still fall apart after updating to 1.0.5:

• Re-weld affected joints. Old welds created under the broken build may not self-repair. Disconnect and reconnect the Connect Tool on every bearing, suspension and piston that was failing.
• Check controller logic. Some machines relied on pistons that no longer reached their endpoints. Review your controllers and sensors timing if a sequence stalls.
• Test after a save reload. Load the world, drive the vehicle or run the machine for two minutes, then save and reload. If joints hold, the fix is working.

Report any joint that still detaches on 1.0.5 with a save file attached — see the reporting section below.

Common launch-week issues

Old Survival saves

Pre-1.0 Survival worlds often fail to load, spawn without underground access, or miss quest markers and Schematic progression. This is expected — the 1.0 chapter was built for fresh worlds. Do not force an Early Access save into Drilling Thunder unless you have a backup.

Your options:

• Start a new Survival world (recommended for the full questline).
• Roll back to a legacy Steam beta client and keep playing the old save — see how to keep legacy saves.
• Import tested Creative blueprints through the Scrap City Garage if you only need specific vehicles or machines.

Mods and Workshop content

Many Workshop mods broke when 1.0 changed item IDs, bot behaviour and world generation. Patch 1.0.1 reduced some mod-related crashes, but authors must publish 1.0-compatible updates individually. In multiplayer, every player needs the same mod list or the host will desync.

Disable all mods, launch a test Creative world, and confirm the base game runs cleanly. Then re-enable mods one at a time. Read the full compatibility guide on mods and Steam Workshop.

Missing Creative parts

Some players reported missing Creative Mode parts immediately after the 1.0 launch. Patch 1.0.4 restored the full part library. If parts are still greyed out, verify you are on 1.0.4 or later and restart the game after patching.

Raids not triggering

Patch 1.0.3 fixed a bug where Farmbot raids would not spawn after the player reached mid-game progression. If you cleared every warehouse and never saw a raid, update to at least 1.0.3. Raids require active farm production and a minimum world age — idle bases with no crops may not attract attention.

Log and save file locations (Windows)

These paths help when reporting bugs or backing up before a patch.

Game log

%LOCALAPPDATA%\Axolot Games\Scrap Mechanic\Player.log

Paste %LOCALAPPDATA%\Axolot Games\Scrap Mechanic\ into the Windows Run dialog (Win+R) to open the folder. The log records crashes, script errors and mod load failures from your most recent session.

Survival save files

%LOCALAPPDATA%\Axolot Games\Scrap Mechanic\User\<SteamID>\Survival\<WorldName>\

Each world folder contains Game.db, terrain data and blueprint exports. Copy the entire world folder before testing a risky mod or rolling back a patch.

How to report a bug

Axolot Games tracks official bug reports at bugs@axolotgames.com. A useful report saves the team hours of reproduction time.

Include all of the following:

1. Short description — what you expected vs. what happened.
2. Steps to reproduce — numbered list, starting from a fresh load.
3. Game version — e.g. 1.0.5, Survival or Creative, solo or multiplayer.
4. Player.log — attach the file from the path above, captured right after the bug occurs.
5. Save file — zip the world folder if the bug is world-specific. For Creative test worlds, a minimal reproduction is fine.
6. Mod list — name every active Workshop mod, or state “no mods”.
7. Screenshot or short clip — optional but helpful for visual glitches.

Do not send bug reports to the wiki contact form — we cannot forward them to the developer. For wiki errors (typos, outdated guides), use the footer contact instead.

Quick checklist

Symptom	Likely cause	Fix
World won’t load	Pre-1.0 save	New world or legacy beta — legacy saves guide
Game crashes on launch	Outdated mod	Disable mods, verify files
Welds break on bearings	Pre-1.0.5 bug	Update to 1.0.5, re-weld joints
Missing Creative parts	Pre-1.0.4 client	Update to 1.0.4+
No raids	Pre-1.0.3 bug or idle farm	Update, keep crops growing
Multiplayer desync	Mod mismatch	Sync mod lists across all players