Fields of Mistria fish
The fishing surface is a seasonal collection lookup for players deciding where and when to look. The boundary is broad enough for collection questions but still makes the limits of the public capture visible. Fishing remains bound to the v1.0.2 capture.
Steam 1.0 release ·Fishing source boundary
Start this fishing check with the displayed count, then keep the chosen field and source link together when the answer affects a longer route.
Fishing lookup
143 records shown · v1.0.2
143 records shown · Name A–Z
No records match this lookup.
A fishing question is easiest to solve when it is broken into the clues the source actually captured. Search the fish name if the target is known, or choose season, location, size, sell value, rarity, or museum status to narrow the 143-row collection. The field filter and value filter work together, while sorting changes only the order of the matching rows. Location and season usually provide the first useful cut; weather, size, rarity, and value are supporting observations rather than a complete encounter formula. A high captured value does not prove that the fish is efficient to pursue, and a rarity label does not supply a percentage. Museum fields explain collection relevance but do not guarantee that every row has a complete set assignment. When a result lacks location or weather text, keep the not-captured state visible and open the source page for context. The lookup is designed to reduce a large list to a defensible next check, not to manufacture a spawn map from partial public fields.
What this lookup covers
Fish rows preserve the shared route fields: location, season, size, value, rarity, museum set, diving status, weather, type, tags, and source page. Missing location or weather remains “Not captured”, while known values stay sortable and filterable. This route stays within the v1.0.2 community-data boundary. Museum membership appears as a direct field and cross-link, not a generic checklist. Open the linked source whenever a field needs fuller context. Size, rarity, and value remain captured record fields; they are not converted into probabilities, rankings, or guarantees. A fish row can carry several collection clues at once, but the clues are not a complete encounter algorithm. Use the captured season, site, and weather text as a reading aid, and preserve the original wording when an exact source claim matters more than a simplified label. This section keeps the 143 fishing records inside the v1.0.2 capture separate from later research.
The fishing records retain names, source pages, locations, seasons, size labels, captured values, rarity text, museum flags and sets, diving status, weather text, tags, page updates, and revision ids where those fields exist. Their unevenness is part of the evidence. One fish can have a detailed season and site while another exposes only a name and collection relationship. The interface preserves that difference instead of copying information across rows. Search examines the captured values broadly; a field filter asks whether a specific value belongs to the selected field. This prevents a word in a source note from being mistaken for an official location or season assignment. Fishing links to the museum, bugs, artifacts, and foraging routes because they share collection work, but each family keeps its own record contract. Nothing on this page derives bait choice, time-of-day odds, skill requirements, or route duration unless a captured field states it. Use the source link whenever the decision depends on one of those absent details.
Version boundary
Choose a season or location to reduce the list, then sort by sell value or name. Museum work is quickest when the museum column and set are read together; rarity is retained as captured community data rather than presented as an official drop-rate promise. The nearby relationship disclosure connects fish collection with the museum route and keeps the player task in the same almanac navigation. When the row says “Not captured”, use that as a cue to open the source page, not as permission to fill the gap from memory or from an unrelated fishing game. For a short outing, search the family name first and then narrow by the strongest captured location or season clue. If more than one row remains, compare the source links rather than inventing a priority from rarity alone; the route does not model time, bait, or luck. Use the fishing result as a documented next step, then revisit the linked source if a later version changes the field.
All fish rows on this surface are read inside the displayed v1.0.2 community boundary. The official updates page remains the chronology for Steam announcements, while this route remains the structured view of captured fish fields. A later release can change balance, add a fish, revise wording, or expose new conditions. Such a change should arrive through a newer record and revision marker, leaving the older boundary auditable. For a current outing, filter the relevant season and location, inspect the remaining museum or value fields, and note which constraints are still uncaptured. If the source revision is newer than the boundary shown here, use the linked page as the final check and treat this row as an older snapshot. Sorting and filtering are local reading tools; they do not update the source or estimate probability. This separation lets a player plan a short search with real clues while avoiding a false promise that every encounter condition has been modeled by the almanac. Preserve the exact weather and location wording when recording a personal note. Simplifying those fields too early can erase the distinction that made the captured row useful in the first place.
Show captured system relationships
Fish relationships point toward collection and museum context; they are shown as captured links, not as a promise that every listed family shares a spawn location.