Not the best example considering the assets were remade at least 3 times over the years, subsequently dropped, then picked up by another company, slapped together and recoded again in just a few months.oplinger said:Yeah! just like that duke nukem forever crap! Rushed as all hell! And look what happened.Sylveria said:Shitty, rushed game made by soulless corporate drones who have no concern about the quality of the game they make or consumer satisfaction is shitty.
Agreed, this seems to be an all too common logic when defending a company fucking up. I remember when I pointed out that everyone I know who owns a 360, including myself, has had to replace it at least once, I was met with a deluge of replies saying 'nuh uh mine works fine it's obviously your problem!'AzrealMaximillion said:I love how the argument here is this:
Person A says, "I got screwed the the majority of other players trying to simply play this game, this is horrible customer service"
Person B says, "I played the game with ease so Blizzard obviously did nothing wrong and everyone who's complaining needs to shut up."
Person B's argument is laughable.
It's really some sad for of Buyer's Remorse where people who weren't affected are shielding Blizzard like they were part of some "rapture".rob_simple said:Agreed, this seems to be an all too common logic when defending a company fucking up. I remember when I pointed out that everyone I know who owns a 360, including myself, has had to replace it at least once, I was met with a deluge of replies saying 'nuh uh mine works fine it's obviously your problem!'AzrealMaximillion said:I love how the argument here is this:
Person A says, "I got screwed the the majority of other players trying to simply play this game, this is horrible customer service"
Person B says, "I played the game with ease so Blizzard obviously did nothing wrong and everyone who's complaining needs to shut up."
Person B's argument is laughable.
If the number of people experiencing a problem is great enough to make it newsworthy, then it's the manufacturer that has dropped the ball, not the user.
They shouldn't have had this IN game if it was going to require such drastically inconvenient measures.Ickabod said:The online only isn't to fight pirates in this case, it's to secure the RMAH, their new revenue source.
And in order for that business model to work, they can't allow any off-line play, not even play separate from the AH, because then a large group of people would forgo using the AH and thus reducing Blizzards potential revenue.
If the RMAH works, expect to see A LOT more of it in other games.
You both are speaking words. Words with wisdom inside of them.rob_simple said:Agreed, this seems to be an all too common logic when defending a company fucking up. I remember when I pointed out that everyone I know who owns a 360, including myself, has had to replace it at least once, I was met with a deluge of replies saying 'nuh uh mine works fine it's obviously your problem!'AzrealMaximillion said:I love how the argument here is this:
Person A says, "I got screwed the the majority of other players trying to simply play this game, this is horrible customer service"
Person B says, "I played the game with ease so Blizzard obviously did nothing wrong and everyone who's complaining needs to shut up."
Person B's argument is laughable.
If the number of people experiencing a problem is great enough to make it newsworthy, then it's the manufacturer that has dropped the ball, not the user.
Really? Sounds to me like they delivered many times over on that.CriticKitten said:Considering one of their big selling points was that Diablo 3 would have vastly improved PvP over Diablo 2, yet is releasing with NO PvP, that sounds like a rushed game to me.
Yep. Wasn't my copy, though.Abedeus said:Did you play the game?
The game, as we see it today, took about a year and a half of total development time. 2008-2010 development was scrapped whole when they realized they were using a non-proprietary engine.Then shut up and don't say it's shitty without having played it. Rushed? It took 10 years to release, and was announced in... 2008 or 2009? That's not rushed.
I remember another game that was unplayable for weeks after it's launch. It' a pretty popular game now, though. You might have heard of it. It was called wow or something.I remember problems Half Life 2 had after release. Game was unplayable not for the first few hours, like D3, but DAYS.
tee hee.Ympulse said:I remember another game that was unplayable for weeks after it's launch. It' a pretty popular game now, though. You might have heard of it. It was called wow or something.
It is together, has been togheter since like 4 hours after launch except 1 maintenance of 30 mins the launch day and 1 server restart yesterday.Innegativeion said:God I'm so glad I chose to withhold getting this until Blizz gets their shit together.
And lols were had by all.Sylveria said:Shitty, rushed game