X

Final Fight: Streetwise Latest News - XBX

  • Publisher: Capcom
  • Genre:Action, Fighting
  • Developer: Capcom
  • Release Date:Mar 2, 2006
  • # of Players:2 players
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:Cody, the infamous hero from the classic Final Fight games, has disappeared. Play as his brother Kyle, an underground pit fighter who's determined to find out what happened. Use street smarts and brawl-based fighting tactics to survive on the gritty streets of Metro City. The fighting action is more intense than ever with two modes of hand-to-hand and weapons-based combat. The non-linear storyline takes you through highly interactive environments where you'll encounter all kinds of seedy types, from loan sharks to hoodlums. But choose your actions wisely. Respect is key to success. Trash your rep at your own peril. The amount of respect you command changes how NPCs react to you.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Final Fight: Streetwise News

  • No results

 

 

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>