Fields of Mistria artifacts
Use the artifact ledger for archaeology questions that need an item name, site, value, rarity, or museum set. It gives the museum question a stable starting row before a player follows the source into a longer archaeology note. Artifacts remains bound to the v1.0.2 capture.
Steam 1.0 release ·Artifacts source boundary
Start this artifacts check with the displayed count, then keep the chosen field and source link together when the answer affects a longer route.
Artifacts lookup
110 records shown · v1.0.2
110 records shown · Name A–Z
No records match this lookup.
The artifact ledger is organized for a player who remembers one clue about a relic but not the entire museum context. Search the name across 110 captured rows, then use location, sell value, rarity, museum status, or museum set to isolate a smaller group. Sorting changes the reading order without turning rarity or value into a drop probability. A relic with a high recorded value can still matter more as a collection item, and a museum set does not reveal a complete excavation route. Location text is preserved exactly when the source exposed it; a missing site remains not captured. Stable ids help distinguish similarly named records, while the outgoing source page carries the context that does not fit the compact row. The safest workflow is to identify the relic, check its set and site fields together, and open the source before planning around an absent location or a rarity label. This makes the ledger useful for museum work without presenting a partial archaeology capture as a complete dig table.
What this lookup covers
The lookup surfaces the fields that support museum work: archaeology source, location, sell value, museum flag, museum set, rarity, tags, page id, and revision id. It does not turn rarity into a drop-rate claim and does not invent a dig-site map. Search runs across the real source text and field values; field and value options are taken from this route’s records, so sparse museum data remains visible as “Not captured”. The stable id and revision marker make it possible to tell two similarly named relic rows apart when later captures add or correct a field. The ledger keeps site text, museum grouping, rarity, and value adjacent because those are different reasons a player may care about a relic. None of those fields alone proves a complete dig rule. The revision id provides the useful audit trail when a later capture changes the public wording. This section keeps the 110 artifacts records inside the v1.0.2 capture separate from later research.
Artifact records can include a name, archaeology source, location, captured sell value, rarity, museum flag, museum set, tags, page identity, revision marker, and source URL. The page exposes those fields as separate observations. It does not calculate excavation odds, rank sites, infer a missing set, or treat a sell value as advice to discard a donation. Search finds terms across the visible record, while field filtering confirms whether a term belongs to the location, rarity, set, or another chosen category. That distinction is important when a source note contains place names that were not normalized into a structured site field. The artifact route connects to the combined museum checklist, where stable ids support private local marks, but the ledger itself remains the deeper source-oriented view. Fish, bugs, and forageables use different field contracts and should not be used to fill artifact gaps. Every not-captured value marks the boundary of the public record and points toward a source check rather than a guess.
Version boundary
Search a named relic, filter to a museum set, and sort by sell value when you need a quick comparison. Open the captured page for details outside the structured record. For collection progress, the Museum route joins artifacts with fish, bugs, and forageables under stable record ids and local checklist state. A missing site is a boundary marker, not a hidden location; use the source link for the full page context before planning a dig around it. A player can search a remembered name, filter a set, and inspect the value order in seconds. Use the result to choose a source to read, then preserve the captured set and id when recording a personal museum goal; the site does not convert the ledger into a drop table. The version marker also gives the next lookup a clean handoff: a source correction can be compared with the old row instead of being mistaken for a timeless fact. Use the artifacts result as a documented next step, then revisit the linked source if a later version changes the field.
These artifact rows belong to the current v1.0.2 community capture, with revision ids retained so later changes can be compared. Official Steam announcements establish release chronology, while the community artifact pages establish the structured relic fields visible here. One source cannot silently stand in for the other. If a new patch adds archaeology content or a community revision corrects a museum assignment, the next dataset should preserve the newer source and leave the earlier row auditable. For an immediate collection task, search the relic, verify the museum set and location, and note whether rarity or value was actually captured. Open the source when a planned dig depends on an exact site or condition. Local filtering never updates museum progress, and sorting never changes the underlying evidence. The combined museum page is the correct place for a private checklist; this route remains the versioned ledger that explains which captured record sits behind that mark. When two relics share similar wording, carry the stable id into a personal note. Names alone are less reliable than the source-bound identity when a later revision adds another item to the same set. Retain the museum set beside that id so the note remains useful after the visible list is resorted.