RSS feed2009-06-23 21:07:45
Greetings, and welcome to Blizzard's Test Realm Forum!
The purpose of this forum is primarily to collect reports on the latest version of the game that is running on our Public Test Realms. Additionally, well-constructed feedback is also allowed. General discussion will be allowed in specific, Blizzard-sponsored threads to keep the forums clean. The PTR is a critical phase of testing for our product, and Blizzard greatly appreciates our fans' participation and enthusiasm for quality.
Keep in mind that this forum is a direct line of communication to Blizzard Entertainment. It is one of the best ways to bring issues to our attention. All we ask is that you place the critical information about the issue in the first post of each thread.
This forum is much more heavily moderated than other forums such that the fate of every thread is to be deleted or locked, except with discussion threads. Threads that are locked have been noted and are made available to other players to search for their issues. The following threads will be immediately deleted:
1. Duplicate issue reports
2. Invalid issue reports
3. Poorly constructed feedback (see below)
4. Posts requesting information on game mechanics (How does this work now?), non-PTR information (release dates, server status) or PTR Server configuration (Premades, Training Dummies)
5. Requests for help already covered in existing topics
6. Reposts of deleted threads
7. Posts made on other forums (Don't spam.)
8. "Accomplishment
9. Posts requesting status updates on existing issues.
10. Bug compilation posts. These posts make it very difficult to do our job. Please break out your bugs into individual threads. Not all threads will be deleted but one thread = one bug is preferred.
11. Bugs that aren't specific to the build on the PTR.
Before reporting any issue, please insure that you are running the latest version of the PTR. Your issue should be retested if you are not doing so. Posts that describe issues that occur in invalid builds will be deleted. See the thread at the top of the forum for information about the latest test build.
Before you do anything, read the stickies on the Bug Report Forum:
http://f
Below are the types of posts typically made on this forum:
[BUG]
Before you do anything, search the forum to see if your issue is already reported. Duplicate posts will be deleted. Using keywords (such as a unique element of a crash log or an ability 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.
If you have an assertion or game crash, it is extremely important that you copy and paste the crash log into your thread. Double check that you are running the latest game client version: your crash log will indicate the build the crash occurred in (Note that Macs will have a 1 placed before their build. Example: 18970 is build 8970).
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, 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.
----------------
[FEEDBACK]
While we mainly look for issue reports on this forum, feedback can also be left. To insure that your feedback stays on the forum and isn't deleted, adhere to the following guidelines:
1. Put [FEEDBACK] in your header and make the subject as descriptive and succinct as possible (such as just the ability name or class you are providing feedback on).
2. Proper spelling and grammar. Take time to construct your feedback. Don't use acronyms.
3. Don't be emotional. Just provide straightforward facts. If it’s a problem, logic will win the day, not flashy words.
4. Break down your feedback into logical sections. A wall of text is hard to process.
5. Provide hard evidence for any claims that you make, comparing them against other classes / mechanics as much as possible. Isolated viewpoints, unsubstantiated claims and invalid data will result in a thread deletion. This might mean spending significant time generating test data, but if you're uninformed or your opinion can best be described as "I think", then it isn't good enough. An informed view of the entire picture and how it interacts with everything will make your feedback that much stronger.
6. It is much better if the meat of your feedback focuses on outlining the problem than offering a solution to said problem.
7. Words to avoid: nerf, sucks, QQ, "I demand", harsh language, etc.
8. Write your feedback outside the forum software. Idling too long will automatically log you out and cause all your work to be lost.
9. Calling for wide sweeping changes or total revamps are not good feedback threads.
10. Feedback threads based on observations during normal play aren't good. If you observe a problem, attempt to reproduce it in a controlled environment and confirm your hypothesis before posting about it.
[SUGGESTIONS]
If a game mechanic is working as intended or described in the game, then any change request would be a suggestion. Suggestions for current PTR or Live retail content should be placed in the Suggestions forum:
http://f
There's much more that isn't covered by this one thread. If you have questions, please check the stickies first, search the forum, and post on this thread only if you cannot absolutely find any help. Please try and keep this thread clean of any issue reports or other problems. I'll do my best to answer any concerns.
[PTR INSTALLATION / DOWNLOAD ISSUES]
First, check the installation guide stickied at the top of this forum. If you still have trouble, please post your problems in the Technical Support Forum. They will be able to assist you. This forum should be kept to in-game client issues. The technical forum can be accessed by the Forum Nav at the top-left of your window.
[CHECKLIST OF THINGS TO DO BEFORE TESTING]
1. Make sure you are running the correct version of the game. This can't be stressed enough.
2. Update all your hardware drivers, especially video cards. This is the #1 reason people encounter issues with a game.
3. We read all reports, but we can't respond to every one. Please bring your patience with you.
----------------
[HELP]
Crashes
1) Check the Blizzard Support website for your error message:
(http://u
2) If your issue is still not resolved after reading that, create your own thread with information about the issue, your DXDiag (or system profile) and your PTR build number. To obtain that information, view the [BUG] section above.
Invalid Login Errors
To solve this, do the following:
1) Try using an older password. This does include any passwords Blizzard has sent you if you reset your password. *Note, if you cannot remember an older password, you're out of luck*
2) Make sure your game is the latest version. To find out what the latest version of the PTR is and how to find out what your version is, see the top of the Test Realm Forum.
3) Make sure your account has been active for ~2 weeks prior to the PTR announcement.
Character Copy
Don't make posts about Character Copies... Check your Character Copy Status and just be patient. There's an Average Wait Time that you can use to go by. However, that's just an average, if it takes a little longer than just be patient, if it's quicker, then lucky you.
UI, Macros, and Addons
To get addons onto the PTR, see here:
(http://w
For help with any of this (creating, writing, updating, etc), head over to the UI&Macros Forums, they'll be more than willing to help you:
(http://f
-------------
[CODE OF CONDUCT]
This forum, by necessity, needs to stay focused on the issues. Feedback and issue reports from people who have downloaded the PTR and experienced the changes live is the optimal scenario, but this doesn't encompass all who post on this forum.
Any forum user that posts on this forum that shows extreme disrespect or makes disparaging, insulting comments towards Blizzard Entertainment or other testers trying to submit feedback / issue reports will have their general forum privileges revoked. The more severe the transgression, the lengthier the ban.
Please, be professional and courteous to your fellow posters, even if you disagree with what they are saying. Anything else won't be tolerated.
The purpose of this forum is primarily to collect reports on the latest version of the game that is running on our Public Test Realms. Additionally, well-constructed feedback is also allowed. General discussion will be allowed in specific, Blizzard-sponsored threads to keep the forums clean. The PTR is a critical phase of testing for our product, and Blizzard greatly appreciates our fans' participation and enthusiasm for quality.
Keep in mind that this forum is a direct line of communication to Blizzard Entertainment. It is one of the best ways to bring issues to our attention. All we ask is that you place the critical information about the issue in the first post of each thread.
This forum is much more heavily moderated than other forums such that the fate of every thread is to be deleted or locked, except with discussion threads. Threads that are locked have been noted and are made available to other players to search for their issues. The following threads will be immediately deleted:
1. Duplicate issue reports
2. Invalid issue reports
3. Poorly constructed feedback (see below)
4. Posts requesting information on game mechanics (How does this work now?), non-PTR information (release dates, server status) or PTR Server configuration (Premades, Training Dummies)
5. Requests for help already covered in existing topics
6. Reposts of deleted threads
7. Posts made on other forums (Don't spam.)
8. "Accomplishment
9. Posts requesting status updates on existing issues.
10. Bug compilation posts. These posts make it very difficult to do our job. Please break out your bugs into individual threads. Not all threads will be deleted but one thread = one bug is preferred.
11. Bugs that aren't specific to the build on the PTR.
Before reporting any issue, please insure that you are running the latest version of the PTR. Your issue should be retested if you are not doing so. Posts that describe issues that occur in invalid builds will be deleted. See the thread at the top of the forum for information about the latest test build.
Before you do anything, read the stickies on the Bug Report Forum:
http://f
Below are the types of posts typically made on this forum:
[BUG]
Before you do anything, search the forum to see if your issue is already reported. Duplicate posts will be deleted. Using keywords (such as a unique element of a crash log or an ability 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.
If you have an assertion or game crash, it is extremely important that you copy and paste the crash log into your thread. Double check that you are running the latest game client version: your crash log will indicate the build the crash occurred in (Note that Macs will have a 1 placed before their build. Example: 18970 is build 8970).
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, 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.
----------------
[FEEDBACK]
While we mainly look for issue reports on this forum, feedback can also be left. To insure that your feedback stays on the forum and isn't deleted, adhere to the following guidelines:
1. Put [FEEDBACK] in your header and make the subject as descriptive and succinct as possible (such as just the ability name or class you are providing feedback on).
2. Proper spelling and grammar. Take time to construct your feedback. Don't use acronyms.
3. Don't be emotional. Just provide straightforward facts. If it’s a problem, logic will win the day, not flashy words.
4. Break down your feedback into logical sections. A wall of text is hard to process.
5. Provide hard evidence for any claims that you make, comparing them against other classes / mechanics as much as possible. Isolated viewpoints, unsubstantiated claims and invalid data will result in a thread deletion. This might mean spending significant time generating test data, but if you're uninformed or your opinion can best be described as "I think", then it isn't good enough. An informed view of the entire picture and how it interacts with everything will make your feedback that much stronger.
6. It is much better if the meat of your feedback focuses on outlining the problem than offering a solution to said problem.
7. Words to avoid: nerf, sucks, QQ, "I demand", harsh language, etc.
8. Write your feedback outside the forum software. Idling too long will automatically log you out and cause all your work to be lost.
9. Calling for wide sweeping changes or total revamps are not good feedback threads.
10. Feedback threads based on observations during normal play aren't good. If you observe a problem, attempt to reproduce it in a controlled environment and confirm your hypothesis before posting about it.
[SUGGESTIONS]
If a game mechanic is working as intended or described in the game, then any change request would be a suggestion. Suggestions for current PTR or Live retail content should be placed in the Suggestions forum:
http://f
There's much more that isn't covered by this one thread. If you have questions, please check the stickies first, search the forum, and post on this thread only if you cannot absolutely find any help. Please try and keep this thread clean of any issue reports or other problems. I'll do my best to answer any concerns.
[PTR INSTALLATION / DOWNLOAD ISSUES]
First, check the installation guide stickied at the top of this forum. If you still have trouble, please post your problems in the Technical Support Forum. They will be able to assist you. This forum should be kept to in-game client issues. The technical forum can be accessed by the Forum Nav at the top-left of your window.
[CHECKLIST OF THINGS TO DO BEFORE TESTING]
1. Make sure you are running the correct version of the game. This can't be stressed enough.
2. Update all your hardware drivers, especially video cards. This is the #1 reason people encounter issues with a game.
3. We read all reports, but we can't respond to every one. Please bring your patience with you.
----------------
[HELP]
Crashes
1) Check the Blizzard Support website for your error message:
(http://u
2) If your issue is still not resolved after reading that, create your own thread with information about the issue, your DXDiag (or system profile) and your PTR build number. To obtain that information, view the [BUG] section above.
Invalid Login Errors
To solve this, do the following:
1) Try using an older password. This does include any passwords Blizzard has sent you if you reset your password. *Note, if you cannot remember an older password, you're out of luck*
2) Make sure your game is the latest version. To find out what the latest version of the PTR is and how to find out what your version is, see the top of the Test Realm Forum.
3) Make sure your account has been active for ~2 weeks prior to the PTR announcement.
Character Copy
Don't make posts about Character Copies... Check your Character Copy Status and just be patient. There's an Average Wait Time that you can use to go by. However, that's just an average, if it takes a little longer than just be patient, if it's quicker, then lucky you.
UI, Macros, and Addons
To get addons onto the PTR, see here:
(http://w
For help with any of this (creating, writing, updating, etc), head over to the UI&Macros Forums, they'll be more than willing to help you:
(http://f
-------------
[CODE OF CONDUCT]
This forum, by necessity, needs to stay focused on the issues. Feedback and issue reports from people who have downloaded the PTR and experienced the changes live is the optimal scenario, but this doesn't encompass all who post on this forum.
Any forum user that posts on this forum that shows extreme disrespect or makes disparaging, insulting comments towards Blizzard Entertainment or other testers trying to submit feedback / issue reports will have their general forum privileges revoked. The more severe the transgression, the lengthier the ban.
Please, be professional and courteous to your fellow posters, even if you disagree with what they are saying. Anything else won't be tolerated.
Dresorull
Blizzard QA
