X

Watchmen: The End is Nigh - Part 1 & 2 Screenshots and Images - Xbox 360

  • Publisher: WB Games
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Jul 21, 2009
  • # 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:Rorschach's Journal: more than ten years before the Watchmen movie storyline. Tonight I hit the streets in Watchmen End is Nigh: two part prequel action brawler with Rorschach and Nite Owl. Two heroes fighting crime together. Cleaning city of scum. Holding back nothing in combat where bottom-feeders get what they deserve. Keene Act not yet passed. City still needs and respect its heroes. Vigilante justice best way to clean up human trash. Part 1: explore once-fruitful partnership of Rorschach and Nite Owl. Part 2: Rorschach contacts Nite Owl for help in finding missing girl. Combat not for squeamish. Bloody and unforgiving. Explore characters, rivalries, and backstory of landmark graphic novel.
G4TV Rating
N/A
  • Avg User Rating
    (6 Ratings)
    3.5 / 5
  • Rate This Game
  • Watchmen: The End Is Nigh Part 2 Trailer

    Posted: July 15, 2009

    2,978 Views | 01:07

 


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>