Blizzard is always happy to talk about new ways of making money, you know, working on porting diablo 3 to consoles, macs, the next expansion pack, etc. But no word yet on PVP. Hmmm...
Blizzard is always happy to talk about new ways of making money, you know, working on porting diablo 3 to consoles, macs, the next expansion pack, etc. But no word yet on PVP. Hmmm...
And the console programmers have what to do with PvP?
Blizzard have been looking into porting Diablo months/years before release.
Blizzard pretty much screamed it in our faces that console development and PC development were completely separate. The development of the console version would not hinder the PC version at all.
EDIT: Whether or not that still applies I'm not sure. They said that before D3 was released.
Rollback Post to RevisionRollBack
Bashiok - Blizzard Representative - 08/01/2011 -"So how many skill combinations are there now? Well taking into account 6 active skills, all the rune combinations, and 3 passives we currently expect each class to have roughly 2,285,814,795,264 different build combinations."
"Hey, I thought you'd like the witty irony of grub-on-glowie violence!"
Blizzard is always happy to talk about new ways of making money, you know, working on porting diablo 3 to consoles, macs, the next expansion pack, etc. But no word yet on PVP. Hmmm...
And the console programmers have what to do with PvP?
Blizzard have been looking into porting Diablo months/years before release.
Well maybe Blizzard could take those programmers off the console project for now and have them help out with the PVP that is already 8 months late.
I never even mentioned anything about programmers, just the fact that they have time to talk about all of these other things and yet we still haven't heard a thing about the one thing that matters to most players right now.
I never even mentioned anything about programmers, just the fact that they have time to talk about all of these other things and yet we still haven't heard a thing about the one thing that matters to most players right now.
"most"
Funny how when Blizzard decided to delay PvP the player base was "mostly" uncaring about PvP.
You would have had to actually have been around pre launch to know this though.
I never even mentioned anything about programmers, just the fact that they have time to talk about all of these other things and yet we still haven't heard a thing about the one thing that matters to most players right now.
For the entire duration of Blizzard announcing the job opportunity for console development there was one position for a console programmer. It got taken and the guy was shown around on some interviews talking about how they're looking into what can work and what can't. I'm assuming there's maybe at least one more guy with him right now, which pretty much encompasses the "console team".
And the designers can talk about a console port all they want since design isn't exactly "the crunch" companies go through when they're working on a feature that is already mostly established.
@WhiskeyDex420
If Blizzard pulled all their resources into one thing that still had work to be done WoW would still be on its second expansion and SC2 would be pre-launch. Because people would constantly be changing their priorities. That's not how you run a company with 5+ teams of developers.
They're doing this mistake with Titan, constantly recycling the team in order to help on different projects, like for example the launch of Battle.net 2.0 (which did happen). And we can see what the progress on Titan has been.
I never even mentioned anything about programmers, just the fact that they have time to talk about all of these other things and yet we still haven't heard a thing about the one thing that matters to most players right now.
"most"
Funny how when Blizzard decided to delay PvP the player base was "mostly" uncaring about PvP.
You would have had to actually have been around pre launch to know this though.
What does that have to do with the present though? The past is the past. People felt that way because it was delaying the release the of the game, not because they didn't care about it. They knew it would come later. No one thought it would take this long though and we are quite disappointed as a result.
What does that have to do with the present though? The past is the past. People felt that way because it was delaying the release the of the game, not because they didn't care about it. They knew it would come later. No one thought it would take this long though and we are quite disappointed as a result.
Sure, but now people are saying Blizzard should've delayed release in order to get PvP in. See how the community opinion goes?
Well maybe Blizzard could take those programmers off the console project for now and have them help out with the PVP that is already 8 months late.
Not a programmer, I see. Adding more programmers/developers to a project has very diminishing returns. See Brooks's Law.
As for the console port - I'm not all that happy about it. Or better yet, I have some fears about it. Adding a console port usually means simplifying a game in different areas (UX, controls, gameplay,..) - and I don't think they should do that in D3. They already simplified it more they I would like.
Well, the game has already said to have been dumbed down for consoles from the very start. That's the explanation for why the UI is so simple and generic, no customization, no addons, no lobbies, etc. Not saying it's a fact, just a hypothesis.
You ever remember a single time when Blizzard was not LATE with their development promises?
Just once?
Ever?
You can tell who has never been around for a Blizzard game when it is new before.....
Yup, LoD was released exactly a year after D2. And was excellent.
Of course, almost none of the people that made it have worked there for years. Maybe there's a lesson there...
Didn't they miss the holiday window they originally advertised for LOD? (I seem to recall a 2 month delay with LOD, I think they even mention that in one of their "retrospectives")
And on topic about the console version;
I really, really, really doubt a console version will ever see the light of day. (SC Ghost flashbacks and all that jazz)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Blizzard is always happy to talk about new ways of making money, you know, working on porting diablo 3 to consoles, macs, the next expansion pack, etc. But no word yet on PVP. Hmmm...
And the console programmers have what to do with PvP?
Blizzard have been looking into porting Diablo months/years before release.
Ha. Bagstone.
EDIT: Whether or not that still applies I'm not sure. They said that before D3 was released.
Bashiok - Blizzard Representative - 08/01/2011 -"So how many skill combinations are there now? Well taking into account 6 active skills, all the rune combinations, and 3 passives we currently expect each class to have roughly 2,285,814,795,264 different build combinations."
"Hey, I thought you'd like the witty irony of grub-on-glowie violence!"
Well maybe Blizzard could take those programmers off the console project for now and have them help out with the PVP that is already 8 months late.
You ever remember a single time when Blizzard was not LATE with their development promises?
Just once?
Ever?
You can tell who has never been around for a Blizzard game when it is new before.....
"most"
Funny how when Blizzard decided to delay PvP the player base was "mostly" uncaring about PvP.
You would have had to actually have been around pre launch to know this though.
For the entire duration of Blizzard announcing the job opportunity for console development there was one position for a console programmer. It got taken and the guy was shown around on some interviews talking about how they're looking into what can work and what can't. I'm assuming there's maybe at least one more guy with him right now, which pretty much encompasses the "console team".
And the designers can talk about a console port all they want since design isn't exactly "the crunch" companies go through when they're working on a feature that is already mostly established.
@WhiskeyDex420
If Blizzard pulled all their resources into one thing that still had work to be done WoW would still be on its second expansion and SC2 would be pre-launch. Because people would constantly be changing their priorities. That's not how you run a company with 5+ teams of developers.
They're doing this mistake with Titan, constantly recycling the team in order to help on different projects, like for example the launch of Battle.net 2.0 (which did happen). And we can see what the progress on Titan has been.
Ha. Bagstone.
What does that have to do with the present though? The past is the past. People felt that way because it was delaying the release the of the game, not because they didn't care about it. They knew it would come later. No one thought it would take this long though and we are quite disappointed as a result.
Sure, but now people are saying Blizzard should've delayed release in order to get PvP in. See how the community opinion goes?
Ha. Bagstone.
What makes you believe that dev effort is the bottleneck for PvP delivery?
Yup, LoD was released exactly a year after D2. And was excellent.
Of course, almost none of the people that made it have worked there for years. Maybe there's a lesson there...
Well, the game has already said to have been dumbed down for consoles from the very start. That's the explanation for why the UI is so simple and generic, no customization, no addons, no lobbies, etc. Not saying it's a fact, just a hypothesis.
Didn't they miss the holiday window they originally advertised for LOD? (I seem to recall a 2 month delay with LOD, I think they even mention that in one of their "retrospectives")
And on topic about the console version;
I really, really, really doubt a console version will ever see the light of day. (SC Ghost flashbacks and all that jazz)