Welcome Thread & FAQ

Bug Report
En Taro Tassadar, and welcome to the Starcraft II Bug Report forum!

The purpose of this forum is to collect issue reports on the Live version of the game. 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. Unless a moderator asks for more information, all the critical information of a post should be contained in the subject and first post.
Every post will be responded to in some fashion before being locked. When a thread is locked, it means we have sufficient information on the issue and won't require any further assistance.
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:
    * Please 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.

Feedback and Suggestions:
We want to hear your feedback but it needs to be placed in the right forum. All suggestion or feedback posts should go on the Gameplay discussion forums.

General Rules and Policies:
Blizzard Entertainments Forum Code of Conduct
Common Confusion Reports

Bumping and Spamming:
Please do not bump threads or spam new threads on the same issue. All posts in this forum are read by a member of the QA team 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.

Deleting Posts Policy:
Posts that have been determined to be Not A Bug, Invalid Issue Reports, duplicates without more information, 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. Deleting invalid posts helps keep the forum clean and organized for QA to sort through.

• When will a 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 are 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?

• 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, QA does 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 an 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.

Crash Reporting Guidelines
When you crash an Error Reporter window will appear with the crash log and an area to enter a description of what you were doing when the crash occurred. Please be sure to describe what you did for the last few minutes before the crash occurred before sending the report, as well as including your characters name and identifier. Adding your character name and character code to the report will assist us in linking your crash report to your forum report. If you have an assertion or game crash, it is extremely important that you copy and paste the top portion (including the crash line and top 2 lines of the stack trace) of your crash log into your thread. We do not need to see the user/computer name so please edit out them out of the post on the forums.
Battle.net Bug Guidelines
If you encounter issues with achievements, matchmaking, friends, or other Battle.net 2.0 services, please include the following information.
  • Name and Character Codes of all players involved (ie, me and my friend Raynor.123 cannot match for 2v2).

  • For achievement bugs, please include the name of the achievement and any progress you have on it.

  • For Matchmaking or Ladder related issues, include your rank, league and stats information from the time the issue occurred.

  • Always include a brief description of the problem you are encountering.

  • Include a screenshot if applicable.

As always the more information you can provide, the better!
Gameplay Bug Guidelines
If you encounter issues with units, structures, abilities or any other game functionality, please include all relevant information.
  • Units, structures or spells involved.

  • Related upgrades you or your opponent had researched.

  • Screenshots and replays are very helpful, please include a link to them if possible in your post.

Graphics Bug Guidelines
Graphic, performance, or other hardware related issues should include a DXDiag (PC) or 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.

Please be sure to mention whether you are using an SLI / Crossfire setup or not in addition to the following:

If you have a Windows PC, we will need the following information from your DxDiag:
To obtain a DXDiag:
- Press the Windows Key + R at the same time.
- In the Open: field type in dxdiag and click the OK button.
- Click Save All Information, then open the file and copy the requested information into your post.

    - Operating System:
    - Processor Info:
    - Ram Info:
    - Direct X Version:
    - Card Name:
    - Manufacturer:
    - Chip Type:
    - Device Identifier:
    - Vendor ID:
    - Device ID:
    - Display Memory:
    - Current Mode:
    - Native Mode:
    - Driver Version:
    - Driver Date/Size:

If you have a Mac, we will need the following information from your system profile:
To obtain a System Profile:
- Open the Apple menu and choose About this Mac.
- Click "More Info..."
- Copy the requested information into your forums post.

    - OS Version:
    - Processor:
    - Graphics Card:
    - Memory:
We've received a large number of reports in this forum that are either not bugs or should be directed to another location. In order to cut down on the amount of these threads being created we have created a FAQ style list of some of the common reports:

· This player is hacking!
We have a hacks team that handles all of these reports. Please report any hacking activity to hacks@blizzard.com with as much information as possible.

· My player color is set to Green, even though I picked another color in the lobby.
There is a setting in the game that allows you to always be displayed as green, your allies as yellow, and your enemies as red. This can be toggled with 'Alt+F' or by clicking the “handshake” icon by the minimap.

· I found a bug on a custom map (non-Blizzard map).
Blizzard does not support issues with player created custom maps. Please contact the map author if you'd like to see a bug fixed.

· You have Left the Game.
The Score Screen will say that you have left a game in progress if there are any players at all left in the game, including your allies. Your Win/Loss status will be viewable in your match history some time later, though it can take a variable amount of time for Battle.net to clear matches in progress once all players have left. This delay also applies to games with AI allies as well as players.

· Stuck at Players Found.
Some college campuses have been known to block a number of ports that can prevent players from joining multiplayer matches. This can be fixed by having your IT department open these ports. Please see the College Campus Network Connection Issues thread on the technical support forum for a list of ports and more information.

Join the Conversation

Return to Forum