X

Galactic Civilizations II: Dread Lords Videos and Trailers - PC

Galactic Civilizations II: Dread Lords
  • Publisher: Stardock
  • Genre:Strategy
  • Developer: Stardock
  • Release Date:Feb 21, 2006
  • # of Players:1 player
  • ESRB:E10+ - Everyone 10+ (Language, Mild Fantasy Violence)
  • Platforms:
Game Description:The sequel to Stardock's hit turn-based strategy game, Galactic Civilizations II is a strategy game that takes place in the distant future where mankind has become a space-faring civilization and now must contend with other galactic powers who strive for domination in the galaxy. The sequel includes numerous changes over the original, including the ability to design entire fleets of unique ships from research technology points, more variation in planets for greater numbers of choices on any class of planet, fleet command options, improved combat, and 10 playable races of characters. Galactic Civilizations II also features a vastly overhauled and scalable graphics engine that now runs in 3D (yet is still playable on low-end systems.)
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Galactic Civilizations II: Dread Lords 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>