Whatever is holding up development on Prey 2, the simple truth remains: we aren't able to play it. And for a game that showed so well, publicly, that sucks. Offering the latest update to IGN, Bethesda VP of PR and marketing Pete Hines says it's been frustrating for all parties involved.
"It's simply not good enough," explained Hines. "We're not going to just proceed blindly with something that isn’t good enough. We've been very specific about why, and we've been very specific about the whats. When that gets addressed and changed or whatever, at that point we can give an update. But nobody's disappointment is greater than ours.
"We spent a lot of time and money and effort trying to make this thing happen and support folks," he continued, "but at the same time, you just can't keep throwing money at it and saying, 'Sure, it'll eventually work.' You have to have the discipline to say, 'It's not good enough. It's not hitting the quality bar. Why isn't it? We've been at this for a while, and what we have is not what we talked about.' So that's where we are."
On the bright side, I'm so numb to the bad news over Prey 2 that this isn't the least bit surprising. Commenting on the rumors from the development side, Hines said that "I think all of the stuff that you've heard at this point has been from one side of this, and it's been somebody putting spin on it, like, 'Here’s what happened.' No, that's your version of what you think happened. I haven't heard from anybody yet that actually sat in the room."
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
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.