News for hackers. Stuff that matters.
Re:Blizzard Calls DRM a "Losing Battle" by Groxx on Thursday May 27, 2010 @04:14PM (#1384817)
They may not abandon them completely, but they come pretty darned close. Diablo 2, for instance, still pegs my system pretty hard - 100% on a single core. Their display code apparently requires 256 color mode on startup, but not in-game, leading to the Mac launch problems a while back. It also lags occasionally on a single player or local network game and takes a second or two to catch up. And if you've ever tried allowing more than one person behind a NAT to connect to Battle.net, you'd realize just how little they've touched the older games, despite how much money they still get from them.

(For those interested:) The only way to allow more than one person to connect to Battle.net in the older games is to rewrite packets on your router (iptables or similar), because the games steadfastly refuse to communicate on any other ports, and don't even communicate error messages. They just fail to connect, as if the servers are down. How hard would it be to specify a launch parameter which sets which port you use? Even if it's not simple for the average user, a solution is better than none, and this has been an acknowledged problem for many years.

Re:Blizzard Calls DRM a "Losing Battle" by algorias on Thursday May 27, 2010 @07:19PM (#1385203)
Counterexample: Just last year a StarCraft patch (1.16 IIRC) came out which drops CPU usage from 100% to around 3%
Re:Blizzard Calls DRM a "Losing Battle" by Groxx on Thursday May 27, 2010 @11:39PM (#1385633)
Yeah, the latest round of patches was pretty big, and it's nice they keep doing it. But it's also kinda sad they didn't make some of the critical changes earlier / yet. I have a feeling a lot of the motivation behind the updates was to get people to buy them before SC2/D3 comes out.