Finish your current campaign act on 3.0.0 if your saves still load, then check that the next chapter or act is unlocked. Completed campaign milestones are expected to survive the version change; an individual checkpoint may not. That distinction determines how much progress you could lose when 3.0.1 returns.
Which saves work after the rollback?
Blizzard restored version 3.0.0 to give players more time to finish their active acts. That helps players with older saves, but it creates another compatibility problem for anyone who saved while 3.0.1 was live.
| Save or progress type | What to expect on 3.0.0 | Practical consequence |
|---|---|---|
| Existing saves from 3.0.0 | Should generally remain usable | Continue the campaign and finish the active act before the next update. |
| Saves created under 3.0.1 | May disappear from the load menu or fail to load | Keep the files and a separate backup; the rollback does not make them compatible with 3.0.0. |
| Completed chapters and acts | Expected to remain unlocked | You may be able to resume from an unlocked campaign entry even when a checkpoint cannot load. |
A checkpoint holds a mission in progress. Campaign unlocks record which chapters or acts you have completed. Blizzard’s preservation guidance concerns those completed milestones, so a mid-mission manual save or autosave offers less protection across this update.
What the Battle.net save warning means
The Battle.net warning flags save incompatibility. It does not promise automatic conversion or recovery. Patch 3.0.1’s notes warned that previous saves would stop working, and the live release left some manual saves and autosaves hidden from the menu or unable to load.
A save can remain on disk even when the game rejects it because its build does not match. Keep those files. Deleting them removes any opportunity to use them with a compatible build later.
Blizzard plans to keep 3.0.1 on the public test realm for additional testing before redeploying it. There is no firm return date, and players should not assume the next release will convert every existing checkpoint.
What to do before 3.0.1 returns
- Back up before continuing. Close the game and copy the entire Warcraft III save folder to a separate location. Label the archive with the date and build number. Keep 3.0.0 and 3.0.1 backups separate rather than replacing one with the other.
- Record your current chapter and act. Note the last completed milestone. Create a clearly named manual save before the final stretch of the active act, treating it as protection within the current build rather than protection against the patch.
- Finish the act while your saves work. If you can complete it in the current session, avoid stopping at an intermediate checkpoint. Completed chapters and acts are the progress boundaries Blizzard says will be preserved.
- Check the campaign menu, then back up again. Make sure the next chapter or act is unlocked. Close the game and create a second archive, keeping your earlier backup intact.
- Avoid unnecessary build switching. Moving between 3.0.0 and 3.0.1 can leave checkpoints inaccessible. Preserve any 3.0.1 files even if the current live build cannot display or load them.
FinalBoss // Gear
Level up your setup
01Top-rated gaming headsetson Amazon→02High-refresh gaming monitorson Amazon→03Gaming chairson Amazon→04Discounted game keyson Kinguin→Affiliate links · As an Amazon Associate, FinalBoss earns from qualifying purchases.
Want to Level Up Your Gaming?
Get access to exclusive strategies, hidden tips, and pro-level insights that we don't share publicly.
Ultimate Tech Strategy Guide + Weekly Pro Tips