Fix launch, save and campaign softlock problems

Blizzard re-deployed 3.0.1 on October 19; its hotfix post lists build 24371. The October 7 notes warn that earlier save files cannot be loaded in 3.0.1, while progress between Chapters and Acts is retained.

Players report that mid-map saves made during the first 3.0.1 window (October 7–8) do not load on the re-deployed build either, though one player’s October 7 prologue save did. During the rollback, players also reported 3.0.1 saves missing from the 3.0.0 list while the file stayed in Documents. None of these reports proves a file was deleted, and no recovery or conversion method is known.

Exit the game before copying the remaining save and campaign-state folders to a separate backup location. Keep that backup untouched. Record the creating version, campaign or custom map, Act or mission, time and exact symptom. If you cannot establish the creating version, label it unknown rather than guessing from the current client.

This is a proposed diagnostic capture, not a test Kingy has performed. Use one save from each version window, from the same campaign or map where available: 3.0.0, the first 3.0.1 (October 7–8) and the re-deployed 3.0.1.

A file appearing in the menu, a file loading and an objective or checkpoint persisting are separate observations. Report failure without assuming deletion; check whether the backed-up file still exists.

1. With the game closed, copy the original save and campaign-state folders outside the game’s working folders. Keep the originals untouched and test only copies.
2. Show each save’s modified date and the version window it falls in, or mark it unknown. Show the installed build before every load attempt; hide account identifiers and personal file paths.
3. Load each test copy on live 3.0.1. Record whether it is listed, whether it loads, the exact error and the campaign checkpoint or objective shown. Avoid saving over the copy.
4. For each failure, restart that map and confirm that completed Chapters and Acts are still unlocked.
5. Compare the attempts and state any case not yet tested. Check that the originals remain present and untouched. Describe the result as a build-specific observation, without promising recovery.

These are diagnostic recommendations based on the published requirements. They are not confirmed fixes for every machine or error code. Change one thing at a time so you can tell what helped.

Blizzard’s current support article explicitly says Warcraft III: Reforged no longer supports offline mode. Its Legacy 1.29 client retains offline play and LAN for Reforged and Classic owners, but that does not establish Forsaken Kingdom access in Legacy. The campaign’s current store terms require Reforged, an internet connection, a Battle.net account and the desktop app. Plan for online play; the general Bonjour requirement for LAN is not an offline workaround for this campaign.

If your connection drops, check whether Battle.net itself is reachable before changing game settings. Record whether the failure occurs at login, campaign selection or after loading. That distinction is more useful to support than “the game is broken.”

Two September Blizzard-forum reports make map transitions worth treating as a save boundary. One player says purchased Agility tomes changed Anya's displayed statistics but the gain disappeared after travelling to Tirisfal Glades. Another documents an Act 2 crash while leaving the survival activity, followed by missing campaign state files and lost progress.

These are attributed reports about earlier campaign play. Kingy has not reproduced either failure. The 3.0.1 save-crash and attack-rate cache fixes are live again since October 19 but do not name these exact failures. A reload, reinstall, language change or file edit is not a guaranteed repair.

Before removing files or reinstalling, keep a copy of important saves using your normal file backup process. Do not overwrite your only working save while testing a failure.

For support, include error text, platform, campaign or custom map, Act or mission, the version that created the save and the version/branch used to load it. State whether the file still exists on disk and whether it appears in the menu. Remove account identifiers and personal information from public reports.

No universal save migration, mod compatibility or hardware performance fix has been verified for this launch edition.