DiabloFans

Hey guys,

I decided to compile and start a running list of issues that have been reported both internally here at Blizzard as well as externally on these forums that are not considered bugs. I will try to keep this as up to date as possible.

If any of you feel passionately that these issues should be considered bugs and fixed, please post constructive feedback in the Beta Feedback forums.

Launcher/Agent
When Diablo III crashes, Agent does not close.
Reason: Agent continues to run because it is expecting you to relaunch Diablo III. When running the Launcher after crashing, it will use the Agent.exe that is running instead of loading up a new one. To turn off Agent, close Diablo III normally.

Combat
The Barbarian is able to generate Rage by destroying destructible objects, while the Monk does not generate Spirit by doing this.
Reason: The Barbarian loses Rage when out of combat while the Monk does not. We allowed the Barbarian to gain Rage on destructibles to compensate for this.

Items
Wizard items that are books are classified as Orbs.
Reason: Books are considered orbs in our game because they function just like orbs. The name is a little confusing, but since all the book does is give you stats like an orb, we call them orbs. The only real difference between a book and an orb is the model.

Monsters/NPCs
When the Templar says "How should I train?" the player character does not respond.
Reason: The Templar is letting the player know that he is ready for a new skill to be learned.

Quests/Boss Events
I declined the ready check/joined the game after my party started the Skeleton King boss fight and now I can't participate in the boss fight.
Reason: Our boss fights are heavily scripted for ensure epic encounters. However, it became clear in the early development stages of the game that these events would break if players were allowed to come and go as they pleased. We lock the event to only those who accept it at the time it is initiated to ensure that the event will not break by people entering or exiting the game.

Here is the list of known issues in the Public Beta. This is by no means a complete list, but covers several of the general issues player will encounter or find during their testing.

Issues that occur in specific places are notated with "Act - Level Area". The level area is the name of the location you are in. It is displayed above your minimap.


Battle.net
Text can be cut off while on different Battle.net screens at different resolutions. The current work-around is to set the game to Windowed mode and then change it back to any resolution.

Clicking on "Remember Account" does not remember your account.

Sending an item from the Auction House to a stash that is full will lock your account of the Beta until a server restart.


Battle.net Banner System
Players cannot use a banner to teleport to a player who is not participating in an event started by a party member. For example, if there are three players in a party and player 1 starts the Skeleton King event, players 2 and 3 cannot use their banners to port anywhere even though they are not involved in the Skeleton King event.


Combat
Demon Hunter:
The Demon Hunter will sometimes say "out of Discipline" when she is actually out of Hatred.

Fan of Knives is not being buffed by increased attack speed nor increased casting speed.

The passive skill Brooding has a 5 second-delay buff that is not removed when it is swapped with another passive skill.

The passive skill Thrill of the Hunt has a 10 second-delay buff when it is swapped with another passive skill.


Monk:
When holding down Dashing Strike, the player has a chance to get stuck casting the Skill without spending Spirit.


Environment
Cathedral bookshelves have several issues in the beta. Sometimes loot will drop to the floor above the bookshelf. Other times clicking on the bookshelf will make the player path up to the floor above it. These issues have been fixed for launch.

Act 1 - New Tristram: The door to Cain's House remains closed after the portal to get inside his house opens. The portal works correctly, it just appears over a closed door.

Act 1 - Old Tristram Road: There is a canyon north of New Tristram that displays a solid red and orange glow. The light does not fill the canyon.


Quests
It is possible for the Blacksmith's anvil to not appear when the Blacksmith repairs the crown you turn into him.

Act 1 - The Slaughtered Calf Inn: Leah's VO plays at inconsistent levels when she says " "I came back here to rally the militia, but--".

Act 1 - Old Ruins: When Leah opens the gate during the quest "The Legacy of Cain : Go to the Old Tristram Gate", the lock flies very far off of the gate.

Act 1 - Cemetery of the Forsaken: During the quest "A Shattered Crown : Search for Leoric's Crown in the Cemetery of the Forsaken," the Matriarch's Bones event can break if two or more players click on two different Funerary Urns at the same time.

Act 1 - Cemetery of the Forsaken: You are able to target the Cemetery Gate that leads to the Fields of Misery after using the Stone of Recall during the quest "The Crown of Mad Leoric : Talk to the Blacksmith"


Items
Certain Rare items will lack names.

Some Demon Hunter and Wizard helms are not displaying the correct icon.

Some Witch Doctor-specific item affixes misspell the class as "Witchdoctor".


Monsters/NPCs
Skeletal Archers deal much more damage than other equivilant Skeleton-type monsters

The lore entry for the Skeleton will not play its voice over. The lore entry itself shows up correctly in your Journal.

Hydras that are spawned by killing Arcane-affixed Hydras display the name "!!Missing!!" in the chat log if the player is killed by them.


Compatability
We are aware of the several issues related to nVidia Optimus machines.

Hey guys,

Once again, welcome to the Bug Report Forums! I am very excited to work with all of you.

Now that I've spent the morning going through all of the posts from last night and today, I wanted to touch base with you on what I am looking for in bug reports. Please read through this guide as it explains some Do's and Don't's for bug testing and reporting.

Alright, let's get started.

Ground Rules
First off, feedback is NOT a bug. Anything related to feedback, class balance, boss suggestions, etc. belongs in the Beta Feedback forum.

I read every single thread that is posted on the forums. However, I will not always respond to them. Please DO NOT bump posts. I will ignore and possibly delete any post that simply says "Bump" or calls out for 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 I am unable to reproduce any of them on my end.

Please use the Search feature to search the forum and see what bugs are post. If you have a duplicate thread, I will lock it and point you to the current thread where the bug is being discussed.

Finally, please only discuss bugs within the threads. Avoid completely off topic discussions or other things not related to the bug in the thread.

Bug Writing
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 include a Summary that attempts to accurately describe the bug. I should be able to understand at least 75% of the issue you are reporting simply by looking at your Summary. I understand that the size of the Summary has to be short, but please do your best.

Good summary: Tooltip for the skill Bash has a typo
Bad summary: Bug with smash skill

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? I need to know this stuf.f

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 designers.

Finally, it always helps to attach a link to Photobucket (or another picture hosting site) that displays a screenshot of the bug. If you need to include a , link to a as well.

Types of Bugs
Below are some different types of bugs you will encounter in Diablo III. I also have included the specific information I 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 them, I ask that you include two things. The first is the name of the quest and quest step that you were on during the quest. 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.

The second thing I ask is if this happened 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 I need more information about. For Environment bugs, please describe the issue you and tell me where it is located. The level area you are in can be found above the minimap. Every location in the game has a level area, and it helps to know this before I start looking.

Screenshots are perfect for Environment bugs as well. They will accurately display the issue you are seeing.

Example - In New Tristram, one of the houses is bright pink.

Crashes
Crashes are getting their own section because of their complexity. Anything from your client closing to the entire server going down can be a crash. For these, you just need to be as specific as you can. Is this reproducible? Is this multiplayer only?

For my required information, I would like you to copy paste the beginning of your DxDiag (or config file for Macs). This will tell me what your computer's specs are, what card you are using, and what your drivers are. If a crash log is generated, please copy the crash line and the first few lines of the stack trace as well.

Again, welcome to the Beta Bug Report forums! Following these guidelines will allow all of us to work together as efficiently as possible. Thanks for reading and enjoy the game!