List of Bugs After Maintenance 9/10 and 9/18


#72

I don’t have a question. MetalHead claimed that the initial Blizzard response was that client-side issues were suspected. I was merely posting to confirm that was, indeed, their initial response.

At the time of the initial “reboot your router / flush your DNS cache” response was issued, there were already a number of threads, each with multiple contributors to it, that were complaining of exactly the same thing, all of which occurred directly after the scheduled maintenance.

Standard root cause analysis is that the most likely cause of a problem is the most recent change and, baring in mind many people had exactly the same problem after a maintenance, that points to the maintenance being the cause, not lots of client PCs all over the world suddenly developing router / DNS cache issues.

Regardless, it’s now three days later and we’re still awaiting more news.


#73

Also to add a lot of the player base cannot type in party chat or clan chat and it takes an act of congress to get in a party sometimes,


#74

Wasn’t happening till tuesday when they took it down and broke it, so the logical thing to do is take it down and fix it, but i guess that makes to much sense.


#75

MissCheetah:

I don’t fully understand who you are or what your relationship to all of this is, and you are pretty quick to defend what is happening or not happening. Alienating the community in the way you are is not helping fix anything, and its not reassuring anyone that sometime or anytime soon things will be fixed. Thank You


#76

easy temp fix for the party chat bug, just use “conversation chat”


#77

several things to mention, some of which probably has been mentioned already…
1: can’t talk in party chat,
2: having issues doing invites to guildies
3: the game keeps sounding off the sound bytes regarding skills not being ready regardless of going to cast them or not, and sometimes for several minutes after the rift was closed… any ideas why?
4: the circles for the season are fading way too fast, and a good part of the time they fade within 5 seconds of them appearing, with no chance of getting to them…


#78

The game should really just be roll back , this is absurd It’s been since Tuesday and it keeps getting worse


#79

I agree Mixxx. These issues really make the game painful to play. I am quitting until they fix it. There are no excuses, unless you are hiring high school programmers that do not have experience. As a programmer, I can not understand the issues. Blizz either wants us to suffer or they dont care to fix it. Either way, it is on them and it is unacceptable.


#80

Diablo 3 as a game was built before the modern Bnet infrastructure and communications network. They have worked to migrate parts of D3 to the new structure, but it is clunky. Trying to mash together old tech and new tech tends to be that way. Whatever they did to the Bnet infrastructure on Tues, is not playing well with the social features of D3 anymore.

Chances of it being simple are low. Chances of the people who made the old D3 code, or even migrated it to work with Bnet, still being around are low.

I don’t expect a fast fix to be honest. They still have not fixed the missing recent players list bug from December.

They actually do care, and don’t want us to suffer. It is kind of silly to think they would be that malicious. It is just that it is not a simple fix.

What I do feel they need to do is provide some more communications about it. Even if that communication says they are still working on finding the source of the issue. If this was just a diablo thing that would be easier, but it is the Bnet client that serves all the games that they changed.


#81

I started both a bug report and a TS thread as soon as I discovered no one else had.
We are coming up on almost a week now and somehow this passed QA :frowning:When will we get our fix, this is ridiculous and defending this process isn’t helpful.
We just want to play D3.


#82

You know I don’t have an answer for that. Further, explaining what is going on is not “defending” it.

Nobody likes bugs. Nobody. That does not mean everything has an instant fix though.


#83

Diablo 3 was not changed so there is nothing to roll back. The Bnet infrastructure that controls login, communications, etc. was changed. That impacts all game. Some of the older games have more issues, such as D3, because it was created before the modern Bnet infrastructure.


#84

I understand Cheetah


#85

can fix it by kicking and reinviting the member but so many other bugs. some we cant fix.


#86

ok then that should be rolled backed.


#87

I assume this counts as a bug.

My game options constantly reset the advanced tool tips setting. It’s happened at least a dozen times in the last week. I can only get rid of the advanced tool tips by resetting it, shutting the game down entirely, and then restarting D3.

I know it’s not me because it just did it. All I did was change from Grifts to rifts, and boom…there it was. It makes the game unplayable with the info for all those items constantly covering the screen. It started just after the latest patch/update.


#88

I’m still experiencing the inability to chat in clan. Private party chat is still messed up as my chat isn’t seen by others and others can’t see my chat. The ability to invite or be invited to private parties is also not functioning.


#89

Hey if you just fix the apparent issue this game has with time that should fix most of the faults. Pst me if you want to know more


#90

How do you expect us to play future games when you can’t even take care of this one properly?


#91

This kind of problem worries me about D3 future, so if the game code is old and has a lot of problems when interactions updates are made to Bnet structure, I imagine that they do not have promising news (expansion. new heroes, etc) to D3.
So, if it is so hard to maintain an old coded game to new updates, the only thing that could maintain the franchise is a continuation (Diablo 4 ?) I personally do not have any hopes for that, and it is sad, cause it is a game that I care too much.