Fields of Mistria items
Items is the material lookup for names that do not belong exclusively to crops, fish, bugs, forageables, artifacts, or food. Its purpose is to identify a material and its captured context before a player commits to a broader resource plan. Items remains bound to the v1.0.2 capture.
Steam 1.0 release ·Items data boundary
Start this items check with the displayed count, then keep the chosen field and internal record provenance together when the answer affects a longer route.
Items lookup
70 records shown · v1.0.2
Community reference images · not an official source
70 records shown · Name A–Z
No records match this lookup.
The items page is the general material lookup for a name that does not fit cleanly into crops, fish, bugs, forageables, artifacts, food, or another narrower family. Search the 70 captured material records, then filter category, source text, tags, or captured sell value. This is especially useful when a request names an ingredient or resource without explaining where it belongs. The result count reflects the current controls, while the internal record provenance identifies the captured page behind the row. A value can be sorted, but the list does not calculate vendor margin, crafting efficiency, acquisition effort, or drop probability. Categories help separate mine, farm, animal, and general material context, yet they do not create a recipe or guarantee a source. A not-captured field remains visible instead of being replaced with a likely shop, monster, or location. Start with the item name, use the category to identify the evidence family, and recheck the displayed fields and version boundary when a purchase, craft, or route depends on a field outside the compact record.
What this lookup covers
The material rows preserve category, source text, sell value, tags, page id, revision id, and version id where the public page exposed them. Search covers material names and source notes. Sorting by sell value is a direct comparison of captured values; no vendor margin, recipe cost, or drop-rate calculation is added. The field controls are populated from the material boundary and show the “Not captured” state for sparse records. Categories and source phrases remain visible because they provide the context needed to distinguish an ordinary material from a mine, farm, or animal relationship. Material records often sit between several systems, which is why source phrase and category remain first-class fields. A sell value is not a crafting cost, a source note is not a spawn guarantee, and an item name alone does not establish where it belongs in progression. The table keeps those distinctions readable. This section keeps the 70 items records inside the v1.0.2 capture separate from later research.
Material rows can contain the captured name, category, source phrase, sell value, tags, page id, revision id, version id, and source URL. These fields are intentionally smaller than a full inventory database. The page does not infer stack size, vendor stock, crafting recipes, drop tables, storage state, or an acquisition location that the source did not expose. Search checks the retained record text broadly, while the selected field filter confirms whether a value belongs to category, source, tags, or another shown field. This prevents a word in a note from being promoted into a formal acquisition rule. Items connects to mines and animals because both routes can point toward materials, but the relationship stays directional and source-bound. A mine-related tag does not establish a floor or drop rate, and an animal-product category does not establish a care schedule. The general lookup should route the player to the correct source family and keep every unsupported step visibly unresolved.
Version boundary
Use search for a required item, filter by category or source phrase, and sort by value when choosing between records. follow the displayed record context for context that does not fit a structured row. Mines and Animals link into this page because their captured material relationships are real, while unsupported inventory planners remain outside the route plan. If a field is absent, use the row as a lead into its source rather than treating the page as a complete inventory database or a promise about acquisition odds. Search the item name before choosing a category, since the source phrase may be the clue that finds a sparse record. After filtering, compare only the fields that are actually present and follow the source when a mine, animal, recipe, or quest relationship would change the practical next step. Use the items result as a documented next step, then revisit the linked source if a later version changes the field.
The material list uses the v1.0.2 capture boundary displayed across the site. Community revisions support the row-level fields, while official announcements provide dated release context. If a later patch changes a value, source, category, or recipe relationship, the update should be represented by a newer capture with its own revision evidence. Stable ids allow a player to compare the new row with the older one instead of losing the earlier context. For current use, search the required name, inspect its category and source, and treat a missing field as a reason to follow the link. The page does not read inventory data or remember which materials the player owns. Local sorting only changes the display order and cannot establish the best item to sell or keep. This version discipline turns the general list into an auditable reference and prevents a familiar genre assumption from becoming an uncited material rule. If the same name appears in another family, compare category, source, and stable id before treating the rows as interchangeable. A shared label can point to different evidence contexts even when the visible wording looks identical. Preserve the exact category when moving a result into a crafting note. Without it, a later search can return a similarly named record from the wrong source family and make the note look more certain than it is.