Ore Factory Squad Steam Deck Crash After New Digsite
Use a save-safe isolation order when Ore Factory Squad crashes on Steam Deck after selecting or loading a newly purchased digsite.
Quick answer
If Ore Factory Squad crashes on Steam Deck immediately after you select or load a newly purchased digsite, do not delete the save or repeatedly force the same transition. Fully restart the Deck, confirm the game is current, verify the installed files, then compare one solo load with one multiplayer load. Stop as soon as the trigger is clear and preserve the save for a useful report.
Steam currently labels the game Playable on Steam Deck, not Verified. That means the game is expected to run with some possible compatibility conditions; it does not promise that every property transition or multiplayer session is crash-free.
Safe recovery order
- Exit the game completely instead of relaunching from a suspended or failed state.
- Restart the Steam Deck.
- Confirm no Ore Factory Squad update is waiting. The current official game version is v1.1.1.
- From the game's Steam properties, verify the installed files.
- Load the save and remain at the current safe location before choosing the new digsite.
- Try the transition once in solo play.
- If solo works, try one multiplayer session and record whether the host or guest crashes.
File verification is a safe installation check, not proof that damaged files caused this particular crash. If the failure repeats at the same transition after verification, move to reporting instead of cycling through random compatibility settings.
For a broader startup or post-update load failure, use the game will not load guide. If you are concerned about save state before testing, follow the Steam Cloud and save backup guide.
Isolate the trigger without risking the save
Record four facts: the game version, the property or digsite selected, whether the test was solo or multiplayer, and the exact point where the crash occurred. Useful distinctions include:
- crash when selecting the property versus after the loading screen begins;
- solo crash versus guest-only multiplayer crash;
- one save affected versus a new temporary test save; and
- crash before arriving versus crash after the property has rendered.
Do not use an important save for repeated experiments. A temporary test save can tell you whether the problem follows the property transition or one existing save, but it cannot repair the original save.
What not to change first
Avoid deleting saves, clearing cloud data, forcing an arbitrary Proton version, or changing many graphics and compatibility options at once. Those actions can destroy useful state or make the result impossible to interpret. If you test one reversible setting later, record the previous value and change only that setting.
The current player reports do not establish a graphics-memory problem, a broken property, a multiplayer-only defect, or a Proton defect. Treat those as possibilities only after the solo/multiplayer comparison.
Report a repeatable crash
When the crash survives update, restart, and file verification, send the current version, Steam Deck model, save context, selected digsite, solo or multiplayer role, and the last visible screen. Include a short video or screenshot if possible, and attach files only when support tells you which files it needs. The bug reporting guide gives a compact report format.
Sources
The current Steam store page shows the Playable Steam Deck rating. The current Steam discussion about crashes after selecting a new digsite supplies the reported trigger; it does not establish the cause or a guaranteed fix.