The short answer
[Release edition · evidence-led] Use the Recipe Book, Fishing Notebook, item inventory and current journal as your collection ledger. Keep a pre-departure save before story transitions, and treat classic SC totals, chest routes and book locations as comparison material until the remake confirms them.
Before you start
- Access to the current collection menus
- A manual-save rotation
- A note or screenshot method for unresolved entries
Let the game’s notebooks lead
[Confirmed systems] The official activities page describes the Recipe Book, occasional Attack Food from failed cooking, rod/bait fishing combinations and Fishing Notebook rewards. Exact full-game totals are not published there.
| Category | Current evidence to record |
|---|---|
| Books | Exact title, where the current build displayed it and whether the entry persisted. |
| Recipes | Recipe name, ingredients visible in the Recipe Book and result/effect. |
| Fish | Fishing spot, rod, bait, catch and notebook reward state. |
| Chests and items | Map label or screenshot, item name and whether the route is one-way. |
| Achievements | Platform, displayed condition and unlock state; do not infer from a checklist alone. |
Run one region at a time
[Pending verification] Current community completion discussions are useful research leads, but disputed counts and old-SC replies stay out of Kingy’s progress totals.
- Before leaving a town, check shops, Guild requests and changed NPC dialogue.
- Update the Recipe and Fishing Notebooks immediately after an activity succeeds.
- Mark any missing book, chest or recipe with the current objective and map name.
- Save before a chapter transition and keep the prior file until the next region is verified.
- Only promote a total to the wiki after a release-build source records the denominator.
Use a two-file collection strategy
A story file protects forward progress; a collection file protects experimentation. For demo continuations, retain the original trial save until the full-game import has been checked.
If a guide disagrees with the current journal, keep the current build evidence and record the disagreement. The goal is a reproducible route, not a confident-looking list.
- Label a story save and a collection save.
- Create a pre-departure save before each major transition.
- Record platform and version beside any new total.
- Do not overwrite a return point to test an unverified route.
Your checklist
0 of 6 complete · Loading saved progress…
Research checked 2026-09-17. This is a source-based guide; Kingy has not independently play-tested these steps. Evidence and coverage.