Conflict: Desert Storm Latest News - XBX

  • Publisher: Take Two
  • Genre:Action, Adventure
  • Developer: Pivotal Games
  • Release Date:Oct 2, 2002
  • # 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:Conflict: Desert Storm places you in the thick of the Gulf War. Leading a four-man team of Special Forces as US Delta Force or British SAS, you will scope out targets, infiltrate heavily guarded compounds, assassinate Iraqi leaders and rescue hostages. You will kill with the silence of a knife stroke or the high-powered blasts of high-tech rifles. For larger targets you will detonate explosives, call in air strikes, artillery batteries or cruise missle launches. You will also move seamlessly through indoor and outdoor environments, day and night. Humvees, tanks and helicopters will also be at your disposal.
G4TV Rating
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Conflict: Desert Storm News

Displaying 1–1 of 1 articles

  • War is Games: From the Civil War to the Iraq War and Beyond

    Memorial Day. What does that mean? Well, to the typical America, it means beer, bikinis, and a day off from work! And if you're a gamer, it also means double experience in Call of Duty: Modern Warfare 2. Or even TRIPLE experience if you're diving into the recently updated Gears of War 2 experience. What better way to honor the valiant dead than...

    Posted May 30, 2011

    War is Games: From the Civil War to the Iraq War and Beyond


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 -->

        <customErrors mode="Off"/>

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 -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>