World of Warcraft

PTR Bug Reports

The Primary purpose of the PTR forum is reporting bugs in the new content. Please use these guidelines when reporting bugs.

The more information you can provide to Blizzard about the bug you are experiencing, the more likely it is to get addressed by them and subsequently, the developers. This includes but is no limited to: a full description of what happened, steps for reproduction if possible, screenshots, crash logs, etc.
I can not stress how useful screenshots can be for helping Blizzard reproduce a bug.

Also, feel free to post on other players bug reports if you have similar reports to file or simply more information on that particular issue that was not provided by the original poster.

If a reported issue is already known, one of the moderators may lock the thread at their discretion.

PTR In-game Feedback Tool
In the some Public Test Realm builds we include a new tool for reporting player feedback in the form of bug reports, suggestions and player surveys.

You can find this new tool via the blue “B” button to the right of your mini-map, clicking on it will bring up the Feedback UI. You can also access the tool by typing “/bug” or “/suggest” in the chat bar.

Please use this tool whenever you encounter a bug in the game, this tool gathers character and location information that QA uses to identify and document issues. Even if you intend to post about an issue here in this forum (which is still being monitored) please also submit an in game report at the time the issue occurs.

Some tips when using the tool:
- Submit any issue you encounter immediately, not only will the details be fresh in your mind but the information the tool gathers will be most relevant.
- There is a limited amount of space to describe your issue, refrain from including information not directly related to the issue.
- Make sure to accurately answer the initial questions this helps us classify issues and see trends.
- Be sure to submit bug reports and suggestions appropriately so they will reach the correct people.

PTR Bug Reporting FAQ
• Q. I crashed, what do I do?
A. Whenever you crash you should be presented with a window to send the crash information to Blizzard. Please always do so. Also please always be sure to fill out the description of what led up to the crash. We track crash logs very closely and descriptions of the circumstances are very valuable to us.
Although it is not necessary to post your crash log here in the forums you can if you would like.

• Q. What type of information should I provide in my bug report?
A. First and most important is a thorough description of the problem and what occurred leading up the issue. The more information you provide us the faster we can reproduce your issue and start working on a fix.
Always provide what Operating system you are running when encountering the issue, Mac or Windows and the version.
Screenshots are very valuable to us and help speed the process of identifying bugs.
Any additional information that you feel might be useful to us, such as testing results on other hardware or by other players on different accounts.

• Q. How can I provide you with more information about my computer?
A. On windows PCs please provide the DXDiag information.
To test and obtain the DXDIAG information, please follow the instructions below:

Important Note: Please reboot your system prior to creating the dxdiag and files.

1. Click on Start.
2. Click on Run.
3. Type in DXDIAG and press Enter or click OK, this will open the DirectX diagnostic tool. Run the DirectDraw, Direct3D and DirectSound tests found under the Display and Sound tabs before creating the dxdiag.txt file.
4. Click on the Save All Information Button (save this file to your windows desktop and name it dxdiag).

On Macs please provide the type of Mac you are using (PPC or Intel) and the version of the Mac OS.
• Q. I have a screenshot or video of my bug, how can I get it to you?
A. There are a number of free image and video hosting services available on the internet that you can use to display your screenshots and videos.

• Q. I have a bug with one of my add-ons.
A. As UI add-ons are not provided by Blizzard we do not support their uses on the PTRs. You should contact the Add-on creator for assistance.

• Q. Why isn’t this bug fixed yet?
A. Identifying a bug is merely the first step in a long process before a fix can be added to the PTR, do not expect bugs to be fixed immediately.


Please keep in mind the more information you can provide to Blizzard and the Devs about any crashes and bugs, this includes screenshots off graphical and other issues, will greatly aid Blizzard in tracking down and fixing issues that are found.

Also while the PTR is not named a Beta by Blizzard it effectively is, you are testing unreleased content and there may be bugs, numbers can be changed at a later date and time once functionality bugs are corrected

Suggested layout for a bug report - Feel free to copy this to a new post

World of WarCraft: Test Build Number - build xxxxx <- this will help determin if you are using the correct version number

Computer Type and Model - Desktop/Laptop/Netbook - custom builders just put type

Processor - PPC/Intel/AMD - please provide type and speed if you know it

Graphics - ATI(AMD) Radeon/Nvidia GForce/Intel - please state model if you know it also if it is onboard

Operating System - MacOS X/Windows XP/Vista/7 - please state if you are using a 64 bit OS

Running Programs - Please include your Firewall and Anti-Virus even if they are in a disabled state

Please provide any error messages in full below:

<space to fill with you error>

Where does this issue occur?

How often does this issue occur?

If this issue is repeatable please provide steps below

Example Bug Report

World of WarCraft: Test Build Number - build 13449

Computer Type and Model - Desktop

Processor - Intel I7 860

Graphics - Nvidia GForce 240

Operating System - Windows 7 64 bit

Running Programs - Firefox, WinRar, Task Manager, AVG Free 9.0, Outpost Firewall 7.0 (running in disabled mode)

Please provide any error messages in full below:

Every time I open the graphic setting I get an error

Message: Interface\FrameXML\GraphicsQualityLevels.lua:375: bad argument #1 to 'format' (string expected, got nil)
Time: 09/15/10 16:47:11
Count: 1
Stack: [C]: in function `format'
Interface\FrameXML\GraphicsQualityLevels.lua:375: in function `readfilter'
Interface\FrameXML\VideoOptionsPanels.lua:520: in function `initFunction'
Interface\FrameXML\UIDropDownMenu.lua:69: in function `VideoOptionsDropDownMenu_Initialize'
Interface\FrameXML\VideoOptionsPanels.lua:439: in function `Graphics_DropDownRefreshValue'
Interface\FrameXML\VideoOptionsPanels.lua:424: in function `RefreshValue'
Interface\FrameXML\OptionsPanelTemplates.lua:258: in function <Interface\FrameXML\OptionsPanelTemplates.lua:256>
[C]: in function `securecall'
Interface\FrameXML\OptionsPanelTemplates.lua:289: in function `BlizzardOptionsPanel_Refresh'
Interface\FrameXML\VideoOptionsPanels.lua:179: in function `Graphics_Refresh'
Interface\FrameXML\VideoOptionsPanels.lua:170: in function <Interface\FrameXML\VideoOptionsPanels.lua:169>
[C]: in function `pcall'
...
Interface\FrameXML\OptionsFrameTemplates.lua:284: in function `OptionsFrame_RefreshCategories'
Interface\FrameXML\OptionsFrameTemplates.lua:213: in function `OptionsFrame_OnShow'
[string "*:OnShow"]:1: in function <[string "*:OnShow"]:1>
[C]: in function `Show'
Interface\FrameXML\UIParent.lua:1445: in function `SetUIPanel'
Interface\FrameXML\UIParent.lua:1250: in function `ShowUIPanel'
Interface\FrameXML\UIParent.lua:1176: in function <Interface\FrameXML\UIParent.lua:1172>
[C]: in function `SetAttribute'
Interface\FrameXML\UIParent.lua:1856: in function `ShowUIPanel'
[string "*:OnClick"]:2: in function <[string "*:OnClick"]:1>

Locals: (*temporary) = nil
(*temporary) = 1
(*temporary) = "string expected, got nil"


Where does this issue occur?

When I open the graphics options

How often does this issue occur?

Everytime

If this issue is repeatable please provide steps below

Open the graphics options from login screen or ingame

As Addons are available on the PTR the addon developers are actively updating them to be compliant with the current builds.

Can you please provide a list of any running addons with your report.

Please note however Addons are not supported by Blizzard in any way. Any problems with your addon must be directed to the developer of the addon.

If you are having a repeatable crash please disable your addons and then try and recreate your problem, if you are still having the problem please create a new thread with your error and information using the guide.

This will help those of us who are doing the technical support deal with your problem quickly as we can normally spot common issues quite fast with a full report and running with no addons rules them out as a possible cause.

If you need to gain access to an error log that you have just sent or attempted to send to Blizzard to post on these forums for more active technical support or you have been requested to you can find these in your PTR installation directory.

on Windows 7 for example the default location is

C:\Users\Public\Games\World of Warcraft Public Test

Within this director there is a folder called /Errors in this folder are your crash logs they are all dated and time stamped so just look for the last one.

I do realise that the report is quite long and also that the forums don't fit the entire post, please break it down as much as you can, and try not to miss anything. I know it can happen, hopefully we can use this to track down a possible solution for your issue.

I wrote it on the old forums, and I put it up when there's a PTR because a lot of people don't understand the purpose of testing.

I however have done it for a living and still do it freelance, I also teach people how to beta test from time to time.

Maybe if more people knew how to provide decent feedback rather then "QQ they nerfed my class again posts," then QA wouldn't have such a hard time finding and fixing the bugs that pass through the system occasionally.

The purpose of the PTR which is a beta test, is large scale deployment of infrastructure and code changes, along with other balancing issues relating to the game itself and to see the impact on a larger user base with the intention to compile more relevant data, more quickly then can be done via small teams and in-house sessions.

This can be anything from impact on server and network models and stresses, to how the existing system handles something new like a new data base for example.

Help us, help you with your PTR problems and maybe fix some bugs along the way.

*cough*

World of WarCraft: 13449

Computer Type and Model - Laptop HP

Processor - Intel

Graphics - Nvidia

Operating System - Vista

Running Programs - SpywareBlaster, Norton 360

Please provide any error messages in full below:
Way WAY too big :/ it is a critical wow error.

Where does this issue occur?
When loading into World of Warcraft/Arena

How often does this issue occur?
Depends, sometimes I am not able to log on at all.

If this issue is repeatable please provide steps below.
When Loading onto wow, double click the character you want to play.
Just simply enter the arena.

Thanks for the nudge in the right direction Nekoko.

Well the error is the important bit :p

That has all the relevant information debug information that I need to look through

I know it's a lot of data which is why breaking it into small chunks in a new thread is helpful, but at least you are moving in the right direction, I will try and keep on top of it and pass on what I find ;)

http://eu.battle.net/wow/en/forum/topic/1498672476?page=1#3
The error message took 51 pages on Microsoft word...

yeah I know plus occasionally the new forums have an attack of the wobbles, not to mention it doesn't give you a character limit number so if you go over you have no idea half the time.

Most of the "thread" information is there that I need, so you can skip alot of that, if the rest of the post is just that sort of "Thread X" Blah info then that's all good, if it goes on to some other information start from there.

I do however have a raid in 10 mins, so it might be later on tonight or even tomorrow before I can digest and go through it properly for you.

hello i just whant to report a normal smal bug em in Woodpaw Den, there is a flying fire o.o its in the air can walk under it and all. but it might only be a normal design mistake, but still who knows.

You might be better off putting that in a separate topic Airianda as this is for crash bugs not for graphical bugs.

sending it back to top to help people give good reports.

I do like that there are very few crash issues on this test cycle *thumbs up to QA*

Thanks for the sticky guys :D