Mistfall Hunter Wiki for Builds, Maps, and Your Next Run

Start with the decision the build must support. You can copy one of 372 imported snapshot presets or create a local build from the recorded classes, weapons, armor, skills, talents, gems, and quick-use items. A preset is a reproducible starting record, not an official recommendation or a current meta ranking. The editor checks recorded class, weapon, armor-slot, skill, talent, and quick-use constraints without deleting conflicting selections behind your back. If a class or weapon change makes an older choice invalid, the conflict stays visible until you remove or replace it. Total Combat Value appears only when every required selected-equipment value is known. The minimum known level comes from selected talent requirements; skill level stays Unknown when the imported source has no reliable field.

Use Compare when two or three same-slot candidates need a field-by-field review. Missing values remain Unknown rather than becoming zero, and Replace changes only the intended slot. Ownership is a separate local fact, so selecting a candidate never marks it owned automatically. When the build is ready enough to test, use Find acquisition beside each missing canonical item. Repeating Add Missing from the same source is idempotent and cannot silently double the required quantity. The result is a build connected to concrete acquisition targets, not a disconnected list of names. Open the custom build planner to begin, or read the classes, weapons, skills, and talents guide before selecting a preset.

Acquisition begins with the exact item or action, not a guessed source. Search the canonical record, review every imported loot, crafting, vendor, merchant, reward, and auction-seed path, then choose one whose recorded conditions match the run you can actually make. Probability, pity, first-time status, timing, map, mode, and party conditions stay attached to the source. A possible point is not a guaranteed live spawn, a seed price is not a live market quote, and the resolver does not call one route fastest, safest, or best. When a path is absent or incompatible, leave the target unresolved or choose another recorded source instead of manufacturing an answer.

Next Run Plan consolidates the same canonical entity across Build, Acquire, Building, Crafting, Season, Quest, Mission, Cipher, and map workflows. Assign a legal map, intensity, and party context, bind relevant points to the specific target, and order the route yourself. Run Brief groups relevant, other, and unassigned goals while preserving the relationship between each route point and its target. Party format is context only; it never rewrites a recorded probability. Open the acquisition resolver, continue in the Next Run Plan, and carry the final context into the compact Run Brief. The current client remains authoritative if it differs from the dated snapshot.

Broad gameplay and platform statements come from the official Mistfall Hunter site or the current Steam listing. Detailed entity, build, acquisition, progress, and map relationships come from an authorized capture of publicly accessible MistfallDB pages dated 12 Aug 2026. Derived results combine those records with explicit inputs: examples include build conflicts, material deficits, comparison deltas, route grouping, expected-run estimates, and crafting calculations. Local values such as owned quantities, completed goals, selected routes, and manual prices are facts entered in this browser. These evidence layers are displayed separately because one cannot substitute for another.

Freshness and publication labels explain whether a field is from a reviewed official page, a dated third-party snapshot, a derived calculation, or local state. Unknown, unavailable, stale, and conflicting values stay visible. The tools do not fill gaps from similar names, icons, text mentions, or community assumptions. Before a purchase, high-value run, or current-rule decision, open the linked source and compare it with the released client. Read the Mistfall Hunter data sources and evidence labels or the full data policy for the boundary behind each result.

This version has no login, community profile, cloud inventory, or server-side user database. Builds, Plan items, routes, map targets, progression, quantities, display preferences, and imported state are stored in browser local storage. Export creates a versioned JSON copy. Import first validates and previews Merge or Replace so the selected action matches the displayed changes; invalid records do not modify current state. A shared URL contains only the records you explicitly encode, and the recipient decides whether to import them. Clearing browser storage removes local state on that browser, so export before clearing or moving devices.

Analytics remains disabled unless a production measurement ID is configured. When enabled, the integration sends page paths rather than search queries, build contents, plan contents, routes, imports, or form values. Storage can fail because of browser settings, private mode, quotas, extensions, or device policy; the product shows that state instead of pretending a save succeeded. Review the privacy and local data controls before importing, exporting, sharing, or clearing data. Use Data Portability settings to inspect the available controls.

If you are new, read the first-extraction beginner guide and create one objective. If you already know the desired class, filter snapshot presets or build from scratch. If the build is known but gear is missing, start in Acquire. If progression blocks the run, choose the relevant quest, mission, season, building, achievement, or cipher workspace and add only the open canonical target. If a target already has a source, map, mode, and party context, go directly to Map and Run Brief. Each path returns to the same local Plan instead of creating an isolated calculator result.

Use the directories when you need evidence rather than an action: browse equipment, skills, talents, enemies, vendors, NPCs, kits, treasure pillars, recipes, quests, missions, seasons, buildings, achievements, or source records. Detail pages keep source dates and unavailable relations visible. The evidence-labeled guide library explains workflows, while the complete data directory exposes the imported records. Start with one checkable decision, verify it in the current client where required, and update local state only from what you actually observe.