Beast of Reincarnation Save Data Not Recognised After a Shutdown
A developer has read this report and answered without a fix, which is rare enough to state plainly. No recovery procedure exists, and no save-file location has been published that would let you back one up first.
Nobody has published a recovery procedure, and nobody has said whether the data is recoverable at all. What is unusual about this report is the reply: a developer answered it and did not offer a solution. That is not the same as being ignored, and it is not the same as being fixed.
Where this is being asked · By players who lost power or force-quit and came back to a game that no longer sees their save. It is the highest-stakes report in the launch bug thread, because every other entry there costs you a session and this one can cost the run.
A grade describes sourcing, not truth. Inferred means we concluded it and the reasoning is shown; unverified means someone asserted it and nobody stands behind it.
UnverifiedThe game can stop recognising save data after an unexpected shutdown.
One reporter in the launch bug megathread. No second report and no reproduction.
CorroboratedA developer has read the report and has not published a fix.
The developer reply sits in the same thread as the report. This is the one part of the entry that is directly observable rather than reported.
InferredNo precaution can be recommended, because no save-file location has been published.
Ours. Backing up the save folder is the standard defence and requires knowing where it is. Nobody has posted that, so the advice cannot be given without inventing a path.
§01
What was reported, and what makes it different
After an unexpected power loss or a hard shutdown, the game stops recognising existing save data. One reporter in the launch bug megathread. What separates it from the other twenty-odd entries on our known-issues page is that a developer replied to it — and the reply contained no solution. Most reports there have no developer response at all, so it is easy to read silence as "not seen yet". This one has been seen. It still has no answer, and that is worth knowing before you decide how much to trust the autosave.
§02
The thing nobody has published, which is the thing you would want
A save-file location. If anyone had posted where the saves live on disk, the honest advice on this page would be "copy that folder now, before it happens to you" — the standard defence against exactly this class of bug. Nobody has, on either the forums or the established wikis, and this site has not established it either, because doing so means running the game. So the useful precaution exists in principle and cannot be given here yet. That is a gap in what is published rather than a statement that the files are unreachable.
§03
What not to do with the advice circulating
Nothing is circulating, which is its own kind of warning. There is no verified fix, no half-verified fix and no plausible-sounding guess doing the rounds — the report simply sits there. If you meet a page confidently describing how to restore a Beast of Reincarnation save, check what it cites, because as of the date on this page there is nothing to cite.
§04
What reduces the risk in the meantime
Only general practice, offered as general practice and not as a fix. Close the game through its own menu rather than force-quitting where you have the choice; a clean shutdown is the condition the report says was absent. Steam Cloud, where it is enabled for your install, keeps a copy off the machine — though nobody has tested whether it helps in this specific failure, and a cloud copy of a save the game refuses to read may be no better than the local one. Neither of those is verified against this bug and neither is presented as one.
Expiry condition
What would have to change for this answer to be wrong
An answer about a live-service game without this is an answer with a hidden expiry date.
The developer publishes a recovery procedure, a patch addresses it, or any player posts the save-file location — that last one would let this page carry a real precaution rather than a description of a missing one, and it is the smallest thing that would change the most here.
Citations
Every source, with its date
A complaint posted before 30 July 2026 describes the playtest, not the game you bought, and a source whose publication date nobody captured cannot show that it postdates launch either. Both are flagged rather than quietly mixed in.
That a player reported the game no longer recognising save data after a sudden shutdown, and that a developer replied to that report without offering a solution. Read 2026-08-05. The post rendered with a relative timestamp when the thread was read, so the date is approximate. It establishes the report and the reply; it establishes nothing about the cause or about how common it is.
Related questions
Nobody has published an answer either way. The one report of this has a developer reply attached and no solution in it.
