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.
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.
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.
Blizzard never had any issue in any game concerning server lagg, right aithos?
It was always client side right?
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.
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
>lag disappears
>its our ISP, dudes 8-)
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.
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.
I can tell for a fact lag is worse now than ever before. I have been playing hc since d2 and never made another non hc char. I lost my char on Sunday due to rubber banding in gr55 solo. i have top of the line internet machine and routers. In fact when I was lagging my wife had no problems with the Internet and no she wasn't downloading anything crazing to choke my upload. Servers just are no good.
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.
WoW is a little different scenario than Diablo 3 because of the server structure, with WoW the players choose where they want to play and so Blizzard can't load balance properly. That's why they have login queues and sometimes offer free realm transfers, because the biggest realms are the most popular. What people don't realize is that each "server" isn't literally a server box, it's all virtual and a single box contains multiple realms.
So sometimes what happens is that when a big patch or expansion comes out the small realms flood and the extra performance the big realms typically have because the small realms have low numbers of concurrent connections is gone. That causes server lag and can mean DCs or even server crashes (world servers), more common is just that the code itself has bugs that cause problems though. WoW is a MUCH more complex engine and has a lot more moving parts, because of the number of connections to a single world it makes crashes a lot more likely when code isn't optimized.
Diablo, on the other hand - is server invisible. What I mean is that you don't choose a game server, you just connect. That means Blozzard can dynamically load balance, it makes stablilty INFINITELY better because no single server takes a greater portion of the concurrent connections. The only time they might have issues would be patch related or around a major rewrite (2.0) or expansion. It is definitely possible that 2.3 had some issues, but that's code related and not server related. As I said - server issues aren't really a thing with games, 9 times out of 10 it's your ISP.
Also, it doesn't matter if you're playing from different cities (or countries). The servers are located in one place per region, so in order for there to be an ISP issue all that has to happen is one piece of the backbone (like a router) to go out that you have in common to cause problems. ISPs share backbone,myli could have different ISPs in different cities in different countries, but you may still use part of the same path and if that part breaks it will cause you issues that others don't have.
I'm not sure why people still don't understand that having a "beast" computer and a high-tier internet plan doesn't mean that issues can't be on their side.
First of all: speed-test doesn't mean a thing, download speeds, upload speeds and ping to a server nearby you over less than a minute connection have virtually nothing to do with your connection to a game server that's probably *not* nearby you. Secondly, it's packet loss and instability that cause your connection to reset and it typically has nothing to do with either your connection speed or the game servers.
The thing you need to realize is this: the game servers don't typically have issues. They sit at a data-center and wait for information to come to them, the data-center has more than enough bandwidth to service the servers and server-side issues that aren't patch-related are INCREDIBLY rare. What happens more often is that part of an ISPs backbone will go out and cause people in certain area's or with certain ISPs to go down (ones in the path of the typical route to the servers).
In other words - it's your ISP. It doesn't matter if it's literally on your end (at your home) or a part of their backbone, it could even be another ISP that is leasing infrastructure to your ISP. The important thing is that it's not on Blizzards side. If it was "server issues" (which is flung around far too much) then EVERYONE would have the same problem, it wouldn't matter where they are located. There would be a technical support post detailing the issue and every forum would be absolutely flooded with posts about it.
Except that it's not on Blizzard's end. I've had no lag or DCs at all since the first few months of the original games launch, and a very short period of time around RoS when all the DDOS attacks directed at gaming companies (LoL especially) were happening. I don't get rubberbanding, I don't get disconnects, I have stellar ping and everything is super responsive.
So I suggest you get some packet loss logs and contact your ISP, that's where your problem is.
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.
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.
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.
WoW is a little different scenario than Diablo 3 because of the server structure, with WoW the players choose where they want to play and so Blizzard can't load balance properly. That's why they have login queues and sometimes offer free realm transfers, because the biggest realms are the most popular. What people don't realize is that each "server" isn't literally a server box, it's all virtual and a single box contains multiple realms.
So sometimes what happens is that when a big patch or expansion comes out the small realms flood and the extra performance the big realms typically have because the small realms have low numbers of concurrent connections is gone. That causes server lag and can mean DCs or even server crashes (world servers), more common is just that the code itself has bugs that cause problems though. WoW is a MUCH more complex engine and has a lot more moving parts, because of the number of connections to a single world it makes crashes a lot more likely when code isn't optimized.
Diablo, on the other hand - is server invisible. What I mean is that you don't choose a game server, you just connect. That means Blozzard can dynamically load balance, it makes stablilty INFINITELY better because no single server takes a greater portion of the concurrent connections. The only time they might have issues would be patch related or around a major rewrite (2.0) or expansion. It is definitely possible that 2.3 had some issues, but that's code related and not server related. As I said - server issues aren't really a thing with games, 9 times out of 10 it's your ISP.
Also, it doesn't matter if you're playing from different cities (or countries). The servers are located in one place per region, so in order for there to be an ISP issue all that has to happen is one piece of the backbone (like a router) to go out that you have in common to cause problems. ISPs share backbone,myli could have different ISPs in different cities in different countries, but you may still use part of the same path and if that part breaks it will cause you issues that others don't have.
It isn't "server problems".
I'm not sure why people still don't understand that having a "beast" computer and a high-tier internet plan doesn't mean that issues can't be on their side.
First of all: speed-test doesn't mean a thing, download speeds, upload speeds and ping to a server nearby you over less than a minute connection have virtually nothing to do with your connection to a game server that's probably *not* nearby you. Secondly, it's packet loss and instability that cause your connection to reset and it typically has nothing to do with either your connection speed or the game servers.
The thing you need to realize is this: the game servers don't typically have issues. They sit at a data-center and wait for information to come to them, the data-center has more than enough bandwidth to service the servers and server-side issues that aren't patch-related are INCREDIBLY rare. What happens more often is that part of an ISPs backbone will go out and cause people in certain area's or with certain ISPs to go down (ones in the path of the typical route to the servers).
In other words - it's your ISP. It doesn't matter if it's literally on your end (at your home) or a part of their backbone, it could even be another ISP that is leasing infrastructure to your ISP. The important thing is that it's not on Blizzards side. If it was "server issues" (which is flung around far too much) then EVERYONE would have the same problem, it wouldn't matter where they are located. There would be a technical support post detailing the issue and every forum would be absolutely flooded with posts about it.
Except that it's not on Blizzard's end. I've had no lag or DCs at all since the first few months of the original games launch, and a very short period of time around RoS when all the DDOS attacks directed at gaming companies (LoL especially) were happening. I don't get rubberbanding, I don't get disconnects, I have stellar ping and everything is super responsive.
So I suggest you get some packet loss logs and contact your ISP, that's where your problem is.