Drunkenthumbmaster said:If Torchlight can be done Diablo 3 can be done.
Lazy vs Crazy said:Sony and MS may not let that happen though. They could view it as an activision trojan horse. "Hey you let us do this for Diablo. Now you are going to let us do it for CoD."
Mrbob said:Call of Duty is interesting. As much crap as Activision gets at times, Call of Duty games fully embrace Steamworks integration. They don't wall around their own services like EA does. Is it possible the next CoD game on PS3 might be Steamworks enabled alongside the PC version?
Xater said:Microsoft is a problem though.
AzureNightmare said:If there is one subsidiary that Kotick can't boss around its Blizzard. There's a contractual agreement that exists to give Blizzard complete and total control over themselves. Kotick can ask them to do something, and they have every right to tell him to go piss himself or something.
Dedication Through Light said:Add expansions and patch effectively? Dont our console games already do that in the form of DLC?
Metalmurphy said:Yeah no why? It's a service that completely bypasses XBL. They made the exception for SE cause it was freaking FF and they thought they needed it. If they made it for SE they can make it for Blizzard.
Even if the game can't be a pitch perfect port, the point is can it still be excellent, and highly profitable, the answer to both is certainly yes.Boonoo said:Torchlight is a much slower paced game than Diablo (Diablo 2, at least). Endgame in Diablo is all about speed and precision.
Why? If a console port does not effect the PC version at all, what is the logical reason for wanting it to be exclusive?tjohn86 said:I'll take any D3 I can get. I prefer a PC exclusive though.
StuBurns said:It's going to happen for one reason:
Kotick
charlequin said:It's honestly difficult for me to see the money proposition here. Blizzard games sell immensely well on PC; Diablo 3 will easily outsell Starcraft 2 by a significant margin on PC alone. It's hard for me to imagine there are many untapped customers on consoles as opposed to just customers who would switch their platform.
StuBurns said:Why? If a console port does not effect the PC version at all, what is the logical reason for wanting it to be exclusive?
Developers who crow about how the PC version of their multiplatform game hasn't been affected by console ports are usually lying.StuBurns said:Why? If a console port does not effect the PC version at all, what is the logical reason for wanting it to be exclusive?
The simple answer is that blizzard will make less money overall if a console port exists for the reasons I stated previously. Even today, anywhere that sells PC games carries Starcraft Battlechest, Warcraft 3 Battlechest, and Diablo Battlechest. Theyre still always around the top10 or 20 sellers of PC games every year. If a console version of Diablo 3 exist, the constant recycling of used games over a decade would amount to a ton of lost sales over time, lower expansion pack sales due to difficulty selling $40 DLC that requires a base game, and a shift of some sales from PC to console resulting in lower margins. Add to that the cost of supporting the console version and it just doesn't make sense.StuBurns said:Why? If a console port does not effect the PC version at all, what is the logical reason for wanting it to be exclusive?
mysteriousmage09 said:How many times must it be said that Activision has no say at all as to how Blizzard does things. Blizz has stated this themselves dozens of times.
If there is any compromise to the PC version, then fine, that's a perfectly reasonable reason to fear a port, but there's no way Blizzard would ever do that.Hari Seldon said:Because blizzard has 10 programmers and 9 of them work on WoW. If you throw in a console port you are talking about 3-4 years more of additional work if they want to launch them simultaneous.
I made that all up but how else do you explain the duke-nukem style development of D3?
You have no idea what the game would sell on consoles. It could sell thirty million units at $60 and make more than Diablo 2 ever did for all we know.Zzoram said:The simple answer is that blizzard will make less money overall if a console port exists for the reasons I stated previously. Even today, anywhere that sells PC games carries Starcraft Battlechest, Warcraft 3 Battlechest, and Diablo Battlechest. Theyre still always around the top10 or 20 sellers of PC games every year. If a console version of Diablo 3 exist, the constant recycling of used games over a decade would amount to a ton of lost sales over time, lower expansion pack sales due to difficulty selling $40 DLC that requires a base game, and a shift of some sales from PC to console resulting in lower margins. Add to that the cost of supporting the console version and it just doesn't make sense.
Also the market for diablo style game on consoles is unproven. Sacred 2 did poorly on consoles and ran at like a constant 20fps. These isometric games look simple but they have a lot going on, Diablo 3 being the best looking game in the genre won't make it any easier to make run smoothly on console.
Really I thought Blizzard does their own shit.... I mean don't they still own their games, or does Activision. The wait for this game is insane already anyway, so any person that really would want to play it will buy it on PC. I'll take them another 4 years to port it lol....StuBurns said:It's going to happen for one reason:
Kotick
Former Blizzard employeeSo if most publishers control what their developers produce, does Activision control what Blizzard does?
No. There are obviously certain considerations, such as funding, that a developer must be aware of when making their game, but Blizzard is in a unique situation in that they (and WoW) are such a cash cow that any A-B interference would likely result in an inferior product -- and, subsequently, lower sales. They know that Blizzard does things right, and will continue to do so in the known future, resulting in greater profits for the publisher.
I do not think that at the moment Blizzard is doing so well that they are beyond interference. Otherwise why would they merge anyway?
Majine said:It's not happening for one reason:
Battle.net.
This is the only scenario where I could see a console port being viable. Next generation will also likely have serial keys for console games to access online and that would definitely be something Blizzard will require for a console port. They don't want to lose money to used sales.Opiate said:Has anyone considered that this could very well be for the PS3/360 successors? The game doesn't come out on PC until 2012: that could easily mean 2013 for consoles.
If it's on PS3/360, it would be in the twilight of those system's lifespans and would represent huge bottlenecks for RAM usage. Not saying it's impossible: just not sure why people are still assuming the 360 will be a modern platform when it reaches its 8th Christmas (which is where it will be in 2012).
Opiate said:Has anyone considered that this could very well be for the PS3/360 successors? The game doesn't come out on PC until 2012: that could easily mean 2013 for consoles.
If it's on PS3/360, it would be in the twilight of those system's lifespans and would represent huge bottlenecks for RAM usage. Not saying it's impossible: just not sure why people are still assuming the 360 will be a modern platform when it reaches its 8th Christmas (which is where it will be in 2012).
That's going from an installbase of 80 million to nothing. Doesn't seem a very good idea unless they're also willing to wait till that installbase builds up again.Opiate said:Has anyone considered that this could very well be for the PS3/360 successors? The game doesn't come out on PC until 2012: that could easily mean 2013 for consoles.
If it's on PS3/360, it would be in the twilight of those system's lifespans and would represent huge bottlenecks for RAM usage. Not saying it's impossible: just not sure why people are still assuming the 360 will be a modern platform when it reaches its 8th Christmas (which is where it will be in 2012).
Starcraft didn't work well on N64 so it didn't compete with the PC for sales. Diablo 3 on consoles would compete with the PC version, and the PC version would be much higher margin for Blizzard.Einbroch said:Did Starcraft suffer because of a port to the N64?
mysteriousmage09 said:How many times must it be said that Activision has no say at all as to how Blizzard does things. Blizz has stated this themselves dozens of times.
Diablo as a whole series hasn't even sold twenty million units. MW2 sold more, one game, made in two years.Zzoram said:Starcraft didn't work well on N64 so it didn't compete with the PC for sales. Diablo 3 on consoles would compete with the PC version, and the PC version would be much higher margin for Blizzard.
It's actually a liability for Kotick to have control over Blizzard. Blizzard has been autonomous for a decade and has become the most successful PC developer ever, and nothing but Call of Duty exists than can challenge Blizzards franchise and revenue strength. Kotick just ran guitar hero and Tony hawk into the ground, do you think when Vivendi decided who would be in charge of what, they would trust anyone but Blizzard to decide what Blizzard does?hsukardi said:This just cannot be real, having zero control of a major part of your business = liability.
StuBurns said:That's going from an installbase of 80 million to nothing. Doesn't seem a very good idea unless they're also willing to wait till that installbase builds up again.
However you have a point certainly, although more with the expansions, they'll be supporting the game beyond the life of these systems.
Hitting as a 'Diablo 3 Complete' in like 2016 with all the expansions could be a good fit, if all three consoles are technologically viable, and have been out for a couple of years, it'll be a nice install base at that point.Opiate said:I agree. I think Diablo 3 would be hitting at an awkward time on consoles: 2013 will almost certainly be a time when the current generation systems are in decline from a software standpoint (i.e. they will sell less software in 2013 than they did in 2012), but it also won't be a time when the new generation of consoles has hit a critical mass in terms of install base.
Wii HD launch (console) exclusive!Opiate said:I agree. I think Diablo 3 would be hitting at an awkward time on consoles: 2013 will almost certainly be a time when the current generation systems are in decline from a software standpoint (i.e. they will sell less software in 2013 than they did in 2012), but it also won't be a time when the new generation of consoles has hit a critical mass in terms of install base.
Opiate said:Has anyone considered that this could very well be for the PS3/360 successors? The game doesn't come out on PC until 2012: that could easily mean 2013 for consoles.
If it's on PS3/360, it would be in the twilight of those system's lifespans and would represent huge bottlenecks for RAM usage. Not saying it's impossible: just not sure why people are still assuming the 360 will be a modern platform when it reaches its 8th Christmas (which is where it will be in 2012).
Majine said:It's not happening for one reason:
Battle.net.
Very much THIS. But considering the moneybags they can make on each platform, its worth the investment of time and resources to tailor each version of the game to fit its platform perfectly.IoCaster said:I don't care if they port the game to an iPod Mini. As long as they get the PC version done first and keep any 'consolitis' crap from infecting and/or ruining the definitive experience, it's all good.