Fields of Mistria mines

119 records shown · Name A–Z

No records match this lookup.

The mines lookup joins captured mine-system records with location and material records so a player can begin with a place, resource, task, or source phrase. Search the name, then filter category, type, source, location, or captured value to separate different evidence families. A location row identifies a named place but does not supply coordinates or a floor map. A material row can show mine or gathering context without proving a drop floor, frequency, or route. System records explain named player tasks and relationships, yet they do not form a complete progression tree. The combined result count therefore describes records related to the question, not a generated mine run. Use category and type before comparing values, because rows from different families do not share the same meaning. When the source field is incomplete, open the linked page and keep the missing coordinate, floor, enemy, or probability outside the claim. The lookup is an orientation surface that finds the right captured record before a player commits to a detailed route.

Rows on this route retain names, record type, category, source text, captured locations, sell values, tags, relations, page identities, version ids, and revision markers where the underlying record exposes them. The interface combines these fields for discovery but does not normalize them into an invented spatial model. Search can locate a mine phrase across system, place, and material text; the field filter determines whether that phrase is actually stored as location, source, category, or another value. This distinction keeps a broad relationship from being mistaken for an exact drop rule. The relation panel shows named connections to skills, items, the museum, or town systems only when the captured record contains them. It does not add prerequisites, costs, unlock floors, or optimal paths. The items route provides the material-focused view, while the museum route provides collection context. Neither route fills missing mine geometry. Use the linked source whenever the task depends on a floor layout, coordinate, enemy table, or progression requirement absent from the row.

Mine-related records are bound to the v1.0.2 capture context displayed in the masthead. The community data preserves structured system, place, and material fields, while the official update timeline preserves dated release statements. A later engine or content patch can revise mine behavior without automatically rewriting each captured row. New evidence should arrive through a newer source revision and retain the older stable id for comparison where appropriate. For a current question, identify the record family, read its source and relation fields, and verify any missing floor, coordinate, or drop detail at the linked page. Search and sorting run locally and never calculate a route from the player’s save state. The page does not track elevator progress, inventory, combat readiness, or daily time. That boundary allows the lookup to connect real public records while keeping unsupported spatial and probability claims out of the almanac. The update route remains the secondary check when a dated patch could have changed the system behind the row. Record family is essential when saving a result: a place, material, and system note can share mine wording while answering three different questions.