I agree with the above posters, in that having a TCP/IP Connection system for Diablo 3 and/or StarCraft 2, while not vital, will drastically improve the games longevity, and playability. I do not want to have to put up with bots and spammers on closed realms just so I can play a game with my brother, or my friends when they come over. (Yes, we still throw LAN partys, including Warcraft 3 and Diablo 2) I really do have high hopes for the games that you have slated for release in the next few years, and it would be a shame if the only reason I wound up not playing them as much as I would (Note, I'll still play them cuz I'm a Blizz-ho, I've got all of your games, XD, and sorry if that term is found offensive.) is because I can't play with my family/friends because the server is down.
This is not even mentioning the mod community, which, though it has suffered a couple hits here and there, is still alive and kicking. The inability to play a mod with other people will inevitably lead to a few things, including, but not limited to:
1) A slow death of the mod community.
2) The loss of many new ideas that "freelance" coders/modders may come up with, including fixes to bugs that may or may not be obvious to the coders/programers that made the game. Ever heard of somebody proofreading a document? It's the same theory, that you may miss mistakes that others catch because you are the one that made them, no offense intended at all.
3) Hackers/pirates (The ones you're trying to stop by eliminating LAN, I assume.) creating their own workarounds, not that I agree with them but I'm just stating that it will probably happen, and that would thus defeat the purpose of having no LAN/TCP/IP support, and in the end only dump on those that are loyal customers/fans.
I sincerely hope that the higher-ups take note of this, and that something can be done to reach a mutual agreement between the community and the company, as this is a serious issue and should be addressed as such.
Your fan,
Roy (LordFryz, Battle.Net USEast Ladder)
|
|
