06-04-2003, 07:22 PM
...or, at least, what is evidently becoming popular belief, "testing a new patch" would in no way affect your client program, at least for non-Diablo II clients. Diablo II is the ONLY Blizzard game to employ a server-side architecture. All other games are strictly peer-to-peer; Battle.Net just acts as a bridge between the clients, and as a central hub (hence the chatrooms). The ONLY way for an upcoming patch, for ANY game (barring D2), to affect you is if it forced you to download one. Which, of course, you WOULD be prompted for.
A more accurate estimation would be that they are working on the Battle.Net server architecture / code, and it is in turn causing problems for clients attempting to connect / play games. It has nothing to do with the end client, but rather the Battle.Net servers.
I do not know if you follow Diablo II news, but Diablo II's 1.10 patch is supposed to introduce some changes to Battle.Net, particularly in the form of anti-cheat measures. In conjunction with this, they may be altering the Battle.Net code and/or server architecture (more likely the former, as I doubt hardware changes have anything to do with these problems). This is not counting the added Battle.Net features of the upcoming Warcraft III expansion: namely, Tournaments. It could be any number of these, or it could be something else entirely. I surely can't say. These are just guesses as to possible reasons behind the cropping of errors. However, as has been said, it is completely a Battle.Net issue, and as such, you'll just have to wait it out.
Curiously, I wonder if Diablo II is affected by this...
A more accurate estimation would be that they are working on the Battle.Net server architecture / code, and it is in turn causing problems for clients attempting to connect / play games. It has nothing to do with the end client, but rather the Battle.Net servers.
I do not know if you follow Diablo II news, but Diablo II's 1.10 patch is supposed to introduce some changes to Battle.Net, particularly in the form of anti-cheat measures. In conjunction with this, they may be altering the Battle.Net code and/or server architecture (more likely the former, as I doubt hardware changes have anything to do with these problems). This is not counting the added Battle.Net features of the upcoming Warcraft III expansion: namely, Tournaments. It could be any number of these, or it could be something else entirely. I surely can't say. These are just guesses as to possible reasons behind the cropping of errors. However, as has been said, it is completely a Battle.Net issue, and as such, you'll just have to wait it out.
Curiously, I wonder if Diablo II is affected by this...
Roland *The Gunslinger*