X

Ratchet & Clank 2: Going Commando Videos and Trailers - PS2

  • Publisher: Sony Computer Entertainment
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Nov 11, 2003
  • # 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:It's time for more galaxy kicks with Ratchet & Clank! Going Commando ups the action, the gadgets, the look, the laughs, the visuals and the gameplay. Surfing space on their righteous mission to rock the galaxy, Ratchet and his dimunitive side-kick robot Clank will explore 20 planets and use 20 new innovative weapons. After being kidnapped by Abercrombie Fizzwidget, the quirky CEO of Megacorp of the Bogon Galaxy, our unlikely heroes Ratchet and Clank set out to find the secrets behind "The Experiment." Promised riches and a sleek lifestyle by Fizzwidget, including a penthouse suite in Megapolis, commando training for Ratchet and an accountant job for Clank, our dynamic duo soon find themselves in for more than they expected. Will our heroes survive Going Commando?
G4TV Rating
N/A
  • Avg User Rating
    (5 Ratings)
    5 / 5
  • Rate This Game

Ratchet & Clank 2: Going Commando Videos

Displaying 1–6 of 6 videos

 


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>