Known issues checked on 18 September
This is a selected reading guide to Blizzard’s 17 September issue list, checked again on 18 September. It is not a complete bug tracker. “Next build” describes an announced fix target; it does not establish that the fix is live. Follow the linked thread for subsequent changes.
| Area | Reported issue | Published status |
|---|---|---|
| Guilds | Charter signatures fail; zero-signature hand-in allowed | Work in progress |
| Paladin | Vengeance periodic-crit triggers; Holy Strike rank progression | Next build |
| Priest | Starshards / Twilight Focus interaction | Next build |
| Hunter / Warlock | Pet statistics display errors | Work in progress |
| Legacy | Opening below level 25 causes tab errors | Listed |
| Interface | Barber error, minimap positioning, missing character details | Listed / work in progress |
| Combat | Glancing calculations and display errors | Work in progress |
| Turn-ins | Waylaid Crates stack limits; Apprentice Curiosities essence mismatch | Next build |
Separate a display problem from a gameplay result
If a displayed statistic looks wrong, preserve a screenshot and the conditions under which it appeared. A confusing panel does not, by itself, establish how damage, healing or resource use behaved. Equally, a tooltip that looks correct is not proof that an interaction worked.
For class planning, keep the build you intended to test alongside your observations. Our nine-class talent guide index is a starting point for those questions. Avoid declaring a talent mandatory or unusable from a single unexplained result.
How we handle community reports
Player reports can reveal useful patterns before an official list changes. They still need a date, a client build and a link to the original account. Several retellings of the same post are not independent confirmation.
For example, players have reported macOS client crashes. This is a community report, not evidence that every Mac is affected or that a particular workaround is verified. Record your own hardware and system version if reporting a similar failure.
A bug-report template for your group
Make one clear report per issue. Use the beta’s reporting channels and describe observed behaviour without guessing its underlying cause.
- Date, client build and character level.
- Class, relevant talents, equipment and location.
- Exact steps leading to the problem.
- Expected result and actual result, in separate sentences.
- Whether it repeated, and under what conditions.
- A screenshot or short recording showing the relevant state; hide private chat and account details.
Keep a small follow-up list
Give each unresolved question a person responsible for checking it after a new build. Preserve the earlier observation instead of overwriting it, then add the new result with its date. This makes it easier to tell a changed condition from a genuine fix.
For joining problems, use the guild creation guide. For a manageable first session, use the week-one testing plan. Neither guide replaces Blizzard’s current issue thread.
We have not added purported bug screenshots without a verifiable source. Screenshots supplied by your own testers are useful evidence when they include the client build and enough context to understand the failure.