Bellring Games published an official list of 12 known issues within 30 minutes of servers opening on July 29 — all client or controller bugs, not server outages, with a fix already submitted for expedited store review. The most important one: repeatedly entering and exiting the area around the Soul Tree while summoning an Extraction Point can incorrectly consume an extra Soul of Return.
The Soul Tree bug, where repeatedly entering and exiting the area while summoning an Extraction Point could incorrectly consume an extra Soul of Return, is fixed. Bellring shipped the fix at 16:00 UTC on July 30 after clearing storefront review — update your client if you have not already.
Player reports and press coverage describe stuttering, FPS drops, and desync at launch, including on high-end PCs. The likely cause is a mix of Unreal Engine 5 shader compilation stutter and server congestion, which can feel identical in a busy fight.
Player reports and press coverage described stuttering, FPS drops, and desync at launch, including on high-end PCs. The July 30 patch addressed several causes directly: random crashes tied to vegetation animation and AMD hair rendering, and optimized shader precompilation to reduce combat micro-stutter.
The July 30 patch resolved all 12 launch-day known issues Bellring listed, including the Season Leaderboard controller crash, a broken item-split bug, console reconnect problems, and an impassable area in the "General Harald" challenge, alongside the Soul Tree bug and the Withered Knight buffs. A second client update is due the week of August 3–9, focused on further stability and opening the Einherjar Mode Mist Lord challenge.
Players in Australia and New Zealand have reported high ping and asked for dedicated OCE servers; this has not been announced as a planned fix as of this writing.
| Situation | Recommended answer | Why it matters |
|---|---|---|
| First time learning | Use cheap gear and test Known issues tracker in low-risk routes | Information is more valuable than one lucky run |
| You already have useful loot | Move toward extraction instead of adding another objective | Banked value is the real win condition |
| A fight gets loud or long | Reset, listen, and assume another player heard it | Third parties punish slow decisions |
| A detail is not yet verified | Mark it as pending and update after launch verification | Trust matters more than fake precision |
Known issues tracker is a specific search intent, not a generic article. Players reaching this page want a focused answer for players troubleshooting launch issues, so the content is organized around decisions, risk, and update targets.
The practical answer is to separate local fixes from server or patch problems. This keeps the page useful before final numbers are public and gives a clear path for adding verified screenshots, values, and examples later.
Do not invent exact drop rates, cooldowns, map pins, or tier rankings for this topic until they are confirmed. The main risk to avoid is telling players to change settings when the issue is server-side.
Is this Known issues tracker page based on confirmed data?
It uses confirmed public game concepts and cautious extraction-game guidance. Exact values, markers, and rankings should be updated after launch verification.
Who should use this Known issues tracker guide?
It is designed for players troubleshooting launch issues.
Why not list exact numbers now?
Publishing invented numbers creates low-quality pages. This URL is structured so exact data can be added quickly once it is verified.
Steam discloses a kernel-level anti-cheat system for Mistfall Hunter.
Read update →The Xbox store lists cross-platform multiplayer and cooperative capabilities.
Read update →Xbox lists online cooperative play for two to three players.
Read update →The Xbox page lists a 2–15 player online multiplayer capability.
Read update →Steam’s official description states that purchases do not provide combat power advantages.
Read update →50 short answers pulled from official sources and this site’s own guides.
No, this is an unofficial fan-run guide and database, not affiliated with Bellring Games or Skystone Games.
An independent, unofficial guide project focused on citing official sources rather than speculation.
The official Mistfall Hunter site, Steam and Xbox storefront listings, and official announcements — see the sources page for the full list.
By checking claims against official storefront and announcement text, and labeling anything not yet confirmed as pending.
Because the underlying detail has not been settled by an official source or live testing yet; the site prefers labeling a gap over guessing.
They are updated with live data, screenshots, and verified values once the game is out and testable.
No, the editorial policy prioritizes official game and storefront information over datamined or leaked material.
No, unverified leaks are avoided in favor of official announcements and live-tested facts.
Regularly, especially around official announcements and, once live, ongoing patches.
The site tracks corrections through its editorial process; check the sources page for how information is sourced and revised.
Build guidance here is currently editorially maintained rather than open-submission; the build planner lets you create and share your own.
No, it is unofficial and unaffiliated.
No, it is unofficial and unaffiliated.
Ad infrastructure may be present on the site as part of standard operation; it does not influence editorial content or rankings.
Check the site footer and sources page for the current contact and policy information.
So readers can tell at a glance what is settled fact versus what still needs verification, rather than presenting both with false equal confidence.
The developer’s own site, official storefront listings (Steam, Xbox, PlayStation), and direct announcement text.
Yes, storefront listings are treated as primary sources for platform, pricing, and release information.
Chinese-language pages on this site are edited separately, not machine-translated wholesale, though coverage depth can lag the English version on newer pages.
Not yet — Chinese localization is rolling out progressively rather than covering the full English corpus at once.
This site deliberately keeps thin or unverified pages out of search results until they have real content behind them, to avoid publishing low-quality pages.
It marks content written before the game is out, where some facts are necessarily provisional pending live verification.
Yes, that is the plan for maps, builds, bosses, and other pages whose exact details need live-game confirmation.
The goal is equal coverage; some platform-specific detail (like console settings) may lag until hardware is testable.
The site is built to work on mobile browsers; there is no separate native app.
Yes, the site is designed to be readable and usable on mobile devices.
No dedicated app; the website itself is the product.
Check the site footer for current community links, if any are listed.
Use the Classes hub or search for the class by name (Mercenary, Sorcerer, Blackarrow, Shadowstrix, Seer, Withered Knight).
It is linked from the main navigation as Map.
Linked from the Builds section of the site.
The server status tracker page, updated with known maintenance and connection issues.
The known issues tracker page, covering crashes, stutter, and reported bugs.
The patch notes tracker page, updated after each official update.
Yes, beta and demo content is labeled separately from full-launch content so the two are not confused.
Not necessarily — beta builds are explicitly earlier and less final than the launch version; treat beta-only pages as historical context.
Confirmed facts are labeled and cited; anything still uncertain is marked as pending rather than stated as settled.
It gets corrected and the page is updated once the discrepancy is caught, consistent with the site’s verification-first policy.
Corrections are made directly on the affected pages as part of normal upkeep.
The Updates page tracks the editorial log and launch verification plan.
No — always treat the live storefront (Steam, Xbox, PlayStation) as the final word on current price.
Yes, regional pricing and promotions can change independently of what is written here.
Because invented numbers create low-quality, misleading pages; better to wait for verified data.
Speculation is avoided in favor of clearly labeled official facts and, where relevant, general strategy reasoning that does not depend on details still pending verification.
Yes, with rankings framed around learning curve, safety, and role fit rather than final balance numbers, since those are not live yet.
Because class balance and exact values are expected to shift after launch based on live data and patches.
Operational details of who maintains the site are not the focus of the content itself; see the sources page for editorial policy.
The site’s process includes AI-assisted drafting cross-checked against official sources, consistent with its verification-first editorial policy.
By leading with July 29 (matching Steam and press coverage) and explaining the UTC conversion that produces July 30 in some sources, rather than picking one and ignoring the other.
On the Sources page, which lists every official reference this site treats as authoritative.
