Check the current patch and known issues
Before changing files or settings, check Jagex’s 1.0.1 update notes and the 1.0.1 known-issues thread. The update lists fixes for disappearing world saves and a catch-up option for some corrupted character saves; Jagex also noted that other save issues could remain. The known-issues thread lists additional save, crash and controller problems, so an old generic workaround may not fit the current build.
Protect the save, then test one change
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.
Record the failure before changing the save
Reproduce the failure once and record the platform, game version, world type, last action and whether it happens at launch, world load, save, combat, building or traversal. Check the current issue list before trying a workaround.
If the problem began after a mod or settings change, test one change at a time on a copy or a disposable world. Avoid repeatedly opening a world that may be damaged. For performance symptoms, compare the same scene and settings so the next test has a clear result.
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.
First low-risk checks by symptom
| What you see | Start here | Do not do first |
|---|---|---|
| The game crashes before the menu | Update the client and verify the installed files; then test without 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.
Report a repeatable issue
If the problem remains, send a report with the exact reproduction steps, what you were doing, how often it occurs, and whether it also happens in a new world. For a multiplayer or dedicated-server issue, note which players are affected and include the server build and recent changes. Keep the affected save intact while you wait for current guidance.
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. The current patch notes and a concise reproduction report are the next useful steps when the low-risk checks do not resolve it.