Mistfall Hunter Wiki: Classes, Maps & Builds
A Mistfall Hunter wiki should organize Classes, Maps, Builds, Extraction, Bosses and Patch Notes. The available sites are independent community resources, not verified official wikis.
What belongs in this wiki
The collected wiki material supports a hub organized around Classes, Maps, Builds, Extraction, Bosses and Patch Notes. These are information categories, not a claim that every individual mechanic in those categories has been verified. The purpose of this page is to make the boundary visible before a reader relies on a detail.
A useful wiki page should separate broad facts from patch-sensitive claims. Game identity, developer and publisher information can be sourced from the Steam listing, while community tools are useful for discovering topics. Exact skills, loot tables and boss behavior remain To be confirmed unless supported by a current official page or direct test.
Independent status
The source file lists several community wiki domains and a Chinese community site. Their search results describe themselves as wikis or official resources in some cases, but the collection does not capture evidence that the developer formally endorses them. This site should therefore use independent fan-wiki language.
That distinction is not cosmetic. It tells readers that a page can be useful without being an official rules reference, and it prevents a community summary from being presented as a developer promise. Every future mechanic page should carry its source and verification date.
Classes and builds
The collected material repeatedly names six classes: Mercenary, Sorcerer, Blackarrow, Shadowstrix, Seer and Withered Knight. The names are useful for navigation, but the class files caution that skills, weapons, talents and strength require current in-game or official verification. The wiki can publish the roster while leaving those fields explicitly unconfirmed.
Build pages should record the class, mode, patch, core skills, talents, equipment, affixes and alternatives. The sources show that community build tools cover these subjects, not that every recommendation is official or currently usable. Import codes, numerical values and rankings should not be added without evidence.
Maps, extraction and bosses
Hallowgrove and Brandrgarde appear consistently in the collected map sources, so they can be used as top-level map navigation. Point-level information is different: community interactive maps provide leads, but the source file warns that locations and rules must be checked in game. Randomness, version and validation date should be visible beside every point claim.
Boss and extraction pages should follow the same standard. A category can be published because the sources identify it as a wiki topic, while exact boss phases, rewards, extraction rules or item locations remain To be confirmed. This keeps the hub useful without manufacturing detail.
Updates and source policy
Patch Notes is a valid top-level section because the official Steam news feed is part of the collected source set. Roadmap and update claims should link back to dated announcements, not only to a third-party summary. Planned content must never be phrased as live content.
This wiki should prefer official store and news pages for platform, release and announcement facts, then use independent guides for topic discovery and practical context. When sources disagree, the page should show the disagreement and mark the unresolved field.