Check To-Dos, lost device boxes, active jobs, mail, licenses, conversations, competitions, saves, and current reports when the ReStory story stops progressing.
Quick answer: check these in order
Do not skip days at random. Check the To-Do list, every shelf and device box, all active counter and email jobs, unread or partly scrolled mail, required software installs, tool or license requirements, room and character conversations, and the latest competition result. Save to a new slot, return to the menu, reload, and recheck. Only then compare the current build with recent technical reports.
Developer guidance versus confirmed bugs
In the current Steam thread, FUNTUL says the team is aware of some broken-story issues while also warning that missed To-Dos or a lost device box are common. That is not a promise that one checklist fixes every save. Use the checks below to establish which visible trigger is missing, and preserve the original file before testing any workaround.
Orders begin at the counter. Read the request, then check the To-Do list before deciding that progress is blocked.
Open original page →Progression audit
Work from concrete state rather than day number or cash total.
| Checkpoint | What to verify | If it is incomplete |
|---|---|---|
| To-Do | No task remains unchecked or off-screen | Finish the named action |
| Device boxes | No accepted device is on a shelf, floor, counter, or storage area | Return it to the bench and finish the ticket |
| Active jobs | Counter and email orders are delivered, not merely repaired | Complete hand-in or delivery |
| Newest messages were opened and scrolled | Read the full message and follow its action | |
| Software / license | Requested install and required capability are complete | Open the correct PC page or license category |
| Conversation | Every room and available character was checked | Let the current scene finish before advancing |
| Competition | Invitation, app entry, build, and result all resolved | Finish the current competition state |
| Save / build | A protected copy exists and the game is current | Update, reload the copy, then retest |
Find a lost device box
Walk the shop slowly with the To-Do list visible. Inspect every shelf level, the floor beside storage, the counter, delivery area, and the bench. A repaired device still in its box can look like finished clutter while its hand-in remains unresolved. Open each suspicious box and compare the device name with active tickets. Do not sell, shred, or discard anything while reconstructing the queue.
Mail, software, and licenses
Open the computer and review the newest messages from top to bottom, including text below the first visible screen. Check whether a proposal, delivery, software installation, or license purchase is the actual next action. Buying unrelated licenses early is mentioned in player speculation, but the current developer reply does not confirm it as a universal cause. Treat it as report context, not a proven trigger.
Story progress can depend on a completed repair, a To-Do, and the next conversation. Check all three before treating a quiet shop as a softlock.
Open original page →Character and competition gates
Visit every accessible room and interact with available characters after the work queue is clear. If progression stopped around the BreadBox joystick, Robodog license, Bucket message, or Akiba invitation, confirm that the associated repair was returned and that the competition app or result screen fully resolved. Link the exact last completed scene in a bug report rather than saying only that the story stopped on day 19 or 25.
Safe reload and backup plan
Create a new manual slot before testing. Quit cleanly, preserve the save folder, then reload the protected copy. Do not overwrite the only pre-stall checkpoint. If a recent backup exists, compare it only after documenting the current last scene, jobs, licenses, and inventory. The Save Location guide links tinyBuild's supported restore procedure for desktop platforms and Steam Deck.
When to file a bug report
Report after every visible blocker has been checked and the same state survives a reload on the current build. Include platform, game version, in-game day, last completed story scene, last returned device, active and finished jobs, To-Do state, shelves and boxes checked, newest mail, purchased licenses, competition state, and a screenshot or short video. Never upload the save publicly if it contains personal folder names; send it only through a support channel that requests it.
Research links
These are the primary pages used to check the facts and current release context in this guide.
Official information, observable release behavior, and community reports are deliberately separated. A community report is not presented as a universal fix until it can be reproduced or supported by current patch notes.