Introduction:

Please allow me to be the first to welcome you to the SC2 Beta Bug Forums! The purpose of this forum is primarily to collect reports on possible issues our players encounter. We greatly appreciate our customers helping us to find issues with the game. As such, this forum is one of your best methods for making us aware of these issues.

Please be advised that this is not a discussion forum. This forum is a direct line of communication to Blizzard Entertainment's Quality Assurance Department to report issues.

The stickies at the top of the Bug Report Forum contain valuable information to assist you. Please read them before doing anything.

Bug Reporting Guidelines:

• Supply screenshots and system information where applicable.
• Provide as much information as possible, give the unit/map/ability name, and what is occurring in the bug. Information such as the last couple of actions you performed before the potential issue occurred is also very useful information for the QA department. Do not assume that the QA representative knows what you are talking about.
• Use proper English, do not use slang, abbreviations or other unclear language when describing the issue. We cannot address bug reports that we do not understand.
• Create a single thread for each issue, lists of bugs are difficult to track and respond to, if you have multiple bug reports please verify that there are not already threads on them and then post them each in their own thread.

Creating a Bug Thread:

When reporting a bug, we would like you to take the time and search the forum to see if your issue is already reported. While we won't delete duplicate reports, it will save us time if you know the issue is already posted and do not repost it. Using keywords (such as a unique element of a crash log or a unit name) is a good way to find threads.

If you haven't found anything, start a new thread with your issue and put [BUG] in the subject while being as descriptive as possible. Additionally, if you have multiple issues, separate them into different threads. Unique bugs should get unique threads.

Try to include steps to reproduce your problem. Be succinct, leave out any opinions on the problem and focus on how best to tell us about it to help resolve the issue.

Crash Logs and System Profiles:

If you have an assertion or game crash, it is extremely important that you copy and paste the crash log into your thread.

Graphic, performance, or other hardware related issues should include a DXDiag (PC) or a System Profile (Mac) of your computer so that we can see what unique configuration you are utilizing as well as your driver information. Most graphical problems are related to video drivers that haven't been updated, so if you encounter a problem please double check that you have the most up-to-date drivers. A screenshot showcasing your issue is also beneficial to have if you have a way to deliver it to Blizzard safely, such as a third-party image hosting site.

To obtain a DXDiag:
- Click on the Start button and select Run. (For Vista Users, press the Windows Key (the key with the Windows logo on your keyboard) + R (at the same time) and skip to step 3)
- In the Open: field type in dxdiag and click the OK button.
- Click Save All Information, then open the file and copy the information into a single post (as much as is allowed).

To obtain a System Profile:
- Click on the Apple at the top-left of your OS and select About This Mac, then More Information
- The System Profiler should open. Save all the information as a Plain Text or RTF file, then open it.
- Copy all the information and place it into the thread reporting your issue.

General Rules and Policies:
For Blizzard Entertainments Forum Code of Conduct go to:
http://forums.battle.net/forum-coc.html

Bumping and Spamming:
Please do not bump threads or spam new threads on the same issue. All posts in this forum are read in the order that it is posted. Bumping threads or spamming new threads on an issue does not help your issue get addressed any faster. Bumping and spamming slows down our process and actually delays bugs getting fixed.

Feedback and Suggestions:
We want to hear your feedback but it needs to be placed in the right forum. All posts should go on the Suggestions forum, located here:
http://forums.battle.net/board.html?sid=5000&forumId=25352526

Deletings Posts Policy:
Posts that have been determined to be Not A Bug, Invalid Issue Reports, or other reasonable posts to make on this forum but that have been disproven will be kept for 24 hours before deletion. If the original poster acknowledges his post before that time, it will be deleted immediately. Posts that are extremely off-topic and other posts that do not belong here will be deleted immediately.

FAQ
*When will this bug be fixed?
As soon as QA has identified a bug and steps for reproducing that bug, we pass it on to the development team to fix. Bugs are usually fixed in order of severity and is usually implemented in an internal version for QA to test thoroughly before public release. This means that typically, known bugs are already fixed in the internal version that QA is testing in preparation for the next patch, but are still active on the version available to players.

*Why was my post deleted?
Please view Blizzard Entertainments Forum Code of Conduct at the following link:
http://forums.battle.net/forum-coc.html

*This unit/race/map/ability is unbalanced. Why won’t Blizzard address this?
While balance discussion is a valid topic and Blizzard cares about player feedback, the bug report forum is not the place for this type of discussion. The balance/general forums are more suited for balance discussions where it is more likely to catch developments eyes.

*Why hasn’t anyone at Blizzard acknowledged this issue?
Unfortunately with the very large volume of reports we receive, we do not have time to respond to every single post. Generally we only respond to a post if we need more information about a report, or if we have confirmed that an issue with be fixed in an upcoming patch.

*Why isn’t this issue on the Known Issues List?
Most often this is because the issue is still being investigated, until we are confident that an issue is understood it will not be listed on the Known Issues post. We also do not list bugs that can be exploited in any way. Please keep in mind that even though we understand an issue it may not be added to the Known Issues List, issues are added to the list when we feel it is appropriate.