World of Warcraft exploit slays cities
World of Warcraft cities across several servers were turned into tombs over the weekend as naughty hackers with insta-kill powers ran amok, slaying players and NPCs alike. One claims the hack has been used for almost a month against monsters, but Blizzard recently detected it so they decided to go out with a bang. The hole has been hastily fixed.
World of Warcraft cities across several servers were turned into tombs over the weekend as naughty level 1 hackers with insta-kill powers ran amok, slaying players and NPCs alike. One claims the hack has been used for almost a month against monsters, but Blizzard recently detected it so they decided to go out with a bang. The hole has been hastily fixed.
"Earlier today, certain realms were affected by an in-game exploit, resulting in the deaths of player characters and non-player characters in some of the major cities," Blizzard said yesterday. "This exploit has already been hotfixed, so it should not be repeatable."
YouTube user 'JaddMMOwned,' who uploaded a video purporting to show the same hack being used on NPC raid bosses, claims this wasn't an especially new hack:
We were using this for almost a month in Baradin Hold (9000g per hour seemed to be the most we could get out of this hack). It was going great for us, but unfortunately, the first ban was issued yesterday to a friend that was using the hack, so we figured it would be fixed in the near future and decided to pay a tribute to the server developer who slipped up for us.
Here's footage one player captured of the slaughter on the streets of Stormwind:
-
Alice O'Connor posted a new article, World of Warcraft exploit slays cities.
World of Warcraft cities across several servers were turned into tombs over the weekend as naughty hackers with insta-kill powers ran amok, slaying players and NPCs alike. One claims the hack has been used for almost a month against monsters, but Blizzard recently detected it so they decided to go out with a bang. The hole has been hastily fixed.-
-
I love when things go wrong like this in an MMO. I remember when that blood plague DOT could be carried from that one 40 main raid encounter back in vanilla (dont remember the boss, long time ago)back into the cities. That was so fucking hilarious. One dude goes to the AH, and within 5 minutes the ENTIRE SERVER POPULATION has a 1 DPS permanent DOT that prevents all healing or mana regen and cannot be cured and lasts until death.
The funniest thing was the "UGH!", "OW!" "URGHF!" grunts all through out the cities as the tiny 1 DPS dot ticked away at thousands of people standing at the bank/ah/windrider. That was so fucking hilarious.
Also, people kiting one of the dragons into Orgrimmar and watching as thousands of white knight hero level 4's and 5's try to be the one to get the killing blow, and are mercilessly obliterated by AOE attacks. -
Screen from the previous chatty thread: https://dl.dropbox.com/u/2650876/MMOwned/WoWScrnShot_100812_013502.jpg
-
-
Never fail to amaze me how people not in the field (or without the nessecary skills) have so many opinions on programming a computer game. You might just be young though, but let me break it down to you in hope that it's simple enough for you to comprehend:
* Programming is difficult.
* People make mistakes.
* Blizzard is full of people. -
Lord British got killed during beta because someone forgot to reset his invulnerability flag after a patch. This is an exploit for a very live and far more popular MMO that allows you to kill any target instantly. How could you possibly think that the two are you know what never mind I don't know why I'm even typing this jesus christ
-
-
-
-
-
Was the hack actually being used for around a month? Or is that what somebody said they had done? I find it hard to believe that no-one thought to report this kind of hack a month ago if it was being used back then, I could just as easily blame the players as well as the hackers for not solving the issue earlier if I decided to spin the story that way.
My point is blame the people that are causing the problem, not the company that will be forced to fix it.
-
-
-
-