Fields of Mistria forageables
Foraging is the quietest way to fill a collection gap, so this page makes the 96 captured forageable records easy to scan by season, location, value, stamina, and museum relevance. It keeps collection work calm and searchable without pretending that the captured fields describe a full walking circuit. Foraging remains bound to the v1.0.2 capture.
Steam 1.0 release ·Foraging source boundary
Start this foraging check with the displayed count, then keep the chosen field and source link together when the answer affects a longer route.
Foraging lookup
96 records shown · v1.0.2
96 records shown · Name A–Z
No records match this lookup.
A foraging lookup works best when it begins with the season or item name that the player already knows. Search across the 96 captured records, then narrow by season, location, sell value, stamina, or museum status. The visible count changes with the active controls, giving a clear distinction between the full family and the current shortlist. A sortable value is useful for comparison, but it does not establish a profitable walking route because distance, respawn timing, competition with other tasks, and complete map positions are outside this dataset. Museum fields provide a second reason to carry an item home, and they should be checked before a sale decision when collection progress matters. Empty location and season cells remain not captured instead of being filled with a likely region. If a search result is driven by a source note rather than a structured field, select the exact field to verify the difference. The page is a reading aid for choosing the next item to inspect, not a generated map of every seasonal spawn.
What this lookup covers
Every row retains the observed name, source text, location when present, stamina, health, sell value, season, tags, museum fields where available, and revision id. The field controls are derived from those records and therefore expose the uneven coverage instead of hiding it. Numeric sorting compares the captured sell value; it does not calculate a daily route or respawn cycle. Source links preserve the original community page for a deeper read. Museum flags and sets remain beside the ordinary sell fields so a collection purpose is not lost when the same item also looks profitable. Forageable rows deliberately retain uneven coverage. A known value can be sorted, a known season can be filtered, and an empty location can remain empty; those states are more useful than a smooth-looking list that hides which parts were never recorded in the public capture. This section keeps the 96 foraging records inside the v1.0.2 capture separate from later research.
Forageable rows preserve names, source text, captured locations, stamina and health values when present, sell values, seasons, tags, museum flags or sets, page ids, and revision ids. These fields do not have uniform completeness, and the interface treats that unevenness as useful information. Sorting known values does not push an unknown value into an invented position, while filtering exposes only values actually present in the selected field. A missing location is therefore different from a location that simply does not match the current query. The route stays connected to artifacts, fishing, bugs, and the museum because those families share collection work, but their encounter rules and evidence structures remain separate. The page does not derive a route length, respawn timer, daily yield, or universal selling priority. Open the community source when the item affects a longer trip, a limited seasonal goal, or a high-value hand-in. Keeping source text and structured fields apart prevents a broad note from being mistaken for a precise spawn rule.
Version boundary
Filter by season when planning a collection run, then use the museum field or set to check why an item matters. If a location is not captured, the row says so directly. The page belongs to the current v1.0.2 boundary and stays linked to Artifacts, Fishing, Bugs, and Museum so the four collection families can be checked together. Treat the result as a short list for the next check, then open the source page before relying on a field that affects a longer route or a high-value hand-in. Use the page to choose what to investigate next, not to calculate a route length or respawn timer. When a museum set matters, keep the family and set visible while checking the linked source so a sell decision does not erase the collection reason for carrying an item home. Use the foraging result as a documented next step, then revisit the linked source if a later version changes the field.
The forageable set is bound to the v1.0.2 capture displayed on the page. This lets a player see which revision context supported a season, value, museum relationship, or location at the time of collection. New patches and community edits can change those fields, so stable ids and source links remain part of the lookup rather than being hidden behind a polished list. For a current plan, filter the season, inspect the museum and location cells, and mark any uncaptured detail as a reason to verify the source. The update timeline can confirm when an official release occurred, but it cannot supply row-level forage data that the announcement never contained. Search, sorting, and filters are local operations that leave the sealed records unchanged. A later capture should add or revise a row with a new audit trail. That approach preserves the evidence used for an earlier decision and keeps a routine collection check from turning into an unsupported claim about the present game state. Keep a sale choice separate from a museum choice when reviewing the shortlist. The same record can support both tasks, but the evidence for value does not replace the evidence for collection membership. Save the source link with any seasonal note that will be reused later, since the row’s revision is part of the fact being remembered.