X

River City Ransom Latest News - GBA

  • Publisher: Atlus
  • Genre:Action, Adventure
  • Developer:
  • Release Date:May 26, 2004
  • # of Players:1 player
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:"To the citizens of River City: I hold your high school captive! With my gangs of students and vicious bosses roaming the streets, nobody can stop me now! Meet my demands - or else!" Slick, the meanest, most powerful gang lord in River City, has issued this ultimatum - and the entire town is powerless in a grip of fear! Now our young heroes Alex and Ryan must fight to free their fellow students and save Ryan's girlfriend. Play in dynamic Story Mode by yourself or co-operatively with a friend, or play against one another in Battle Mode.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

River City Ransom News

Displaying 1–1 of 1 articles

  • River City Ransom 2 Coming To Consoles...In Japan

    Japanese developer Miracle Kidz announced that it is developing "Downtown Nekketsu Monogatari 2" for release on consoles this summer in Japan. "What the hell is that?" you may ask. Why, it's River City Ransom 2! The beat-em-up that originally came out for the NES back in 1989. River City Ransom 2 is being developed by staff...

    Posted March 18, 2011

    River City Ransom 2 Coming To Consoles...In Japan

 


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>