Q: Is the Saber the only vehicle you will be able to fly in space?
EO: We've already revealed the Falcon, which is what we're calling the Warthog in the skies. That's actually what you saw drop Noble team off onto the beach. That is actually pilotable by the player in the campaign.
Q: What about the Covenant ships we saw you blow up in space?
JT: We're not talking about that today.
EO: There may or may not be Covenant ships in the game.
Q: Was there ever any temptation to integrate Kinect into the experience, or would you say it's not suited to action games like this?
JT: I wouldn't say it's not suited but for us Kinect came online about... we were already a year and a half into production. It was just sort of impossible for us to think about integrating it.
EO: That's definitely something you don't want to shoehorn in, right? You want to build that in from the ground up to make sure that experience is built with Kinect in mind, whereas we were already well into the development process by the time Kinect was ready.
Q: Do you see scope for future projects where that could be incorporated into a first-person shooter?
EO: We're really not talking about any... people are doing it, right? I mean other developers are working it in. We're not talking about any future projects today.
Q: We've heard Kinect chews up an entire core of the 360's processor. Is it technically feasible to make a game of Halo: Reach's visual quality and scale that also supports Kinect?
EO: That's probably actually a really good question for the Kinect guys. Technically I really don't have any information on it. We could talk to some engineers but... as far as what it's taking up on processor cycles or CPU cycles, I really don't have any information at all about it. At the Kinect booth I'm sure they have all of those numbers ready to give out, right?
Q: Does Master Chief pop up in any shape or form in Halo: Reach?
JT: Reach takes place just prior to the events of Halo 1. Beyond that I don't think we want to talk any more about what's going on in the campaign, unfortunately.
EO: It's a standalone prequel, so Master Chief's story begins after the events of Reach.
Q: So is that no, Master Chief is not in the game?
JT: That's... er... we're not talking about that right now.
Q: What's been the biggest challenge for you during the development of Reach? What have you had to drop if you've had to drop anything?
EO: There have been no cuts. Everything made it in!
JT: Everything we ever wanted to do is in the game! The challenge for us is always the same when we're making games. It's making games that we think are great, that meet the Bungie quality bar. And at the same time there's absolutely a challenge with a game like Reach where you want to push the envelope as much as possible but you don't want to ruin the core of what's there for fans. So it's a real balancing act. I think we absolutely pushed it pretty far in Reach. Lots of new changes to what's core about Halo, but at the same time a real respect for the core Halo fans.
EO: Speaking to what you were just talking about where the story takes place, it actually makes for a really good entry point for newcomers to the series. If you don't know anything about Halo, this is a standalone prequel. You can get in, fire it up and start the story from the beginning. And people who are invested in the fiction and can tell you what the names of the ships are, or Master Chief's birthday and all that, there's tons of stuff in here - they know what star system planet Reach is in. It's a pretty cool set.