💾 Recovery order
If the failure is multiplayer-specific, compare the co-op checklist and dedicated-server setup; if it is combat-specific, use combat controls.
- Reproduce once and note the location, party state and last action.
- Verify the game files and update status through the platform client.
- Reduce one graphics or overlay variable at a time for performance symptoms.
- Test a new world to distinguish a global problem from a save-specific problem.
- Restore backups before attempting any manual save repair.
The verification signal is two successful loads of the affected world. If only one world fails, preserve it and report the logs and reproduction steps instead of overwriting it.
Triage before changing the save
The official site maintains a known-issues and update trail, and the launch notes distinguish fixed bugs from issues still being tracked. Reproduce the failure in a safe copy and record whether it occurs on launch, world load, save, combat, building or traversal.
Disable the last mod or changed setting, test a new disposable world, then restore a known-good save backup if needed. Avoid repeatedly opening a damaged save while changing several variables. Performance advice should record the same scene, settings and hardware each time.
Separate a crash, a save failure and a performance issue
A crash ends the process; a save failure prevents a world or character from loading; a performance issue leaves the game running but causes stutter, long frames or input delay. Record them separately with platform, build, location, action, world type, mods, recent changes and whether a new disposable world reproduces the problem.
Protect the save first. Copy the affected save, reproduce the problem on the copy, and avoid repeatedly opening the original while changing settings. Test a clean launch, file verification or update, then remove the last mod or setting change. For performance problems, repeat the same base, combat and traversal scenes while changing one graphics option at a time. Stop before any step that risks your only save.
The fastest fix for the five common failure patterns
| What you see | Start here | Do not do first |
|---|---|---|
| The game crashes before the menu | Verify files, update the client, then disable the last mod or overlay | Do not delete the save folder |
| Only one world fails to load | Copy the save, test a new world, then preserve the original for reporting | Do not overwrite the only save with a fresh world |
| The game stutters near your base | Reproduce in the same scene and reduce the newest building or graphics change | Do not change five settings at once |
| Combat inputs stop responding | Check keybinds/controller layout, then test a clean world or low-risk target | Do not assume the weapon or save is corrupted |
| Multiplayer breaks after a change | Test without optional mods and confirm a clean local join | Do not expose ports before the local join works |
This table is the practical first decision. Once the symptom is classified, follow the recovery order above and record the platform and scene for the next test.
Dedicated-server save location
For a dedicated server, logs are under C:\Users\%userprofile%\AppData\Local\RSDragonwilds\Saved\Logs, with saves in the corresponding Saved\Savegames folder. Back up the .sav file before moving or renaming anything. Recovery succeeds when the original world loads, a small change persists after leaving and rejoining, and the same failure no longer occurs.
Stop troubleshooting when the save is safe
Identify whether the problem is a crash, save failure or performance issue, protect the affected save, and stop changing settings once you can reproduce it consistently. Those exact conditions are the useful report.