Keighley vs. Moore: a FaceBreaker showdown



7:33 PM on 06.08.2008

Just because Peter Moore is the head of EA Sports doesn’t mean that he’s a stuffy old “suit”. He’s a pretty skilled gamer in his own right, and that was put to the test on this past Friday’s episode of GameTrailers TV. Moore faced off against the show’s host, the affable Geoff Keighley, in a match in FaceBreaker, the upcoming arcade-style boxing videogame from EA.

FaceBreaker will be the first title to be released under EA’s new “EA SPORTS Freestyle” sub-brand, a label whose games will be aimed squarely at the growing “casual” sports gaming market. Of course, the requisite buzzwords associated with casual gaming are in full effect here: “pick-up-and-play”, “inclusive”, and “casual” -- not that that’s a bad thing, of course. In fact, I’m really looking forward to FaceBreaker, because I’d love to have something sports-related to play with my non-sports-gaming friends.

The video above doesn’t just comprise the Keighley-Moore fight; much of it consists of an extended interview regarding the game, as well as some trash talking. The whole thing is three minutes and forty seconds long, but if you’re solely interested in the fight, jump in at the two-and-a-half-minute mark. I won’t give away the winner; you’ll just have to watch for yourself.

Of note is that both men played with created characters that bore striking resemblances to their real-life counterparts; apparently, you’ll be able to use the Xbox Live Vision Camera to insert yourself into the game (no word yet on whether the game will also be compatible with the PlayStation Eye). FaceBreaker is currently set for a September 5th release; for a number of character videos, check out the game’s page at GameTrailers.

[Thanks, Justin!]



Come for the news, stay for the people:

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.