X

Tom Clancy's End War Latest News - Xbox 360

  • Publisher: Ubisoft
  • Genre:
  • Developer: Funatics
  • Release Date:Nov 6, 2008
  • # of Players:1 player, 4 online
  • ESRB:T - Teen (Alcohol and Tobacco Reference,Blood,Language,Suggestive Themes,Violence)
  • Platforms:
Game Description:It's here. The battle to end all battles, the war to end all wars. World War III. And you must lead your army to victory! Choose your faction from: The U.S., known for its aerial dominance and ground power; Russia, with heavy weapons and demolitions at its disposal; and Europe, capable of speed and high-tech attacks. Decide what type of battalion you want to lead - airborne, technical, or mechanized. Then, engage the enemy in the online Theater of War. Each day, your faction's victories and defeats will be tallied. After a one- to three-week campaign a winner will be declared, and the war will start all over again.
G4TV Rating
N/A
  • Avg User Rating
    (2 Ratings)
    4.5 / 5
  • Rate This Game

Tom Clancy's End War News

  • No results

 

 

 


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>