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. This Chinese URL is intentionally deployment-safe and can be localized in a later copy pass.
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 |
This URL reserves the same long-tail search target for the Chinese site while avoiding unverified claims and encoding risk in the current rapid expansion pass.
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.
