So, you were lucky enough to get into the Beta. Awesome! Enjoy your early look at the game! Though as a Beta participant, you do have a certain level of responsibility to fulfill. After all, the whole point of a Beta is to polish the game for release. So with that in mind, here's what you need to know to help make Diablo III even better.
Think You Found A Bug?
So you think you found a bug, and want to squash that sucker. Before taking any action on the forums, be sure to check it against this list of non-bugs which may be mistaken as one.
<input type='button' class='bbc_spoiler_show' value='Show more stuff' />
Official Blizzard Quote:
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.
Check this often, it will likely be updated regularly
Turns Out It Was A Bug?
Great! Just be sure to check your bug against this list of known bugs before writing up your bug report.
<input type='button' class='bbc_spoiler_show' value='Show more stuff' />
Official Blizzard Quote:
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.
Check this often, it will likely be updated regularly
How To Write A Good Bug Report
So your bug is neither a non-bug, or a known bug, congrats! To be as helpful as possible in reporting your bug, be sure to read through Vasadan's proper bug reporting guide before posting in the Bug Report Forum.
<input type='button' class='bbc_spoiler_show' value='Show more stuff' />
Official Blizzard Quote:
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!
Reporting Hacks, Cheating, And Exploits
Due to the viral nature of these problems, they must be handled differently than other issues. Never under any circumstance post a thread about one of these on the forums, it'll just spread the problem. Your thread will be deleted, and you could be facing a permanent ban. If you find an issue of this type please send a detailed Email to hacks@blizzard.com, or fill out a form here.
Beta Feedback
Squashing bugs and reporting hacks aren't the only productive parts of a Beta. Player feedback is also very important for bettering the game before release. Before you express your suggestions for the game on the Beta Feedback Forums, make sure you've read through the Feedback Guidelines.
Problems With Streaming And Downloading
Having trouble downloading the game, or streaming it to hungry viewers? Check your issues against the currently known problems, and possible solutions here, or if you're on a Mac here.
Now that you know how to handle any potential problems, enjoy your time playing !
Diablofans Social Media
For those who weren't granted Beta access yet, don't fret. We here at Diablofans have a robust, ever expanding collection of Diablo III content just waiting for you to check it out! Be sure to regularly visit all of our branches for your recommended daily amount of Diablo III. Subscribe to our YouTube, Like us on FaceBook, follow us on Twitter, and join us in IRC!
“We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about.” - Albert Einstein
Hahaha, that looks like half my sig! YEAH! Should have trademarked it...
Good post btw. There are quite a few beta testers that reports bugs without screenshots/vids or they post like 5 bugs in one thread (I'm assuming you probably made this topic because of that). This must be annoying for the blizz team as well. Hope the testers see this and act accordingly!
Hahaha, that looks like half my sig! YEAH! Should have trademarked it...
Good post btw. There are quite a few beta testers that reports bugs without screenshots/vids or they post like 5 bugs in one thread (I'm assuming you probably made this topic because of that). This must be annoying for the blizz team as well. Hope the testers see this and act accordingly!
Edit: Don't mind you using it
Thank you
Also, good eye. I was using it as a placeholder until I found the rendered image, which is up now :P.
If the bug is already listed in the known bug list, or non-bug list, there's no need to report on it. Even if it isn't listed in those lists, it would be wise to use the search bar on the bug report forums to see if anyone has posted about it before. If after all three of those checks come back negative, than go ahead and report it :).
“We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about.” - Albert Einstein
That's actually the one I wanted, but couldn't find it. For some reason, when I allowed "Better Pop Up Blocker" on chrome on battlenet, the images changed to the old beta ones...
Ya exactly. I dont thing any real beta invites have gone out that dont include people with special access, like F&F, Press, and special invitee's given a key. As opposed to players who simply got their Battle.Net accounts upgraded because they had the right system specs and were lucky enough to get into a wave.
Ya exactly. I dont thing any real beta invites have gone out that dont include people with special access, like F&F, Press, and special invitee's given a key. As opposed to players who simply got their Battle.Net accounts upgraded because they had the right system specs and were lucky enough to get into a wave.
The actual Beta has begun, no doubt about that guys.
Official Blizzard Quote:
The fiery gates leading to the Burning Hells have opened, and the Diablo III beta test has officially begun! Invitations to participate in the beta test are now being delivered to the chosen heroes. As with beta tests for other Blizzard Entertainment games, the testing process for Diablo III will occur in phases. In each phase we will be selecting players who have opted in via their Battle.net accounts, and we welcome everyone to provide feedback on the official forums.
If you have a beta license, you are free to show, share, or talk about any portion of the beta content to which you have access, as this beta test is not confidential.
We’d like to remind those looking forward to an invite to be wary of phishing attempts. If you believe you’ve received an invite to the Diablo III beta test, it’s best to refrain from clicking on any links in the email, and instead log in to your Battle.net account to see if a Diablo III beta game account was granted. Or, if you were sent a key, attempt to add it manually by going to the Add or Upgrade a Game section of the Battle.net account management page.
For those who have received an invite to the beta test, we thank you for helping us test out our server stability and hardware. For those of you still hoping for an invite, we wish you the best of luck and hope you’ll keep an eye out for some of the beta-key giveaways and promotions we’ll have right here on the Diablo III community site.
For more information, please see the official press release and the beta opt-in announcement and FAQ.
“We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about.” - Albert Einstein
Yes we have seen that blue post, why wouldn't diablo fans post something saying the public invites have gone out then? They posted that blue post when they said the closed beta began and the press and such got their keys.
Yes we have seen that blue post, why wouldn't diablo fans post something saying the public invites have gone out then? They posted that blue post when they said the closed beta began and the press and such got their keys.
We did post on it, it was an update to the already existing announcement of the Press invites going out. In particular, this was said:
UPDATE: It's official! The Closed Beta has now begun... This means those of you opting in can potentially receive invites.
“We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about.” - Albert Einstein
“We act as though comfort and luxury were the chief requirements of life, when all that we need to make us happy is something to be enthusiastic about.” - Albert Einstein
Obviously beta has begun and invites have gone out. I just ment, in my opinion, no public waves that include "significant" amount of players have went out. From what ive seen, everyone in it now, got in through a special circumstance. Im not saying people havent gotten in randomly or through luck or having right system specs, I just havent seen it.
Yea the people who got in through beta opt-in are certainly few and far between. It seems as though most of the people who got in this wave are press and the like and not much else, although there certainly were a few lucky people who got in randomly. As Winged said its the first and (probably) the smallest wave of invites we'll see. Obviously you'll here it from us if suddenly a bunch more people start to get invited, but as of right now its still a very limited beta.
It should be noted, though, that this is going to remain very small throughout its duration. Its never going to get up to the size of, say, the SC2 beta. So although future waves of invites will hopefully be larger, that doesn't mean its ever going to get all that big. Hopefully, because of the limited content, Blizzard will have to send out many waves of invites in order to maintain the amount of active people they are aiming for. That's just something we're going to have to find out about as time passes.
If more press-related people were invited in that initial wave than non-press invitee's, many people would call that the "Press Wave". Course it could be that 20x more non-press folks were given access, who knows
Also, Sixen and Force implied in a Diablocast that people getting into the beta would have their Battle.Net account upgrade automatically and an email would be sent. And there wouldn't even be a need to actually read the email. If this method is still being used, then its a safe bet that anyone who got in through typing in a beta key or opt-in key probably had their account or emails specifically flagged for some other reason, as opposed to being included in a normal public wave.
Im not sure there is a lot of news to post. The beta is only 90 minutes long. Pretty much if your looking to learn more about the game, the info is out there. Force has his Lets Play Videos for beta footage. Were waiting on Blizz for more beta invites, details on RMAH, realease date, etc.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
So, you were lucky enough to get into the Beta. Awesome! Enjoy your early look at the game! Though as a Beta participant, you do have a certain level of responsibility to fulfill. After all, the whole point of a Beta is to polish the game for release. So with that in mind, here's what you need to know to help make Diablo III even better.
Think You Found A Bug?
So you think you found a bug, and want to squash that sucker. Before taking any action on the forums, be sure to check it against this list of non-bugs which may be mistaken as one.
Great! Just be sure to check your bug against this list of known bugs before writing up your bug report.
So your bug is neither a non-bug, or a known bug, congrats! To be as helpful as possible in reporting your bug, be sure to read through Vasadan's proper bug reporting guide before posting in the Bug Report Forum.
Due to the viral nature of these problems, they must be handled differently than other issues. Never under any circumstance post a thread about one of these on the forums, it'll just spread the problem. Your thread will be deleted, and you could be facing a permanent ban. If you find an issue of this type please send a detailed Email to hacks@blizzard.com, or fill out a form here.
Beta Feedback
Squashing bugs and reporting hacks aren't the only productive parts of a Beta. Player feedback is also very important for bettering the game before release. Before you express your suggestions for the game on the Beta Feedback Forums, make sure you've read through the Feedback Guidelines.
Problems With Streaming And Downloading
Having trouble downloading the game, or streaming it to hungry viewers? Check your issues against the currently known problems, and possible solutions here, or if you're on a Mac here.
Now that you know how to handle any potential problems, enjoy your time playing !
Diablofans Social Media
For those who weren't granted Beta access yet, don't fret. We here at Diablofans have a robust, ever expanding collection of Diablo III content just waiting for you to check it out! Be sure to regularly visit all of our branches for your recommended daily amount of Diablo III. Subscribe to our YouTube, Like us on FaceBook, follow us on Twitter, and join us in IRC!
Good post btw. There are quite a few beta testers that reports bugs without screenshots/vids or they post like 5 bugs in one thread (I'm assuming you probably made this topic because of that). This must be annoying for the blizz team as well. Hope the testers see this and act accordingly!
Edit: Don't mind you using it
So mean
Thanks.
Also, good eye. I was using it as a placeholder until I found the rendered image, which is up now :P.
I'm not in either, so it's from the heart!
If the bug is already listed in the known bug list, or non-bug list, there's no need to report on it. Even if it isn't listed in those lists, it would be wise to use the search bar on the bug report forums to see if anyone has posted about it before. If after all three of those checks come back negative, than go ahead and report it :).
The actual Beta has begun, no doubt about that guys.
Official Blizzard Quote:
The fiery gates leading to the Burning Hells have opened, and the Diablo III beta test has officially begun! Invitations to participate in the beta test are now being delivered to the chosen heroes. As with beta tests for other Blizzard Entertainment games, the testing process for Diablo III will occur in phases. In each phase we will be selecting players who have opted in via their Battle.net accounts, and we welcome everyone to provide feedback on the official forums.
If you have a beta license, you are free to show, share, or talk about any portion of the beta content to which you have access, as this beta test is not confidential.
We’d like to remind those looking forward to an invite to be wary of phishing attempts. If you believe you’ve received an invite to the Diablo III beta test, it’s best to refrain from clicking on any links in the email, and instead log in to your Battle.net account to see if a Diablo III beta game account was granted. Or, if you were sent a key, attempt to add it manually by going to the Add or Upgrade a Game section of the Battle.net account management page.
For those who have received an invite to the beta test, we thank you for helping us test out our server stability and hardware. For those of you still hoping for an invite, we wish you the best of luck and hope you’ll keep an eye out for some of the beta-key giveaways and promotions we’ll have right here on the Diablo III community site.
For more information, please see the official press release and the beta opt-in announcement and FAQ.
Keep in mind there will be multiple waves of invites, this first wave being the smallest.
It should be noted, though, that this is going to remain very small throughout its duration. Its never going to get up to the size of, say, the SC2 beta. So although future waves of invites will hopefully be larger, that doesn't mean its ever going to get all that big. Hopefully, because of the limited content, Blizzard will have to send out many waves of invites in order to maintain the amount of active people they are aiming for. That's just something we're going to have to find out about as time passes.
Find any Diablo news? Contact me or anyone else on the news team.
DiabloFans: Facebook, Twitter, YouTube, Live Chat