Heroes' Vow Old-Save Issues: Checks and Official Support
An old save’s age alone does not tell you whether to restart. Match the symptom to a dated update, check your installed version, and use the developer’s support route if the specific problem persists. This page identifies documented checks; it cannot guarantee recovery.
Choose the symptom you actually have
| Symptom | Relevant official record | Useful next action |
|---|---|---|
| Cannot load a county-related save made before September 24 | v1.0.3, September 24: county-loading fix and support for affected earlier saves. | Contact the developer through the save-file route below. Include when the save was made. |
| Peddler absent after upgrading an old save | v1.0.4, September 27: old-save Peddler availability. | Check build, then General Store. If still absent, report the location and save origin. |
| Overburdened on the World Map after loading an old save | Full Version Update, September 23: optional maximum cargo-capacity setting. | Read the rules-setting option below; it is not a file repair. |
| Private-property income differs from older advice | v1.0.3: private civilian-property calculation correction. | Use the property version check; a changed number alone does not prove corruption. |
Overburdened is a different problem from not loading
For an old save that loads but leaves you overburdened on the World Map, the full-release notes offer an option under Settings → Advanced Options: set maximum Cargo Capacity to unlimited.
This changes a carrying rule. Choose it only if you want that rule change; it is not evidence that a damaged save has been repaired. If the save cannot load at all, this in-game option does not answer that symptom.
How to make the official support request specific
The September 24 notes invite players with pre-September 24 saves that fail to load because of the county bug to send the affected save to the developer’s customer-service address: 2689683364@qq.com. This is the game developer’s address, not this guide’s mailbox.
Use a concise report such as:
Game build: [your version]
Save began in: [Early Access or full release]
Save date and location: [what you know]
Character and role: [your character]
Exact symptom: [error text or observed behaviour]
Last action before the problem: [action]
Still occurs after: [checks actually performed]
Replace the brackets with your own observations. If you do not know a field, say so. Do not send account passwords or unrelated personal files. This website does not supply an unverified save-folder path or ask you to upload game saves to us.
If your symptom does not match
Do not assume these fixes cover it. Record the build, location and exact behaviour and consult the current official notes. A loading error, a missing merchant and an income adjustment should not be treated as one failure.
The developer also described an older EA branch in its September 24 plan, but that announcement does not establish that every newer save can safely move backward. This page therefore does not prescribe switching branches as a universal recovery step, deleting local files or overwriting your only save.
Check the dated entries in the developer update notes (external site) before sending a report. A published fix is not a recovery test on your save, and we do not guarantee a reply time. For the broader system changes, return to the 1.0 changes guide.