Not only communication but action, it is that issues are being addressed and solutions are being delivered in clear view.
Well, Matthew C. It looks like Diablo Classic Team needs to rewrite the D3 group code to fix this Bnet Services problem.
Thank you for the extra communication. This is better than it has been since day one of vanilla. It is very refreshing to see you posting. Thanks again!!!
Not True at All!
Blizzard had regular Tavern Talks where we learned alot about the game and what was coming.
During the first 4 years or so of Diablo III there was a lot of communication.
That all stopped 3 years ago or so, when the ppl sitting in board rooms that know not much about anything declared D3 a mistake.
Are you still planning an update for today?
The goal is for today, yes. We don’t want to give a specific time, but we’ll communicate patch notes and get it out soon.
I sure do hope it fixes it man… been very annoying since it ever popped up for most of us!
Did the update.
Guess I have to wait for everyone else online to do the same!
A few in clan have updated yet HC still shows as NS SC.
Patch notes are out / only for the season exploit / nothing listed from the group bugging or displaying non - season and season… Some more waiting I guess.
Just want to clarify the patch notes. The 2.6.7b Patch will not fix the Seasonal/Non-Seasonal Group Bug. We’re still having that in testing today and will have an update very soon.
Ty Matthew for that quick response. Its next leveling of communication. Big respect - keep up the good work!
That is unfortunate;
I mean this in the way that I was hoping the patch would help the issue while at the same time understanding its a complex issue that can’t be solved with a simple click of a mouse.
I am hopeful, not hateful.
Same feeling here.
The rush to fix something only one person or a dozen are guilty of and not hurrying the fix for group bug play is sad indeed.
Blizzard needs to know what are priorities and what are not as important.
!? Really? They have been trying to fix the grouping bug for weeks and giving updates frequently. Several fixes were tried, and did not work. They hoped to have another try at fix today, a fix that has been in the works for days. Maybe, just maybe, it is NOT easy to fix?
Saying the only reason they don’t have this fixed is because it is not a “priority” is really really short sighted and disingenuous in my opinion. You can WANT something and prioritize it all you want, does not make it happen any faster. I am sure you have life experience with that. How many times have you really really wanted something done but it just plain takes time and work?
lol, if Eggman had not done the solo 150 trick this past week then there would have been no patch for that!
It has taken over two months to fix the group bug problem.
It has taken them over a month to even begin to understand that this bug from Bnet Services had ruined group play.
MissCheetah, I know you feel this group bug is a minor issue because you don’t play D3 at all in the past few years.
You have no experience with this bug in group play.
The past two seasons have been ruined by this group play inability!
I have stated this very clearly, and I wish you knew how bad this bug is personally.
A number of people have stopped playing because this group bug has ruined the game.
Anyone that only plays solo will see little and have no effect from this group bug.
It has been 3 months, actually. We knew from the start that it was due to the Bnet update that was done, or at least I did and it was stated on the forums a few times.
You are right! I don’t do group play. Pretty much ever. Just because something does not impact me does not mean I think it is MINOR though. It sure as heck is not. Group play is a core aspect of D3 gameplay and something Blizz does prioritize. Believe this or not, I want good things for other people in all aspects of life. That is why I have spent my time here, for at least 7 years now, mostly helping answer Tech and CS questions. I get nothing from that. It is not about me. It is about players being able to play the game, or understand it at least.
My point is that they have been trying fix after fix after fix for this. They have been really really good about communication on it, especially lately. It IS a priority. IF they could have fixed it already they would have.
Don’t slam Blizz for fixing a critical bug (maybe easy fix?) because the Bnet and Diablo3/Classic team have not fixed another important, but stubborn, bug.
This bug is NOT an easy fix.
That much is very clear.
This bug is about an old legacy C++ coded game that was blindsided by the Bnet Services updates.
I have no doubt there is some serious political problems in house about Blizzard Classic games talking with Bnet Services to fix this group play bug that has ruined the game.
The programmers are working in the wrong area to make this work.
Like Matthew C. said in another post about it may require a rewritten D3 code patch that will take programmers they most likely let go or quit in the last year to complete.
Getting legacy software/hardware to work seamlessly with new product is a challenge.
I am fully aware of the nuances of this type of work.
I understand this group fix will not be easy and most likely will be very expensive as well.
Now we mostly agree.
The only thing I even slightly disagree with is about team relations. I don’t think there are political issues between the Bnet team and the Classic team though. Blizz teams work really well together if mgt allows and funding is there.
The rest of your post is fantastic. Thank you.
I’ve worked with companies where legacy systems and current money making systems under same roof are in different worlds.
I imagined what would have happened when a Diablo Classic team member stopped a Bnet Services guy in hall and said, “Hey, we’ve found a bug from your maintenance that is impacting group play with D3!”
At this point the Bnet Services red faced guy has steam rising from his head and things don’t go well from here.
I know that Bnet Services is not going to change their code.
And I know that little patches here and there will not fix the bug.
So the middle way around this is to rewrite the actual D3 code to accept input proper from Bnet Services and give output back to Bnet Services proper.
When this happens finally, D3 will be a happy game once again!
Nah, they have a structured process. While sometimes hall conversations do make wheels turn, this is a bit big for something like that!
I really don’t think so. I have spent time there. Distinct lack of steaming heads running around. I have met with a lot of folks from many teams. I am impressed by how personable they are, open, and professional. I really don’t think anyone would get angry about a bug. Concerned, sure, angry, nah.
Probably true. I suspect Bnet would change it if it did not impact the other games and other features. Which yeah, puts it back on the Classic team to fix D3…which has very old code.