Update to 1.0.3 before restarting a finished save. That patch fixes AutoRestore's missing Sorting Points, expands Minor Edit's counting, and allows an affected hidden final-item achievement to trigger when the save is opened again. Founders and Recognized on Sight need their own condition checks.
A player can finish the sorting and still be missing an achievement for several different reasons. Some were launch bugs, some depend on a particular action, and one easy-to-miss achievement happens after the visible story work. Treating every missing achievement as a corrupt save makes the troubleshooting harder.
Identify the achievement before changing the save
| Missing achievement | First check | What changed or what to do |
|---|---|---|
| Hackerman | Game version and remaining script upgrades | AutoRestore now earns the Sorting Points that automated runs previously missed |
| Minor Edit | Version, timed condition and how items leave the log | 1.0.3 includes direct folder drops and AutoRestore in the count |
| I am become Janitor | Update and reopen the affected save | The developer names the final-item trigger in the discussion; the patch describes reopening an already affected save |
| Recognized on Sight | Current destination and hover condition | 1.0.2 includes correct Sub-Folders and Item Folders |
| Founders | Post-hidden-mode Main Page interaction | Players confirm an extra founders form after the story edits |
Record the name before trying a fix. “I finished the game” tells another player your broad progress, but it does not reveal whether the remaining task is buying upgrades, meeting a timed condition, dragging a sequence or finding a story form.
Hackerman: distinguish a fixed cause from an old shortfall
The original report described a completed log with four Multiselect levels still unaffordable. The player suspected that using power-ups reduced the available points. The developer later confirmed the actual issue: AutoRestore had failed to award Sorting Points.
In 1.0.3, every item AutoRestore files now earns those points. That fixes the cause for subsequent automated sorting. It does not establish a universal refund of all missed points in old completed runs. If you already have an affected save, update, reopen it, inspect the remaining upgrade cost and your available currency, and keep the save intact while reporting the difference.
Do not confuse currency requirements. Some upgrades use Completion Points, earned by filling rows. Others use Sorting Points. The AutoRestore and upgrade guide explains those separate checks. Spending time on the wrong task will not resolve a shortage in the other currency.
Minor Edit: leaving the log now counts through more routes
Minor Edit's listed target is to route one tenth of the deletion log out within five minutes. Patch 1.0.3 broadens which departures count: items dropped directly into a Sub-Folder or Item Folder and items handled by AutoRestore now count too.
The fix is about the counting routes. It does not remove the time condition or grant the achievement for any eventual clear. If you are diagnosing an attempt, keep those two questions separate: did enough items leave the log within the condition, and was the attempt running a version that counts the route you used?
The discussion contains questions about challenge modes and whether the condition must be the first ten percent. Those questions alone are not confirmed answers. We do not prescribe a particular challenge mode as a guaranteed workaround. Start with the shipped rule and report a repeat failure with the run type and version included.
I am become Janitor: reopen before replaying
The public patch note refers to a hidden achievement without naming it. The developer's reply in the achievement thread supplies the name: I am become Janitor should trigger regardless of how the last item on the last page is sorted, rather than only through the original manual route.
The patch also says that, if the relevant item is already filed in the save, opening that save again will unlock the achievement. That is a much narrower and more useful recovery step than “start the game over.” Update the game, open the original affected save, then check the achievement state.
One player reported a workaround using a single-folder speedrun; another tried similar runs without success. Those inconsistent results do not make a dependable fix. We recommend the developer's patch behaviour instead. If reopening still fails, preserve the affected profile and take the case back to the discussion with the exact version and final-item state.
The other two cases have separate routes
Recognized on Sight received its own fix in 1.0.2. Old advice that only a Sub-Folder counts is outdated: the correct Item Folder now counts as well. The streak guide explains how to plan a controlled attempt and why a proposed automation change should not be treated as an implemented one.
Founders is not covered by the AutoRestore fix. The players in the same thread confirmed that they had missed a form at the end of the hidden-mode story work. The hidden-achievement guide keeps that process behind a spoiler warning, together with the separate Tanager page clue.
Report the smallest reproducible failure
If the current game still fails to unlock an achievement, provide its name, your game version, the profile or challenge type, the action used and what happened afterward. A screenshot of the relevant upgrade or completion state helps the developer distinguish a resource shortage from a trigger problem.
Keep personal information and unrelated files out of a public post. A description of the state is often enough for an initial report. There is no need to post a complete save file, delete your profile or apply a speculative save edit before the developer asks for more information.
