X

Final Fight One Latest News - GBA

  • Publisher: Capcom
  • Genre:Fighting
  • Developer:
  • Release Date:Sep 26, 2001
  • # of Players:1 player
  • ESRB:E - Everyone (Everyone)
  • Platforms:
Game Description:Capcom's classic arcade fighter Final Fight One comes to the Game Boy Advance. There's trouble in Metro City: the Mad Gear Gang have kidnapped the mayor's beautiful daughter, Jessica. The mayor enlists the iron fist team of heroes Cody and Guy. Now, it's a race against time to scour the city, defeat an army of Mad Gear Gangsters and rescue Jessica. Take your fists to the bad guys. Deal out the damage in non-stop punches, kicks and combos.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Final Fight One News

Displaying 1–1 of 1 articles

  • Poison's Gender Explained Comprehensively In YouTube Documentary

    There are two things I love most in life: Examinations of the cultural issues surrounding the fluidity of gender, and the bat-sh*t obsessiveness of video game fans. The video below contains huge gobs of both. As you may not know, Poison from the original Final Fight released back in 1989, may have been created as a trans-sexual character....

    Posted February 27, 2012

    Poison's Gender Explained Comprehensively In YouTube Documentary

 


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>