Cast n Chill Fish Locations in Published Evidence

The cast n chill fish locations dataset currently publishes three records supported by official press-kit screenshots: Threadfin Shad, Bluegill Sunfish, and Walleye at Goldenfork River / The Fork. It is a deliberately partial evidence set, and missing fish, places, rods, lures, times, or sizes remain Not verified.

Coverage boundary

Know what this location page includes and excludes

The official press kit states a broader game scope of 16 fishing spots and 50 fish, but the screenshots reviewed for this release support only the three public rows shown here. The difference is intentional. A product-level count does not reveal the exact fish-to-location mapping, and it cannot fill rod, lure, time, depth, or catch-type cells that are absent from the source.

Threadfin Shad and Walleye are visible in the official map screenshot associated with The Fork. The official logbook screenshot shows one Bluegill Sunfish catch at that spot with medium size, Lil’ Guppy rod, and Soft Plastic Bobber. The equipment fields are labeled as a pictured catch, not as the only setup that works.

A species missing from the explorer is unpublished in this dataset, not disproved. A location missing from Browse by Location is unrepresented by the current rows, not removed from the game. This wording prevents a small verified sample from being mistaken for a current logbook export.

Using the explorer

Search species, combine filters, and read the empty state

Search checks the published text attached to each record, including the fish, location, known optional fields, source type, verification date, and notes. Available filter controls are derived from validated data, so a facet appears only when it has enough represented values to be useful. Invalid query values are ignored rather than causing a broken page or manufacturing a match.

On desktop, the results appear in a semantic table; on mobile, the same records are presented as readable cards. Both views come from one filtered result set. Browse by Location is also generated from those same records, so it cannot quietly claim a fish that is absent from the table and cards.

An empty result means no published row matches the current combination. Reset returns to the full three-record subset. It does not imply that the target combination is impossible in the game, because the source set is intentionally narrower than the official product scope.

Column definitions

Interpret a value without stretching the evidence

Fish and Location are required for every published row. Size, Rod, Lure, Time, Trophy or Legendary status, depth or retrieve behavior, and game version are optional because the reviewed material may not expose them. When an optional field is absent, the interface displays Not verified rather than “any,” “none,” or another guessed value.

Source type distinguishes official material from community records. Source URL lets the reader inspect the origin, while the verification date records when the page’s evidence decision was made. Notes preserve limitations such as “pictured catch,” which is essential when one screenshot shows equipment without declaring a universal requirement.

The controlled location format uses “Region / Spot.” That allows the explorer to group rows consistently and gives future contributors a clear validation target. A new row with an ambiguous or malformed location must be corrected before it can enter search or the location browser.

Candidate expansion

Use community guides as leads, not silent replacements

The collected Reddit community guide organizes species, spots, sizes, rods, and lures, making it a useful source of candidate rows and reader vocabulary. Steam discussions add troubleshooting clues for Northern Pike and Lake Trout, including equipment, time, and depth questions. These are dated player materials, not an official current-build data export.

Before a community candidate becomes a public row, verify the fish name and location in the current game and capture each optional value that will be published. Record the build or version when visible, the date, and the exact source. If only part of a row is supported, publish that part and leave the rest Not verified.

Updates such as new maps or fish can make older community tables incomplete without making every older observation false. Versioning lets the wiki retain a historical record while preventing a past setup from being presented as current certainty.

Location FAQ

Answer location questions with the correct confidence

Adding a supported row

Require one traceable observation before expanding coverage

A candidate row begins with the exact fish name and the controlled Region / Spot location visible in a source. Capture the surrounding screen so the selected water, logbook entry, and any displayed size or catch classification remain connected. Record the platform, date, and game version when it is shown.

Add optional fields only when they are readable. If a rod and lure appear beside the catch, label them as pictured unless the source explicitly says they are required. If time, depth, retrieve, or trophy status is absent, leave the field empty so the interface displays Not verified.

Community records need a direct URL, publication date when available, and a community-reported label. Check the current build before publishing a row from an older guide, especially when it predates later maps or updates. An official total can establish game scope, but it cannot substitute for the row-level observation.

Finally, run schema, duplicate-ID, internal-link, and explorer tests. The same validated record must drive search, query state, desktop table, mobile card, and location grouping. This prevents one presentation from drifting away from the others.

The location browser must remain a view of the same validated rows rather than a separately maintained list. That single-source rule keeps counts, names, anchors, and empty states consistent when coverage grows.