X

Manhunt Videos and Trailers - PS2

  • Publisher: Take Two
  • Genre:Action, Shooter
  • Developer: Rockstar North
  • Release Date:Nov 20, 2003
  • # of Players:1 player
  • 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:Bloody, bleak and funny, the same twisted minds that brought you Grand Theft Auto, hatch a new take on Amerika with Manhunt. You are James Earl Cash, and you were killed. Now in the town of Carcer City, a town filled with rusted-out cars, dingy bars and decaying shacks, they have brought you back to life! But as soon as you start breathing again, they are after you in a vicious manhunt! As the prey you must run and hide! Keeping the dogs at bay, you will uncover what is behind this cruel bloodsport. But before you win back your humanity, you'll have to dole out the punishment yourself. You may be the hunted, but you're on your own little righteous manhunt. Who will win? Rockstar Games again deliver a cultish experience that has the makings of another dark urban classic.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Manhunt Videos

Displaying 1–1 of 1 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>