Last checked August 2, 2026
Check official Steam News, launch patch notes, known issues, server-region notes, and community reports before treating a crash, queue, mail, or patch problem as confirmed.
Latest signals
Use this snapshot as a route into the source, not as a live server monitor. If a new Steam News post appears after this check, trust the newer official post first.
Aug 1 official news
The Second Wave of Launch Rewards post says the team will roll out one client update next week to fix reported issues and improve build stability, with detailed patch notes to be shared later.
Official: Steam News
Jul 30 official update
The July 30 update lists class balance changes and fixes for Sorcerer prompts, Soul Tree extraction consumption, console reconnects, controller crashes, item splitting, and other launch problems.
Official: Steam News
Jul 29 official post
The Known Issues post listed problems found after store review, including Sorcerer tutorial prompts, Flameblade range mismatch, extra Soul of Return consumption, console reconnect issues, controller crashes, and PS5 display anomalies.
Official: Steam News
Jul 24 official FAQ
The launch FAQ says server locations were being deployed across China, the United States, Germany, Singapore, and Brazil. It also points players to official community channels for additional questions.
Official: Steam News
Status check flow
Most launch-week confusion comes from mixing official fixes, store approval timing, community crash reports, and platform-specific issues. Work through the strongest sources first.
Check the newest official post first for patch notes, known issues, launch mail, maintenance language, and client update timing.
If your client behavior changed after a download, compare Steam's update history and the latest official patch post before using an old thread.
Use the public Discord Discovery page or official-site paths before trusting invite links, support tickets, or troubleshooting bots.
Steam Discussions and fan trackers can show patterns, but treat them as reported signals unless a developer reply or Steam News post confirms the issue.
Known issues
The table keeps official fixes separate from player reports. Do not assume every older thread still applies after a newer client update.
Player troubleshooting
These are safe next checks, not guaranteed fixes. Use official support or Discord tickets when a crash, disconnect, or missing reward keeps repeating.
Check Steam News first, update GPU drivers, verify files, and compare developer replies in current Steam threads before changing system settings.
Update the client and compare the Jul 30 console reconnect fix with newer posts. If it repeats, report platform, region, and timing.
Use the codes and rewards page to separate launch mail, Twitch Drops, and public redeem-code rumors before assuming a status outage.
Use newer Steam News posts over older community lists. Fan trackers are useful for leads, but official posts should settle the wording.
Source notes
Status, server, and bug information moves quickly. This page separates official update posts, third-party trackers, community reports, and editorial check order.
FAQ
This fan page does not monitor live server uptime. Check the newest Steam News post, Steam update history, official Discord paths, and current Steam Discussions before deciding whether the issue is global.
Start with Steam News because it is the strongest public source for official patch notes, known issues, launch rewards, and update timing.
No. Steam Discussions are community reports unless a developer reply or Steam News post confirms the issue. They are useful for spotting patterns, not for final status wording.
The August 1 Steam News post checked here says a client update is planned next week to fix reported issues and improve build stability, with detailed patch notes to follow.
Compare the Jul 29 Known Issues post with the Jul 30 update and any newer Steam News post. Update the client before using older community workarounds.
No. It helps you find the strongest source and next check. For repeated crashes, disconnects, or account-specific issues, use official support paths or developer-requested Discord tickets.
