Good Old Games
Donate to Codex
Putting the 'role' back in role-playing games since 2002.
Odds are, something you like very much sucks. Why? Because this is the RPG Codex
News Content Gallery People Games Companies  
Forums About Donate RSS Contact Us!  

What the hell were we thinking?

Visit our sponsors! (or click here and disable ads)

What the hell were we thinking?

Game News - posted by VentilatorOfDoom on Wed 30 November 2011, 10:50:20

Tags: BioWare; Mass Effect 3

OXM had a brief chat with BioWare's Mac Walters and learned that content originally cut from ME2 will be used in ME3 instead. 

 

"There was a Mass Effect 2 plot that was a kind of callback to the first Mass Effect that was going to be on the Citadel, and we cut it. But now it's made a resurrection in Mass Effect 3, so I'm happy, but I can't say what it is. That's the nice thing about trilogies, sometimes you get a second chance."

 

Mass Effect 2's premise and possible endings were a headache to write around, Walters admitted, particularly given the need to prepare the ground for a threequel.

I don't think I'd call it 'trapped'," he explained, when asked how he felt about having to accommodate several possible player decisions at key plot junctures. "They're more hurdles. Sometimes they're hurdles that we've given ourselves, so we kind of smack ourselves in the head and say 'What the hell were we thinking? Why did we do that?'

 

The classic example is 'Hey, let's make the ending of Mass Effect 2 a suicide mission where all your henchmen can possibly die, and Shepard can even die!' Oh right... and then we're gonna do another game after that. What the hell are we gonna do with all those guys?"

No worries, I'm certain you will find a way to make all these decisions and different outcomes entirely insignificant in ME3.

 

Spotted at: Gamebanshee

There are 28 comments on What the hell were we thinking?

Site hosted by Sorcerer's Place Link us!
Codex definition, a book manuscript.
eXTReMe Tracker
rpgcodex.net RSS Feed
This page was created in 0.0501599311829 seconds