01Read Collector as a find-and-kill goal
Steam defines Collector as finding and killing all the creatures. That wording means a successful catch or a Fishipedia entry should not automatically be treated as completed achievement progress. Record the creature after the kill-state result is visible in your current save. This is a safer checkpoint than relying on a remembered catch from an earlier session.
Collector is not Fishipedia and it is not Drip. Fishipedia requires all Drip creatures, while Drip asks for one Drip creature, so their scopes remain separate even when a collection session overlaps. The official list does not publish a complete in-game creature roster. This page therefore uses the documented 49-base-catch table as a practical field list, not as a fake official database.
02Work through regular catch pools before changing islands
For a regular creature, start with its listed rod and lure rather than searching for a permanent shoreline coordinate. The current cross-check organizes 38 regular catches by equipment pool and progression association. Keep the matching lure equipped long enough to test the pool before upgrading away from it. A later lure is not automatically better for an older collection entry.
Use the all-fish table as a checklist, then note the patch, island, rod and lure when a missing target appears. This makes a disagreement actionable instead of vague. A Steam discussion asking about a last missing Blowfish shows the kind of problem this workflow solves. It does not prove a new universal lure rule, so the recorded setup still needs to be checked against the current build.
03Treat the 11 boss rows as encounter chains
The same 49-record cross-check includes 11 bosses or mini-bosses. Their rows use special Boss Lures, quest bait or another creature, so a regular-lure search cannot complete them. Preserve unusual bait such as Tuna, Fish Bucket or a quest item until the active objective is resolved. Selling a chain trigger immediately can turn a missing Collector entry into a repeated route.
Use the Bosses table to confirm location and trigger, then open a focused boss page when the encounter needs a hand-in or current-patch preparation note. Spider Crab, Giant Piranha, Albatross and Bowhead Whale are route gates, while other mini-boss rows do not have a documented unlock in this source set. This distinction prevents the collection plan from inventing progression rewards for every large creature. It also keeps final-chain advice separate from a simple missing-entry lookup.
04Diagnose the last missing creature in a fixed order
First, confirm whether the missing name belongs to a regular pool or a boss row. Next, recheck the rod, lure or special trigger, then the current route association and active quest. Finally, kill the creature and observe the in-game result before marking it complete. This order avoids changing several variables at once when an old community table is incomplete or a patch has changed behavior.
Do not fill a gap with guessed spawn odds, sale values or a claimed exact coordinate. Those numbers are not part of Steam’s Collector condition and are not supported by one stable first-party source. If a target seems absent, keep a short note with the build number and setup. That evidence is useful for a correction request and protects the checklist from a copied claim that cannot be reproduced.
05Finish Collector without merging it into 100% work
Collector is one of the lowest-completion official goals, but its difficulty statistic does not reveal why an individual save is missing progress. Finish the normal 49-base-catch pass first, then return to Fishipedia only for the separate Drip target. This keeps a base creature search from becoming an unbounded rare-variant grind. It also gives a clear evidence boundary when the official game data is not published.
Return to the All Achievements checklist after Steam confirms Collector. The broader checklist can then direct you to Bean, Handyman, money goals or other work without mixing their criteria into a creature route. A dedicated Collector log is valuable because it records what the player tested, not because it pretends to know every hidden state. That is the information gain a completionist needs when the last entry is unclear.
Next verified routes
Continue with the exact next question
Evidence boundary
What this guide can confirm
- Steam officially defines Collector as finding and killing all creatures; it does not publish a complete named roster or a location table.
- Community Patch 1.0.9 through 1.0.11 catch-table cross-checks document 49 base catches: 38 regular catches and 11 bosses or mini-bosses.
- Current Steam discussions show specific last-entry questions, but individual reports do not establish universal lure, spawn-rate or coordinate rules.
Sources and review scope
Check the evidence behind this route
- Steam global achievements for How to Fish
Primary source for the exact Collector requirement and its distinction from Drip and Fishipedia.
- How to Fish: all 49 fish and creatures — GamesHub
Community catch, rod, lure and boss-bait table used for the 49-entry base-catch workflow.
- How to Fish: All 49 Fish, Creatures and Lures — Mobalytics
Independent community cross-check for the 49-entry scope and equipment-first collection method.
- Steam Community — Blowfish Collector question
Current player example of a specific last-creature question; not evidence for a universal lure rule.