Updates · English
Known bugs tracker
A ReStory bug-reporting checklist that separates official known issues from reproducible community reports and unverified claims.
Quick answer
Scope
Updates · Known bugs tracker
Workflow
- Known bugs tracker: Record the exact game build shown by Steam or the executable.
- Write the repair item, story state, or shop screen where the problem occurs.
- Restart once and reproduce the issue with the smallest reliable sequence.
- Capture expected and actual results with a screenshot or short clip when possible.
- Check official news and community channels before submitting a new report.
Before you finish
- Known bugs tracker: Game build and platform match the guide scope
- The same symptom or objective can be reproduced
- Names, buttons, and menu labels match the current build
- A rollback, backup, or reassembly checkpoint is available
Evidence and confidence
Core answer supported; version-sensitive details remain reviewable.
Source method
We separate official information, repeatable video observations, and community reports. A community report can identify a useful lead, but it does not become a verified instruction until it is independently reproduced.
Update policy
This page is reviewed when a patch, platform release, or repeatable player report changes the answer.
Common questions
Is this answer confirmed?
Core answer supported; version-sensitive details remain reviewable.
Why is this page indexed before every detail is verified?
Because the page provides a useful status, a safe validation path, and a transparent evidence boundary. It is not a placeholder or a fabricated solution.
What should I do if my result is different?
Stop at the last reversible step, note your platform and game version, and use the correction link so the discrepancy can be reviewed.