hot  /  reviews  /  video  /  blogs  /  forum

Blizzard not milking StarCraft 2, money was 'never part of the conversation'

Nov 12 // Brad Nicholson

According to Blizzard COO Paul Sams, Blizzard isn’t trying to tickle your pocketbooks by splitting StarCraft 2 into three individual games. In a recent interview with Videogamer, Sams defended the decision by noting that money was never a “part of the conversation.” It was done to provide a “better experience” for the consumer.

From the interview:

I guarantee it. I give my word. There was never, ever a conversation where we said, ‘let’s do this because we’re going to make more money’. I guarantee it. As a matter of fact the sole reason we did it was because we thought it was going to be a better experience. Anybody that says otherwise is not correct. It is absolutely not what we did it for.
While I congratulate Sams for being so blunt, I find it particularly hard to believe that the faces around the boardroom didn’t light up when the idea of splitting the title was being thrown around. Regardless, I have high hopes and I’m starting to buy into the fact that three StarCraft 2s isn’t a bad thing. What do you guys think?

 

[via VG247]


 BLOG A RESPONSE



Brad Nicholson //
 Follow Blog + disclosure

This blog submitted to our editor via our Community Blogs, and then it made it to the home page! You can follow community members and vote up their blogs - support each other so we can promote a more diverse and deep content mix on our home page.



Get more destructoid:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.

advertisement:

395 PEOPLE ARE READING:



Back to Top