Evidence-first angling · Checked August 17, 2026
Cast n Chill Fish Guide: How to Judge Catch Data
Use official scope, dated records, and clearly labeled player clues to plan a target without turning one screenshot or discussion post into a permanent catch rule.

The cast n chill fish guide is a method for choosing trustworthy catch information: start with a verified fish and location record, separate pictured equipment from required equipment, date every community clue, and mark any missing size, time, lure, depth, or technique as Not verified.
Read before copying
Know what a fish record can actually prove
A strong record names the fish and the exact region or spot, then adds size, rod, lure, time, depth, retrieve behavior, catch type, game version, source URL, and verification date only when the evidence exposes those fields. The current public dataset follows that rule. Most optional values remain Not verified because the official screenshots reviewed for release do not show them.
A pictured catch proves that a specific combination appeared together in that capture. It does not automatically prove the rod or lure was required, that the fish can be caught only at that time, or that the same condition survives later patches. The Bluegill Sunfish row is intentionally labeled as a pictured medium catch using Lil’ Guppy and Soft Plastic Bobber rather than an exclusive recipe.
Official totals describe scope rather than individual conditions. The press kit states 16 fishing spots, 50 fish, and 16 Legendary Catches, while the Steam page describes lakes, rivers, oceans, rare targets, and gear upgrades. Neither source publishes a current row-by-row export, so a directory must grow from traceable records instead of being filled from expectation.
Practical search method
Work from target intent to the smallest verified claim
First decide whether the question concerns a species, a location, a size, a trophy, or a legendary catch. A species search asks where a named fish has been documented. A location search asks what the source shows at a spot. Size and catch-type questions require stronger evidence because community language such as L, XL, XXL, trophy, and legendary can be misread when the current interface is not visible.
Next, open Fish & Locations and search the validated records. If a record exists, follow its source link and read the notes before treating any optional field as advice. If the target is absent, the honest conclusion is that this wiki has no published verified row for it; it is not evidence that the species or location does not exist.
Then consult dated community material as a test lead. The Reddit guide organizes fish, places, sizes, rods, and lures, and Steam discussions contain troubleshooting for Northern Pike and Lake Trout. Those sources can identify what to test, but every row from before later maps or updates needs a current-build check before publication.
High-risk fields
Treat rod, lure, time, depth, and retrieve separately
Equipment matching matters in the official progression loop, and player material repeatedly treats rod and lure choice as practical. That does not make every community combination authoritative. Record a rod or lure as required only when the game or a reliable current source explicitly establishes the requirement; otherwise label it as pictured, community-reported, recommended by a player, or Not verified.
Time and depth are especially easy to overstate. Community discussions associate Northern Pike with night and Lake Trout with dawn, Picnic Point, and deeper water, but the research explicitly marks these as candidate conditions needing current-build verification. A useful test notes the exact in-game time, location, water position, equipment, automation state, and outcome across repeated attempts.
Retrieve technique belongs in its own field because it is not interchangeable with lure choice. A King Salmon discussion mentions jigging or dangling, and other player material discusses line control and surface behavior. These observations should be presented as dated troubleshooting leads, not as guaranteed inputs that replace what the current game communicates.
Interface evidence
Use the logbook without inventing symbol definitions
The logbook is a practical place to check whether a fish, size, or target has been recorded, and player footage shows people consulting it while planning catches across maps. Community questions also mention indicators, crowns, and legendary markers. The collected research does not include a current screenshot key that maps every symbol to a verified definition.
When a symbol affects a fish record, capture the full surrounding screen rather than cropping only the icon. Note the selected fish, page, location, version, and any text label that changes with the icon. Compare at least two states so the meaning is supported by a visible difference rather than by the icon’s shape alone.
The Symbols Meaning page keeps those questions separate from this guide. Until a symbol is verified, a fish row should use explicit text fields such as source type, catch type, and notes rather than translating an uncertain crown or marker into a factual label.
When a target will not bite
Change one variable and preserve the failed result
Start by checking whether the fish and location claim came from an official screenshot, a current game capture, a dated community guide, or an undated memory. Then verify the selected spot, rod, lure, time, and active or passive state. Changing everything at once may produce a catch, but it will not reveal which condition mattered.
If a community post describes XXL-rated gear or a particular time, reproduce the condition exactly before testing alternatives. Record unsuccessful attempts too, because a failure can show that an old version-specific clue no longer behaves as expected. Avoid writing “impossible” from a small number of attempts; use “Not verified in this test” and include the build and date.
For Passive Mode, the research contains conflicting reports about legendary attraction and manually selected settings. That conflict cannot be solved by merging the claims. A valid comparison requires the same target, place, equipment, time, automation options, game version, and observation window.
Fish guide FAQ
Apply the evidence rule to common questions
Does a community table make a fish row verified?
No. It supplies a candidate record and useful search structure. The row still needs a current source check, a date, and clear labels for any community-only fields.
What should I do when the wiki has no row for my target?
Treat the value as unpublished here, not absent from the game. Use the current logbook and capture a source-backed observation for later review.
Can one successful catch prove the only valid lure?
No. It proves that the displayed setup appeared in that catch. Exclusivity requires a source that explicitly establishes it or controlled current-build testing.
Where should legendary conditions live?
Use the Legendary Fish page, where the official scope and community-reported fish-specific clues are separated and respawn uncertainty is visible.
Why are so many fields marked Not verified?
Because an unknown field is safer and more useful than a guessed value. It tells the reader exactly what the reviewed evidence did not establish.
Evidence used on this page
- A2 · OfficialOfficial press kit
Developer, release timeline, content scope, modes, upgrades, and co-op context.
Checked 2026-08-17 - A4 · OfficialOfficial Steam store
Current store description, PC purchase path, features, requirements, and changing store data.
Checked 2026-08-17 - C1 · CommunitySteam Community hub
Official announcements surfaced through Steam plus player-guide and discussion demand signals.
Checked 2026-08-17 - C2 · CommunityTrophy fish discussion
Dated player troubleshooting for trophy and legendary conditions.
Checked 2026-08-17 - C6 · CommunityXXL Lake Trout discussion
Dated player clues for one legendary target; current-build verification required.
Checked 2026-08-17 - C7 · CommunityLogbook symbols discussion
Player questions about indicators, crowns, and legendary markers, not an official icon key.
Checked 2026-08-17 - C9 · CommunityReddit community guide
Candidate names and player-organized fields that require current-build checks.
Checked 2026-08-17