Blizzard's Uncertain Future Probed 45
Thanks to the Seattle Times for their story discussing the 'cloud of uncertainty' over Blizzard's future, following the stalled sale of Vivendi Universal's games division. Blizzard's president Mike Morhaime says that "...we don't even know if we're part of the assets being sold. We're used to having more control over our destiny, and now we're just waiting", echoing the sentiments of four key Blizzard staff who took things further by quitting the famed developer a couple of months back. But since Blizzard's "...three franchises - 96 percent of whose fans are male - have sold more than 34 million copies worldwide", there's a great deal to be gained if the right buyer can be lined up swiftly enough.
Sierra (Score:5, Informative)
What happened to them AFAIK was pretty much the same. - Key developers (Al Lowe [allowe.com], Roberta Williams [backspin.org], etc.) from Sierra left the company (or put on crappy games).
The death of Sierra as a game-developer pretty much meant the end of adventure games as a mainstream-genre... It's hard to think of the same happening to the RTS (Real Time Strategy) genre, but then again if someone told me X years ago, that the adventuregames genre would be dead now, I would have laughed.
Re:Sierra (Score:4, Insightful)
But I agree, not having amazing releases like Liesure Suit Larry really is a shame.
Re:Sierra (Score:5, Insightful)
Valve is the developer of Half-Life, and they have very much been working on methods for self-publishing their titles (ie Steam).
Furthermore, whenever Sierra has had full control over a development house, they've had a nasty tendency to run it into the ground shortly after a major release, or even push it into that release before it was ready and then run the studio into the ground. Luckily, Sierra has no control over Valve except to delay release of retail packages and patches when they fail QA.
Re:Sierra (Score:2)
I miss good games like that
Sierra is just stupid (Score:1)
Re:Sierra is just stupid (Score:4, Insightful)
Why they canned the DreamCast version I don't know, but the storyline was released as Blue Shift, iirc.
Sierra's never had any control over Valve except in the QA process for titles Sierra is contracted to publish. In other words, Sierra can force Valve to fix bugs before releasing a title to retail or releasing a patch, but they can't force them to ship a title. Otherwise, we would've had Half-Life at least a year earlier and TF2 a long time ago.
Re:Sierra is just stupid (Score:2)
Not to point out the obvious, but maybe they should reverse the byte order next time they share network data between PCs and Macs
Re:Sierra is just stupid (Score:1)
The only people that really know are Valve and the company that was porting it to the Mac. Either way, Sierra only knows what Valve told them, more than likely.
Re:Sierra is just stupid (Score:1)
However, at the time a lot of patches were being released for the PC version, many of which broke networking compatability with each other. Naturally that means they would also break compatability with the Mac version until a patch was released for that too, but neither Valve nor Sierra wanted to take on the responsi
Re:Sierra is just stupid (Score:1)
Re:Sierra (Score:1)
Re:Sierra (Score:2)
Re:What about Valve? (Score:4, Interesting)
A Vivendi subsidiary would never have been allowed to delay their first title for nearly 2 years. The only reason Blizzard gets away with that kind of crap is because they have a track record of horrible predictions for release dates, but solid releases.
Release Dates (Score:1)
The elasticity that release dates have gained is not what bugs me. What bugs me is that developers feel the need to release incomplete products to store shelves. I understand that sometimes a patch is necessary, but for the love of Baal, how many patches did Diablo 2 eventually see?
Re:Release Dates (Score:1, Insightful)
Re:Release Dates (Score:3, Informative)
The 'balancing' changes are, in themselves, a sign of the poor testing done on the game, though, for the most part, I'd say the game shipped mostly good (except for the Direct3D support).
Re:Release Dates (Score:2, Insightful)
This article discusses Blizzard, and yet the biggest names they cite to leave Blizzard were part of Blizzard North (Diablo fame). There's several games and companies unde
Re:Release Dates (Score:2, Informative)
You're right, except for one thing: Blizzard did an extremely limited beta test for Diablo 2 which was only meant to test battle.net. They ignored gameplay and hardware i
Re:Release Dates (Score:2)
You are referring to the Public Battle.Net Stress Test. That was a public beta, sure enough, but it wasn't the only beta, of course. Rest assured, they beta-tested all other aspects of the game in-house. Now whether they tested it properly or as much as they should have is another matter, but I'm fairly certain they put as much effort and resources into it as other developers/
Re:Release Dates (Score:1)
Re:Release Dates (Score:2)
Blizzard released a patch immediately as soon as they caught it and even people that bought it the first day actually have 1.03, NOT 1.0.
Re:Release Dates (Score:2, Interesting)
9 or 10 patches in a couple years isn't too bad. They did have some major problems that had to be fixed, but they used a lot more of those patches for gameplay and hack fixes than anything else (the D3D support had a couple of minor fixes and then a major fix around the time of the expansion release, which also included a major overhaul of the gameplay in terms of skill trees and diffi
Re:What about Valve? (Score:1)
I used to work for VU on the games side before and during the 'merger'. People went over two years alright. I can't say for sure that it happened on a first title but it definitely happened. When we visited one particular developer's office (nameless naturally) all they'd really achieved in two years was a 12 page promotional booklet and a pathetic amount of research. Although the reverse of the wallchart
Re:What about Valve? (Score:1)
I'm sure it does happen quite a bit, but first titles would normally be removed from that particular developer or the developer would be reshuffled (ie the name stay the same but the people change), assuming the title isn't just canned.
When we visited one particular developer's office (nameless naturally) all they'd
Vivendi (Blizzards parent co.) Merges With NBC (Score:2, Informative)
http://story.news.yahoo.com/news?tmpl=story&cid
Re:Vivendi (Blizzards parent co.) Merges With NBC (Score:1, Informative)
"Blizzard is a part of Vivendi Universal Games which is a different group. Unless you see something that specifically mentions them, it doesn't really apply to Blizzard."
http://www.battle.net/forums/war3/thread.aspx?F
Re:Vivendi (Blizzards parent co.) Merges With NBC (Score:2)
You said that like you mean it...when did Blizzard put out 'quality games'?
Obligitory Penny-Arcade link (Score:3, Funny)
Doesn't hurt my feelings if they disappear. (Score:5, Interesting)
Then Blizzard gets their panties bunched in a knot because someone starts making a pretty cool UT mod with StarCraft characters. They put the smack down on them, and oh while we're at it we'll put the smack down on BNETd to.
To top it off, I had by that time pretty much stopped playing Blizzard games. You see, during the time period I migrated slowly over to Linux until finally I no longer wasted drive space on a Windows partition. I could make Blizzard games run with Wine, but it was never quite like it should be. Heck, all my other favorite games like UT, Descent, Quake 3, later on UT2K3 and quite a few others I just wont bother ratteling off ran great and NATIVELY on Linux. Blizzard was the only game publisher I gave a shit about that fully shunned Linux in all ways. I simply placed them on the not give a shit about list. They'll stay there until they start supporting Linux and offer an apology to the maker of BNETd. Giving him a job or something would make a great apology in my eyes, but just admiting they should have said something earlier or not laid the smack down so hard out of the blue would be enough for me.
When Blizzards gone I'll miss them about as much as I'll as miss Britney Spears when she runs out of steam, which will be about the same amount as I've missed N'Sync. None.
Die Blizzard. You haven't done what you need as a game company to keep an audiance. Sometimes kickass games isn't enough. Lay down your 2x4, your OS blinders, and your attitude and you'll be right next to Atari/Infogrames in my book again.
Re:Doesn't hurt my feelings if they disappear. (Score:3, Insightful)
I hope you're not holding your breath.
-etone-
Blizzard is not so "right" as you suggest (Score:3, Interesting)
In neither of those cases did they really have a leg to stand on. But the small developer communities had no income from their product and therefore couldn't justify spending much money to defend it, much less the amount that would be required to take on Blizzard/Vivendi Universal. So they folded, and Blizzard wins.
Blizzard may have been de
Re:Doesn't hurt my feelings if they disappear. (Score:2)
I'm not mad at them for defending their IP rights. It's theirs and they can defend them. What caused me to get mad at them was the fact they turned a blin
Re:Doesn't hurt my feelings if they disappear. (Score:2)
Starcraft, more of the same with a different story and look (Not to mention the story sucked more then a Mark Hamilton movie in the last 15 years).
Once Blizzard started pushing their obese, bloated weight around and suing movie studios for naming a movie about a Mexican drug lord "Diablo" things start
Re:Doesn't hurt my feelings if they disappear. (Score:1)
Re:Doesn't hurt my feelings if they disappear. (Score:1)
Seriously! (Score:1)
Dont look at me my ebay rating isn't THAT good to be trusted with 800 mil...