I do understand your point on what you said. Personally, I don’t mind the game to be online only. However, that kind of issue we are encountering wouldn’t have happened if this game wouldn’t be online only. Of course, we all know that Diablo 3 will remain online only until the end of it’s life cycle. I would say that error occured in the past and it has been resolved by Blizzard so why is this happening again so I don’t get it.
You can read that thread via this link. Error Code 395002 Can't Load Hero List - #25 by Maskraider-3992
Moreover, that’s even an argument that proves that this issue should be fixed sooner than later because this happened in the past anyway so unless that they don’t know how to save past troubleshooting tickets, it’s reasonable to think that they should solve this really soon.
That’s not specifically true, it depends on what’s causing this issue. If the cause is the same as the post you linked then yes, it should be trivial to resolve, if there’s a brand new cause for the issue this time they’ll have to spend time investigating what caused it and how to fix it.
Error messages and codes are somewhat generic, there are multiple things that can cause them so getting the same error multiple times doesn’t specifically mean the cause is the same.
It could also just be a server hic-up and could fix itself by tomorrow
You just said it right there. If it’s a different issue then why not informing us about it and we can’t presume that it’s a different issue and we can’t presume that it’s the same issue. It sounds like to be the same issue 395002 error code but maybe not. So at the end of the day we don’t know what’s going on and that proves my point that we should be informed and have a time frame to know what’s going on with step to step resolution or something but being vague and not replying at all doesn’t help much either. As I said earlier, it’s nothing against you, it’s not related to me or you. It’s ONLY related to Blizzard to solve that issue that lasts longer and longer. The thing is like if that issue remains longer and longer overtime that will prove way more my points/arguments I said since the beginning of this issue that happened several hours ago. I also have to say that the majority of the playerbase can still play the game without that issue on North american servers. It seems that a small minority of the playerbase that is currently affected by that. However, even if we are a minority of the playerbase affected by that, it doesn’t mean that it’s fine to fix it slower than quicker. That explains why it would be just pure logic to tell us what’s going on. Thank you for your reply.
This is where you’re being unrealistic. First of all it only seems to be happening to a couple of people (Which means it’s going to be lower priority). Secondly like I said the support for D3 is limited (I expect the CM’s they have managing these forums manage many many older game forums so it’s likely they didn’t even see this issue today). I wouldn’t be surprised if they only look at this forum once or twice a day to be honest (and despite what you think or believe, that’s a reasonable level of support for a game this old).
I also expect they might even get us to try a few other solutions on our end before raising this to the developers to investigate. I also expect them to at least respond to one of these threads once they’ve seen them.
Yes you’ve made it clear they aren’t working as fast or providing enough bug report coverage for your liking but this is the reality of the situation and while you don’t think it’s sufficient, I do.
If this issue doesn’t resolve itself or get some response within 24 hours I will have a change of opinion however
The problem is that we don’t have any proofs about how many players are affected by this. We just presume that it’s a minority of the playerbase and it’s probably the case. The thing is like it might be 500 players, 200 players, 100 players. We don’t know because we don’t have access to that information anyway because we aren’t informed about anything from Blizzard. As that being said, my point is that I have paid for the game and moneywise I’m truly right that the argument of saying that it’s a 10 year old video game isn’t enough for me. They have a twitter account and they could have informed us right there because Blizzard is usually using his twitter account to inform us about seasonal start and end dates. Same thing happens for DDOS attacks too so why not informing us about what’s going on right now about 395002 error code. You think it’s normal for a multi billion dollar company to not having a technical support phone number to call to resolve issues for specific accounts or at least to provide a live chat support as a minimum as an example? You think it’s reasonable? Many online based companies that don’t provide technical/customer service by phone do at least prove live chat assistance. That doesn’t make sense to me at all. So the explanations/arguments about seeing or not these forums posts by Blizzard shouldn’t apply because they would know how to inform us in many ways anyway.
So as you said if this issue isn’t resolved in 24 hours you will have to change your opinion about this whole situation. I have this issue since 11:00 AM East standard time and I’ve sent a ticket to Blizzard at noon (12:00 PM) East standard time. So there’s not much left for Blizzard to react now. We’ll see really soon what’s gonna happen about this whole issue.
Based on that following thread https://us.forums.blizzard.com/en/d3/t/error-loading-the-hero-code-395002/54458
We can see that a guy posted that issue about 7 days ago so Blizzard is already aware about that by the fact that this guy also sent a ticket at Blizzard 7 days ago as well based on what he said and nothing happened since then because the issue is still persisting at this day. I guess that it’s still not enough to make that a priority? What are the requirements for an issue to get resolved quicker? How many days of downtime does it take to justify being able to ask to fix this issue?
By the way, if you read that thread from Darth Raven, you will see that he posted that 395002 error code 7 days ago so Blizzard was already acknowledged about that issue anyway. Even at this day, we still don’t know what’s going on with this. It seems that different players is getter that issue at different times and it may be because we don’t create new characters at the same time. That issue happened to me as soon as I was in the process to create a new seasonal Witch Doctor character. So it seems that my point needs to be considered seriously in that whole discussion. Thank you!
If you look through, there are years they have had this issue. I have seen articles that are over 2 years old about this issue. For me, I get my fix on the European server currently. Hopefully today they will have the issue resolved. I also made a ticket. I think everyone with the issue should make a ticket to help bring attention to the issue.
I’m experiencing this error as well. I’ve run through all the basic troubleshooting steps. A response from Blizzard would be nice, at least some acknowledgement that they’re aware of the issue, no matter how small a subset of users it’s impacting, and working on a resolution.
Is that mandatory to follow your instructions at that level? I mean you are at the same level as me so no need to ask people to have specific behaviors just to please you. I have nothing against you personally and you sound like as if you are a Blizzard community manager or something like that trying to defend Blizzard at all costs. If your only argument is to label me as I’m a spammer then i find that really a poor argument to be honest. Moreover, it sounds like that complaining is really bad for you and you sound like if you are trying to make me feel bad about it as you’ve just mentionned that there’s a difference between “complain” and “complain*”. In fact, the difference is by 1 star sign.
