X

Enemy Territory: Quake Wars Previews - PS3

Game Description:The Strogg have made it to Earth. Humanity's only choice is to fight back with everything they've got! Combining the strategy and vehicle combat of the Battlefield series with the run-and-gun quality of Quake, you must take sides with the Strogg aggressors or the Human defenders. Fight on battlefields all over the planet. Choose from five different character classes, deployable gear, and vehicles to wage war and take on your mission objectives, which will move you toward a final goal on each map. You can play with computer-controlled bots for a single-player experience, or take the fight online for multiplayer madness!
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Enemy Territory: Quake Wars Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories

  • Enemy Territory: Quake Wars Review (Console)

    Posted: June 9, 2008

    15,747 Views | 02:31 | 11 Comments

  • Enemy Territory: Quake Wars - Human Juicifier

    Posted: May 9, 2008

    2,194 Views | 01:15 | 1 Comment

  • Trailer: Enemy Territory - Quake Wars

    Posted: April 23, 2008

    2,434 Views | 02:11

 


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>