Sid Meier's Civilization IV: Colonization Screenshots and Images - PC

Sid Meier's Civilization IV: Colonization
  • Publisher: 2K Games
  • Genre:Strategy
  • Developer: Firaxis
  • Release Date:Sep 23, 2008
  • # of Players:1 player
  • ESRB:E10+ - Everyone 10+ (Alcohol and Tobacco Reference, Mild Violence)
  • Platforms:
Game Description:A complete reimagining of Sid Meier's 1994 classic, Colonization is a total conversion of Civilization IV that combines Civilization's addictive gameplay with all-new graphics and features that add more depth to the franchise. In Colonization, players lead one of four European nations on a quest to conquer and rule the New World. Players will be challenged to guide their people from the oppressive motherland, discover the New World, and negotiate, trade and fight with both the natives and other nations as they acquire power and fight for freedom and independence. New features in this version of Colonization include a brand-new interface, improved diplomacy options and special modding tools.
G4TV Rating
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game
  • Civilization IV: Colonization Review

    Posted: September 23, 2008

    14,856 Views | 02:19 | 7 Comments

  • Sid Meier's Civilization IV: Colonization Trailer

    Posted: September 11, 2008

    1,492 Views | 01:27


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