Service flow / no guesswork
ReStory Repair Diagnostics, Explained
Start with official status; retain the exact context before guessing at a workaround.
Input required
- 01
- Record the game version and symptom
- 02
- Check the device dossier
- 03
- Compare the issue tracker status lamp
- 04
- Record reproducible steps when the checks stop matching

Triage by evidence class
Official-current means the publisher named it on 7 August. Historical-playtest and community-report do not become current defects just because their symptoms sound familiar.
Capture useful context
For a report, preserve device, mode, action, display setup and save context. The official list does not publish a universal recovery flow for its seven entries.
Do not turn a thread into support policy
A restart, input layout or placement suggestion from a player is a lead for retest only. Use the official support route for reproducible released-build failures.
Independent fan guide