Known Diablo 3 Beta Bugs/Issues - Diabloii.Net

Known Diablo 3 Beta Bugs/Issues


AGTJ points us to Blizzard’s official list of known issues in the Beta. These are bugs great and small, and even though most of you guys aren’t playing the beta (yet) you may recognize some you’ve seen in the beta videos and live streams.

Here are a few of the more interesting bugs; click though for the full list.

  • Desecrated Enlightened DiabloWikiShrines are not granting the 25% experience bonus.
  • We are currently have many problems with the Public Games feature of Beta. We will be disabling this feature in a coming Beta patch.
  • Players cannot join other players who have started an event. For example, if two players start the DiabloWikiSkeleton King event and a third player joins the game, the third player cannot join the Skeleton King event until after it is done.
  • DiabloWikiFan of Knives is not being buffed by increased attack speed nor increased casting speed.
  • When holding down DiabloWikiDashing Strike, the player has a chance to get stuck casting the Skill without spending Spirit.
  • 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 – DiabloWikiCemetery 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 DiabloWikiFunerary Urns at the same time.

This is actually quite a short list for a beta test, and that testifies to how polished Blizzard games are when they reach this stage. (even ones being rushed to make a year-end deadline, like Diablo 3.) That said, there are quite a few bugs, not all minor, and lots of them relate to the environments. That’s a bit worrying since after all, this is the very start of the game, and it must surely be what the devs have the most polished. Ergo, there are there likely to be more bugs in all the other areas, most/all of which will persist into the launch version of the game.

The same logic applies to the rest of the bugs with character skills as well; these low level Beta-accessible skills should be well-tested and balanced by now, yet there are some bugs with them, and the beta feedback forum is full of player reports about skills that are way OP. And runes aren’t even in the game yet, and we know those will hugely increase the balancing issues.

There will certainly be more balance tweaks before release, and post-release patches will attack any remaining bugs, but many testers and observers are worried that D3 will be fairly buggy and messy upon release, based on what they’ve seen in this beta test. Is that a concern you guys share? Do you not worry since you think Bliz Q&A is hitting the rest of the game while the beta’s going on? Or do you just want the game now now NAOW and you’d be perfectly willing to tolerate any number of minor bugs (to be fixed in post-release patches) to get the game a bit sooner?


Here’s the full post quoted:

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.

General

  • Players cannot log into the Public Beta if they have UAC enabled on Windows 7. The current work around is to fully disable UAC (User Account Control) while playing Diablo III.
  • Desecrated Enlightened Shrines are not granting the 25% experience bonus.

Battle.net

  • We are currently have many problems with the Public Games feature of Beta. We will be disabling this feature in a coming Beta patch.
  • Text can be cut off while on different Battle.net screens at different resolutions. The current work-around is to play the game in Windowed mode and to drag the screen to fit the size of your monitor.
  • Clicking on “Remember Account” does not remember your account.
  • Battle.net Banner System

  • Players cannot join other players who have started an event. For example, if two players start the Skeleton King event and a third player joins the game, the third player cannot join the Skeleton King event until after it is done.
  • 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:

  • 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

  • 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

  • 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 equivalent Skeleton-type monsters.
  • The lore entry for the Skeleton will not play it’s 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!!”. This will be fixed for launch.
  • Compatability

  • We are aware of the several issues players are having using nVidia Optimus machines (hybrid Intel Integrated and nVidia Geforce chips). We are currently working on a fix internally.
  • Tagged As: | Categories: Diablo 3 Beta, Diablo 3 Beta Patches

    Comments

    You're not logged in. Register or login to post a comment.
    1. I’m not surprised about the skills – we know that they went to the current skill system late in development.

      If they need to, I think they should postpone the game to get everything polished.

    2. “This is actually quite a short list for a beta test, and that testifies to how polished Blizzard games are when they reach this stage.”

      I don’t know
      considering the number of years they’ve spent on this, the amount of money they have, and the size and experience of their QA team  (and I believe its also undergone a company wide internal beta before the F&F beta), those are some pretty major bugs

      “many problems with the Public Games feature of Beta”
      that’s pretty shocking

      [quote]That’s a bit worrying since after all, this is the very start of the game, and it must surely be what the devs have the most polished. Ergo, there are there likely to be more bugs in all the other areas, most/all of which will persist into the launch version of the game.[/quote]

      really good point

      “Clicking on “Remember Account” does not remember your account.”

      lol

      • ~jamesL

        I was going to say the same thing, what is going on there, 11 years and we are still not sure if the game is out this year…

      • Having been a QA tester, that is actually a very short list of bugs.  

        Also 11 years in “development” does not mean they spent 11 years programming the game.  I don’t know why people equate the two.  There is a whole conceptual phase that occurs before they even begin pre-alpha.  The same thing occurred with Duke Nukem Forever.  People thought they were actually programming the same game for 15 years when during that time the game was canned and restarted multiple times.

        Another common misconception is that early parts of a game get the polish first.  This is not true.  Once the skeleton of the whole game has been set up the developers jump around.  Coding does not follow a linear path.

        With that said some of these issues are rather major.  The public game part in particular.  Assuming they are eyeing a December release date however they still have a lot of time to fix the game up.

        Anyone else with QA experience can tell you that a lot can be fixed within a single day…although on the flip side a lot can break down as well. 🙂

        • If that were a list of all the bugs, sure, it would be short. But this is just a list of the KNOWN bugs that Blizzard has confirmed and are willing to acknowledge a week and a half after the F&F beta started. I would expect this to be a small percentage (less than 10%) of the true number of bugs that are actually in game.

    3. The big, scary bugs are, of course, battle.net related. I suspect we won’t see the closed beta until Error 3 and the other Errors are taken care of.

      • Yeah it might be another SC2 deal all over again.  Diablo 3 will not come out till they get the Multiplayer working right, so if that means delaying the game 4 months they will.  By then the extra time will let them stream line everything. 

        • They’re still within their timeframe, though (beta to begin by the end of september). I think what we’re seeing is the transparency that we generally don’t get, because F&F betas are always under NDA. Except for Diablo III, for some reason.

          If the NDA was in place (as it always has been) then we’d still be sitting here twiddling our thumbs, waiting for the beta to begin, and we wouldn’t have even known about these login errors and things of that nature.

          • Good point. So if they patch that stuff up before the closed beta, we’d normally be none the wiser.

            So we’re essentially seeing a much earlier stage of development than what Blizzard fans are used to.

    4. Long live to Elder Scrolls : Skyrim

    5. Don’t care, want the game now, patch the game later… we’ve been waiting too long for this…
      Anyway i bet the game won’t be released this year…

    6. I’d say, fix as much as possible before 2011 release  :mrgreen:

      Waiting for 2012 release would be total overkill

    7. If history is any indication they will hold on to it until it’s cleaned up.  Diablo 3 will release next year.

    8. I hereby volunteer to assist Blizzard in finding and fixing all bugs.  Be happy to start this afternoon, in fact, and willing to play for as long as it takes to help them get it right.
       
      😆
       
      More seriously, I don’t think what’s there represents all that big of challenge.  We’ll have the usual characters carrying on about QA but the rest of us will just get on with the fun!

    9. This just goes to show what I’ve been thinking all along. The internal Q & A team are just big FanBoIs like the majority of other testers, too damn excited to actually be playing the game then actually TESTING and REPORTING. Seriously?…the bugs that they’ve listed should have been caught internally. RELEASE THE CLOSED BETA!! and I promise the D3 community will catch every bug. If they would have just released the beta to us earlier it would have benefited them in the long run. I just don’t understand how they can’t see that. The more people that are “testing” it, the faster the bugs would be reported and the faster they could fix them.
      You think Blizzard wants the final release to be polished….you forget how OCD the community is 😉

    10. IMO there are a fair amount of bugs and I wonder why they dont have more people playing the full game … (Could at least play through normal – to test all quests and monsters etc …)
      I mean if their beta testers have been bug testing for awhile now; how are all these bugs found? (ya by the friends and family people) but then shouldnt it go to say that there are many things past the skeleton king that are bound to be found also if they would be tested by more then their internal team?
      and I have a solution; let me test for you 🙂 … no but serious … get more people to test the game why not?
       
       
       

      • Because they aren’t that concerned with bugs at this point – at least not bugs in the game itself. Right now they are testing hardware and looking for problems. Once the hardware issues are resolved, they can increase the number of beta testers to put further stress on the servers. If they catch a few bugs along the way, I’m sure they will fix them, but the point of this beta test is to break in the servers and Battle.net.
        The game is going to be patched repeatedly post-release. That’s just a fact. Think about all the parts of the game like runes, high level skills, items, and the other 90-95% of the game that’s not even being tested. If they wanted a bug-free game upon release, they would need to beta test the entire game and we’d probably be looking at another two year wait.

    11. The game is complete, and they’ve got the entire 2011 Q4 to focus on bugs. I don’t think this will delay ship. But after launch, I do think we’ll see plenty of bugs outside of Act 1, due to the limited beta length.

    12. Something I haven’t thought of before that’s actually on my mind now… I was going to jump straight into hardcore and go from there without first playing through softcore. That would have been awesome except I’m not looking forward to losing characters due to them getting randomly stuck or getting randomly one shotted by some bugged monster doing over 9000 damage. MSLE, Nightmare fire enchanted, intendedly working tomb vipers all come to mind and I worry =o.
       
      Maybe I’ll give the game a quick run through on softcore normal first just to give the devs and players more time to discover and fix up the bugs. But then again, playing with zero knowledge on hardcore is just so sexy. Maybe I’ll wait a month or two before getting the game – who am I kidding… *sigh*

      • really, really good point

      • o come on, hardcore isn’t about being fair. It’s about the thrill and danger of losing it all.
        If we die to a bug, well, our deeds will be remembered. Not like it doesn’t happen already when we have internet problems.
         
        😉

    13. I’m not concerned by the list of bugs. They will fix what they can, and get the rest after release. What I wonder about is how their hardware testing is going. The problem with the Public Game seems pretty important. Also, I have seen several login errors and some in-game crashes. I would like to find out more information about the servers/hardware/Battle.net, because I think these are the most likely to delay the game’s release.

      • Yeah, the hardware stuff is my concern, personally. Most of the bugs listed are just annoying. Most of the threads in the bug report forum are just repeats over and over of the same bug because none of the testers bother to read the stickies or any of the other threads.

    14. Seeing the excitement of all the fans and players from Blizzard. I would suggest to start launching the open Beta. The bugs that have been found by now would only be 10% of all the bugs that are left to be found. Starting up the beta would just speed up the progression of the game itself.
      On the other hand, does Blizzard have enough people to solve the flooding messages of bugs when the open beta starts? What do you think?

    15. I think it is very likely that the internal / dev version of the game is quite a few builds ahead of where the current beta is. Some of the bugs listed there have almost assuredly already been reported internally and likely already fixed internally. In fact, I would be willing to bet that the internal dev build of the game is pretty much feature complete and just about ‘release candidate’ ready save the actual purpose of the current closed beta which is testing battle.net functionality and the patching process / server stability.

      • this is a good comment.  I’ll add this.  The number of bugs is irrelevant.  As a programmer, I can tell you one thing with certainty.  Some of the most seemingly minor and simple bugs can prove to be some of the hardest to fix while a bug that looks major ends up being quite trivial.  You can’t judge anything at all by the number of bugs listed except that more bugs = “potential” for some hard to fix issues that take time.    That said, they have quite a few programmers that can be assigned bugs each day and I wouldn’t imagine many bugs taking longer than a day to fix.

      • +1 to all for sane, informed comments

      • Well we know they are with the runes, since that whole system was held back for major remodeling. I’m sure they’re doing more tweaks on skills and monsters and items, etc. But that stuff would all have gotten rebalanced post-release anyway. And the B.net bugs are since that’s a very new system just implemented, so it’s no surprise.

        But lots of the bugs are things that must have been in the game forever, and they’re just minor enough to slip past Q&A. Like I said in the OP, the beta content is what’s been the most tested and done and redone, and yet there are numerous issues. There’s no way they’ve tested all the rest of the game as thoroughly as the first half of act one…

        • Actually I dunno. I think they may have changed some of the quests in the beta to take out certain bits of information, so some of those bugs may be due to that.

          The bookshelf bug, though, is quite perplexing. How did nobody notice that?

      • Heh, just like how the Hellgate final release code was “several builds ahead” of the beta?

        Big joke that turned out to be.

    16. I’ve been watching the streams (like I’m sure many other have been)… I have to say that the game is not terribly buggy… however I’ve seen a few bugs that aren’t on this list… nothing game-breaking tho…

    17. Having been in multiple F&Fs previously, this is a really short list of bugs. A previous comment hit the nail on the head when they said that normaly the unwashed masses are just blissful in their ignorance of this sort of thing. WoW F&F Alpha/Betas have had far worse bugs (chars being randomly deleted, holes in the world, abilities that just kill you to name a few). These are relatively minor bugs, which should be easily fixed with a patch or two.
       
      I’m content that actually the game is pretty polished. How many people do you see complaining that they can’t kill mobs, or that they’ve got stuck in a dungeon for example. How many have been one shot killed or found themselves unable to progress due to gaps in the dungeon layouts (was an issue early on in d2). Overall the game is in a good position for a late November / early December release.
       
      There’s no way they will put out closed beta for a week or two though, no point in having 5000 additional testers if they can’t form public games for a start.  🙄

    18. If there are this many bugs in the early stages, Inferno difficulty must be virtually untested.
      Still want….

    19. It’s really hard to draw many conclusions about the internal-state of the game.  

      We don’t know how long ago they branched the client code & content for this F&F beta, and we don’t know how many fixes they’ve bothered to merge into the beta from the master branch.  Given their goal of the beta hasn’t been “find content bugs” I’m guessing many of these known content/quest/environment issues have already been fixed in the master branch.

      Since its the same content of the Late-July Press Event, I’m guessing its probably based on that branch, which had to have been made well in advance of the Press Event.

    20. No good reason to rush this out, and a few bad ones (like WoW’s holiday content push).
       
      Add in the player response to bugs when their own real money is involved.  March 2012 may be optimistic.

    21. the internal beta test began May 1st,
      that’s 4 months ago
      so it is surprising to see so many bugs, many of them so basic
       

      • Do consider that since then a number of systems have been changed since then which probably got a majority of the testers attention.  I doubt most of the team has been focused on the last run of bug fixing for general game play.

    22. I think people are exaggerating the current state of things.  There really aren’t that many bugs as a number of people said but I think most people are also completely underestimating the progress the team can make in a short time if they are focused on addressing the bugs.  When you consider the number of people involved, there are probably thousands of man-hours per week being spent on polishing and patching the game.  A lot can be done in that time, including polishing later game content that we haven’t even seen.

    23. I could very well be reading too much into this; however, the few bugs where they say, “This will be fixed by launch”, seems to imply that, “These bugs will be fixed on the original release, and not in a Day 0 patch”.  If correct, the relatively few bugs that actually say that might lead one to think that they don’t have much time before the production run starts (as they would then have more time to include more bug fixes for the physical copies).  Of course, a) they could just be acting cautious with their comments, conversely, b) they could be being inconsistent with their comments, and/or, c) I am reading into things, as the tedium of this long wait is starting to make me crack.

      • I think “This will be fixed by launch” could mean, “we already fixed this upstream but we’re not going to merge it to the beta branch”.

    24. Strange, I don’t see the bug where you get a double templar after asking him to join you. I’ve seen this in every video I’ve watched.

      • The templar has a split personality, remember he starts off as a Barbarian.  

        Once you ask the Templar to join, the Barbarian goes off in a sulk!  🙄

      • Thats couse its not a bug, they even have diferent lines when there are 2 of them, something like “One templar is scary, 2 is just overkill” im paraphrasing.

    25. Id rather get the game sooner couse my inner Diaddict is getting out of control.

    26. 2012 here we come!

    27. Blizzard is absolutely anal about their squeeky clean reputation for releasing finished products.  What they do with this game depends to a substantial degree on how they feel about its readiness for primetime.  Alternatively, they may feel that they are in a position to expend some of that reputation to get in on the holiday rush and then catch up with a few patches. 

    28. Bugs like that and it’s only a fraction of the game.. Yikes..

    29. I’m not going to mention names here – but…
      A few years ago, there was a game I was really looking forward to play. Rushed out to get it and installed as soon as I got back, only to learn that I couldn’t even play the damn thing. It took 2 patches before I could even start it up and another several patches before it became stable or even remotely playable…
      With that in mind, this buglist doesn’t spook me at all, to be honest.

    Comments are closed.