Fields of Mistria skills
Skills brings the 12 captured public skill pages and related system records into one reference. It gives progression questions a named public record without pretending that the capture is a complete build guide or perk database. Skills remains bound to the v1.0.2 capture.
Steam 1.0 release ·Skills source boundary
Start this skills check with the displayed count, then keep the chosen field and source link together when the answer affects a longer route.
Skills lookup
18 records shown · v1.0.2
18 records shown · Name A–Z
No records match this lookup.
The skills surface is a reading index for captured skill and system records, not a calculated build planner. Search a skill name, task phrase, category, type, source, or tag to locate the public record that best matches the player’s question. The result count shows the active selection, while sorting changes only its order. A relation can identify that farming, fishing, mines, town work, or another system is connected to the record, but it does not establish a perk effect, unlock level, point cost, prerequisite, or recommended priority. Category and type are useful for separating a named skill from a broader system note. If a row lacks an effect or cost, keep that absence visible and open the source instead of importing a familiar progression rule from another game. The lookup is most reliable when used to answer which documented surface should be read next. It narrows the research path without pretending that the captured pages describe every possible build, respec choice, or character progression outcome.
What this lookup covers
The page preserves names, categories, types, source text, tags, page ids, revision ids, relations, and version ids. The public boundary contains nine named skill pages plus the captured records needed to connect skills with farming, fishing, mining, and town systems. When a field is absent, the row says “Not captured”; no perk effect or unlock level is copied from an unrelated source. The relationship disclosure exposes the real links captured in the systems data. That restraint is part of the data contract: a category or relation can show where a skill belongs without pretending that the capture includes every perk, cost, or unlock order. A skill category, relation, or task phrase can show how the captured pages connect, but it cannot establish a missing effect, cost, unlock level, or optimal order. The route keeps those absences visible on purpose. Its source links make the reference extensible when an approved capture adds a field later. Read each relation as a bounded pointer: it identifies a neighboring system named in the evidence, not a complete dependency graph. That is why the page can be useful for orientation while remaining cautious about player-facing recommendations. This section keeps the 18 skills records inside the v1.0.2 capture separate from later research.
Skill and system records can expose names, categories, types, player-task phrases, source text, tags, relations, page identities, version ids, and revision markers. Their common structure supports search and comparison, but it does not turn sparse relations into a complete dependency graph. The selected field filter confirms where a term is stored, while broad search helps recover a record from a remembered phrase. This prevents a source note that mentions a system from being presented as an exact prerequisite. The relation panel displays a bounded set of connections present in the captured data. It leaves effects, costs, ranks, unlock conditions, and best-order claims outside the page unless those values appear as explicit fields. Farming, fishing, mines, and town routes provide the record families behind several tasks, while the updates page provides official chronology. These surfaces should be read together only at their documented boundaries. A missing field is a prompt to check the linked source, not permission to complete a perk tree from memory.
Version boundary
Search a skill name or source phrase, filter the category field, and open the source record for the full page. Use the Town route for progression context and Mines for resource context. The v1.0.2 label keeps these records separate from the official Early Access and new-engine chronology on Updates. For a player deciding what to investigate next, compare the task wording and relations first; do not turn a missing effect field into an invented recommendation. This keeps the reference useful as the sealed record set grows. Search a phrase from the task, inspect category and type, and use the relation panel to find the next documented system. Then open the source record before making a build choice. The page is strongest when it answers “which public skill surface should I read next?” rather than “what is the best universal order?” A missing field should narrow the claim, not invite a perk effect from memory. This workflow keeps current records, historical updates, and personal plans separate and makes later revisions easier to compare. Treat the captured skill list as a reading queue: it can point from a farming, fishing, mine, or town question toward a public page, but it cannot rank those systems for every character or play style. Record the source wording when it matters, and let a future sealed revision add evidence rather than backfilling an effect from a familiar genre convention. A careful player can therefore use the route to choose what to read next, preserve the current version context, and avoid turning a sparse public page into a promise about every possible progression path. Keep that discipline when comparing records: a relation is evidence of a named connection, while an absent perk detail remains an open question for the source. Use the skills result as a documented next step, then revisit the linked source if a later version changes the field.
The skill index is read under the v1.0.2 capture boundary, with stable ids and revision markers retained for later comparison. A future patch can add effects, change unlock rules, or revise system terminology. Such changes belong in a new source-bound capture and should not silently overwrite the earlier record that supported a prior reading. For a current planning question, search the task or skill, inspect its category and relations, and open the source before spending a scarce resource or committing to an order. Official announcements can establish when a progression change shipped, but they do not supply every row-level effect. The page does not access a save file, count skill points, or calculate a personalized build. Local filters preserve the records and can be reset without changing any evidence. This makes the route a dependable index into public skill information while preserving a clear separation between captured facts, official version history, and the player’s own progression decisions.
Show captured system relationships
Skill relationships identify the captured system neighbors that explain a task without expanding into a guessed perk tree or build planner.
- Fish · museum-system
- Mines · skills-system
- Town Rank · quests-system
- Skills · mines-system
- Quests · town-rank-system
- Museum · fish-system