Welcome to Diablo III Bug Report Forums! To get started on this forum, please read through this guide as it explains some Do’s and Don’t’s for bug testing and reporting.
Feedback is NOT a bug. Anything related to feedback, class balance, boss suggestions, etc. belongs in another forum.
We read every single thread that is posted on this forum. However, we will not always respond to every thread. If you do not get a blue response, please DO NOT bump posts. We will ignore and possibly delete any post that simply says “Bump” or demands a response from a Blizzard poster.
When reporting a bug, please make a thread for each bug you find. Threads that contain multiple bugs are difficult to manage, especially if we are unable to reproduce any of them on our end.
Please use the Search feature to search the forum and see what bugs are posted. If you have a duplicate thread, we will lock it and point you to the current thread where the bug is being discussed.
Please specify which character on your account experienced the issue you are reporting.
Finally, please only discuss bugs within the threads. Avoid off topic discussions or other things not related to the bug in the thread. Don’t use bug report threads as a platform for discussing game balance, design, or to provide feedback or other subjective opinions about the game.
Ok, you found a bug, congratulations! But now what? This guide will explain how to accurately write a bug report.
When posting a bug, please begin with a one or two sentence Summary that attempts to accurately describe the bug. We should be able to understand at least 75% of the issue you are reporting simply by looking at your Summary. we understand that the size of the Summary has to be short, but please do your best.
Good summary: The tooltip for the Barbarian’s Bash skill contains a typo.
Bad summary: Bug with smash
After your Summary, include a brief description of the bug you experienced. Include as much RELEVANT information as you can. Where you in multiplayer? Could you reproduce the issue? Specifics are preferred as we need to know as much as possible about the issue.
If you have steps and can reproduce them consistently, write them out. This will help Quality Assurance get a must faster turn around time reproducing the issue and reporting it to the Diablo III developers.
Finally, it always helps to attach a link to Imgur (or another picture hosting site) that displays a screenshot of the bug. If you need to include a video, link to a video as well.
Types of Bugs
Below are some different types of bugs you may encounter in Diablo III. We also have included the specific information we would like for each bug reported of this type.
Combat bugs - These are pretty simple. If there is a broken skill in the game, include the name of the skill and the class that uses the skill.
- Example: The Barbarian’s skill Bash does not knock enemies away.
Quest bugs - These can be complicated. For quest issues, we request that you include two things:
Please include the name of the quest and quest step that you were on when you encountered the bug. The name of the quest is the name that displays at the top of your quest log, while the quest step is the specific instructions for you to complete in the quest.
Please specify whether this occurred in multiplayer or solo play.
- Example: During the quest “The Fire From The Sky : Slay a Wretched Mother”, you cannot kill the Wretched Mother in multiplayer.
Environment bugs - Finally, Environment bugs round out the specific types of bugs we need more information about. For Environment bugs, please describe the issue you found and tell us what level area it is located in. The level area is simply the name of the sub-zone you are in and can be found above the minimap. Every location in the game has a level area, and it helps to know this before we start looking.
Screenshots are perfect for Environment bugs as well. They will accurately display the issue you are seeing. Screenshots can be taken by pressing Print Screen and can be found in the Screenshots folder in the Documents/Diablo III folder. Uploading a screenshot to an online photo site like Imgur and linking it back to your thread would help a lot as well.
- Example - In New Tristram, one of the houses is bright pink.
Crashes are getting their own section because of their complexity. One major way you can help Blizzard out is by filling out the crash box that appears if you crash. Simply write a description of what happened when you crashed. Were you in multiplayer? Again, specifics are key and can really help us narrow down the cause of any bugs you encounter and get them fixed as quickly as possible.
Following these guidelines will allow all of us to work together as efficiently as possible. Thanks for reading and enjoy your look at what’s coming for the game in the future!