Not really, people don't know what is causing the problems and since there generally isn't anything you can do about it (the ISPs and datacenters are already aware of the issue) people are just looking for scapegoats. The thing is: the server isn't the same thing as the code. People blame the servers but the game client and lag resulting from inefficient code has almost nothing to do with the servers themselves. Bugs are CODE related, lag in mob density is CODE related, and in the case of the latter it can also be related to your system not being powerful enough to handle the inefficient client. But again...that has nothing to do with the servers.
If it really was ISP related, there would be way more complaining to the ISP companies. Just think of the millions upon millions of connections going thru the routes. If the ISP's route starts lagging this frequently it would even get on the news, like when facebook was working slower than expected. The server code can be shit too, there's always computer related stuff where bugs come out of nowhere as well. I remember having an old laptop that could play cs 1.6, but even firefox or IE wouldn't work on it.
Server problems would be GLOBAL. As in EVERY SINGLE PLAYER would be having the issue, not some or most. Players don't have the information or the knowledge to make assessments about server problems, they are making bad assumptions and placing blame that typically isn't warranted.
If you read my posts then you would know that I pretty clearly stated that it is typically ISP, code or client-side issues. It could be a problem that only affects users below a certain threshold of PC performance, it could be users on a certain path to the servers or it could be game-client related. Again, with Diablo specifically there aren't the same challenges impacting larger games like WoW because the servers are load balanced and can't be overloaded by the choice of the players.
That doesn't mean there can't be performance issues, it means that performance issues are going to be related to the game-client optimization or code and not the servers themselves. A server client that wasn't stable and had the kind of issues people "think" they have would never be able to handle the numbers that Blizzard services at all. It would be universal and Blizzard would be acknowledging the problem and working publicly to resolve it.
Again, that's game-client or client-side issues. It could also be that players in certain regions are all going through a backbone or node that isn't robust enough to handle prime-time traffic, that's no different than when you have a cable modem and live in an apartment complex or a dorm where the bandwidth the users are demanding exceeds what is available. I used to get lag every night between 3pm and 10pm because my ISP had too many people on a single node in my area and everyone else streaming netflix would lag me. That had nothing to do with Blizzard or their servers, that's ISP related.
It doesn't matter what Internet plan you pay for if part of the backbone you go through to get to the servers has problems. That has nothing to do with the servers, it isn't a server problem and it isn't server lag. To the poster above: you're talking about a game client issue, not the servers. It has nothing to do with the servers, it's the fact the code hasn't been optimized and your computer can't run it smoothly because the client sucks. Again: not a server problem and it's not really "lag" how people mean when they say it. Yes, your game is lagging, but it's not server side.
Im telling you, I know how these servers work and if it was server issues EVERYONE would be having the same problem. Since that isn't true it isn't server side, period. No matter how many times/ways you say it you're wrong. I'm sorry, I just get sick of people not understanding what impacts game performance and attributing performance issues to "server issues" when 99% of the time it's client side, ISP or code related.
>massive EP lags in large mob density every evening
>Latency high as ****
>Whole grp from different countries, everyone lags
>its getting "late", like 10pm
>its our ISP, dudes 8-)
At this point it's pretty clear none of you work in IT, or if you do it isn't in software development or server adminstration. I *do* work in IT and I deal with full-stack development issues on a daily basis, so I'm pretty familiar with how this stuff works. I don't work on projects the size of Blizzard games, but I know enough that I can confidently say that except for a couple incidents the issues people complain about are not server problems.
You can deny it all you want, but I'm right and anyone that is similarly knowledgeable/informed will agree with me.
Also, HC has been "dead" or "dying" according to some people for YEARS, and yet tons of people still play it. DC deaths have ALWAYS been a part of Diablo 3, if you don't like it or can't handle it - don't play hardcore. Play SC and use the honor system by deleting your characters when you die, it's YOUR choice to play HC.
I, and many other people have had no problems at all. I've been playing a lot, both during prime times and off-hours and the servers have been rock solid. The only thing I've noticed at all is a little bit of occasional client lag when using a WW build in high mob density, but it isn't "lag" it's just their game client and consequences of recent patch code not being optimized.