Well, if what you said was right, then that's no problem. Let's look at what's been done so far to our knowledge.
For the first 2-3 years, they had a skeleton crew coding the new engine. That's about standard, The unreal engine (which is SOLIDLY replicated) took 4 to my knowledge.
That leaves 4-5 years remaining, of which they worked on a scope that was different for the first chunk. About 2 years into that, a scope change radically shifted the project in terms of singleplayer involving the trilogy split. This would involve them having to start from scratch. At this point, they'd have to re-analyze a new way to handle battle.net as it would not have to encompass 3 games, not just one. This also provided an opportunity to re-evaluate how Diablo 3 worked in.
After that point, when looking at 4 games, why not look to the future. About the same time they realized they had to scrap what they had for a multiplayer backbone and move forward with something new. It was so large of a project it created a whole new software project and not just an implementation within SC2.
This means that about 4 years ago (Benefit of the doubt, worst case scenario), they had to restart the project essentially on terms of the slate, and see what previous information could fit in. For that reason, I'm not having much of an issue when you look at the big picture.. they're working with essentially a 4 year scale for 2 separate projects. Let's also understand that in the youth of the project, it had a skeleton crew and the company as a whole had fires that had to be put out. It's not like they had a fully functional staff working on the project from day 1. And no matter how long or little it takes, that's not an insult to the developers, that's an insult to the methodology of the company. They have a motto "When it's ready". This is what I feel you're mad at.. not the skill of the people creating the game. Please feel free to correct me if I'm wrong, it's only what I perceive after all.
Regarding those fires with WoW, btw. No matter how much passion a person has for a project, the company should always come first, especially one with a repuation that well. If WoW was fine and SC2/b.net infrastructure has issues on the first few weeks, I guarentee they would consider taking people off other staffs (Such as diablo 3 or WoW) to help assist with the debugging if it's a viable option. This isn't "WoW Entertainment" or "StarCraft Entertainment"... it's "Blizzard Entertainment" afterall. I know you know that after all our conversations regarding the matter.
Blazur, I've always suspected that the only reason that your "flawless perception" of Blizzard is reduced is highly influenced with a distaste for their other product, World of Warcraft. Nothing wrong with that, I can't change your emotions or opinions. But in terms of taking a long time to work on a game, nothing has changed in the company. The designers are still calling the shots, not the producers. And even when you admit that you know the games going to be ok but you disagree with them as a company... I speculate 3 days after beta or even release, the frustration will subside quickly. It still supports my own speculation that the issue with Blizzard's delays are not in the company, but in the people/community who expect like they're wronged. It's up to us to be more patient or not. They have an alternative to release a product that could be less than the standards they hold. They are public that they hold high standards and have public mottos regarding it.
If people thought "They'll release it when it's ready" instead of "They delayed beta"... there would be a lot less frustration/disappointment. It's also a shame that they think they're the only ones disappointed. Blizzard wants it out in the public more than we want it in our hands... but it has to be ready. No matter what anyone speculates, that is fact.






Reply With Quote




