Latest Microsoft Bandwagon Lawsuit: Halo 3 is Defective

Information Week is reporting that a San Diego resident is suing Microsoft and Bungie because Halo 3 "consistently causes the Xbox 360 to crash, freeze, or lock up while the game is being played." I have a number of problems with this allegation and this suit. First and foremost, if Halo 3 were truly "defective" or caused the problems alleged, it seems reasonable to assume that message boards and blogs alike would have been exploding with those types of complaints since October. I dare say it might have broken the internet due to the volume of vocal complaints. However, this is the first time I have seen any such allegation, between the Rooster Teeth forums, Bungie forums, and Xbox.com forums or anywhere on the gaming blog circuit. The suit states: "Although faced with repeated and mounting consumer complaints and inquiries concerning this operational flaw in Halo 3, the defendants have failed to recall Halo 3 or otherwise remedy its failure to function on the Xbox 360." I would love to see a full version of the complaint and/or the "mounting consumer complaints" that are being referenced therein.

This brings me to the second issue. What the plaintiff is describing sounds far more like the well publicized problem with the Xbox 360 console rather than any problem with the game. And if that is the case, then the plaintiff should be taking advantage of the warranty repair process rather than filing a lawsuit. Which brings me to the third and final point, that given the available evidence, this seems like a rather simplistic attempt to profit from the game that set the new single day sales record. I have no problem with using the legal system to remedy actual problems, but at first glance, this suit seems like it's either misplaced blame or a shot in the dark. Once the pleadings make their way onto the internet in full, hopefully some more light will be shed on this case.


[Via Joystiq]

0 comentarios:

Publicar un comentario

. . . . . . . . . . . . . . . . . . . . . . .