X

Halo 3 Screenshots and Images - Xbox 360

  • Publisher: Microsoft
  • Genre:Shooter
  • Developer: Bungie
  • Release Date:Sep 24, 2007
  • # of Players:1 player, 16 online
  • ESRB:M - Mature (Blood and Gore,Mild Language,Violence)
  • Platforms:
Game Description:The entire epic story has led up to this moment. The Covenant has taken control of Earth. The Flood's numbers continue to swell. Humanity is scattered and nearly destroyed. Only Master Chief, the genetically altered, cybernetically enhanced Spartan supersoldier, can save mankind. Find the answers to all your questions as you battle your way through the final chapter of the Halo saga! What will happen to Cortana, still caught in the clutches of Gravemind? Will the Covenant activate the network of Halos and destroy all sentient life in the galaxy? Or will Master Chief find the cunning and firepower he needs to destroy the Flood, stop the Covenant, and rescue humanity?
G4TV Rating
N/A
  • Avg User Rating
    (141 Ratings)
    4.5 / 5
  • Rate This Game

Halo 3 Screenshot & Image Galleries

  • A History of Halo

    Posted: November 5, 2012

    11,633 Views | 03:17

  • Halo 3, AC: Revelations and CoD: Black Ops Are Dirt Cheap

    Posted: October 24, 2012

    8,685 Views | 03:00

  • Top 5 Halo Maps by the UFC's Phil Davis

    Posted: July 18, 2012

    5,964 Views | 01:21

  • Top 100 Video Games of All Time #23 - Halo 3

    Posted: June 14, 2012

    10,462 Views | 02:08

  • The Future of Halo with Frank O'Connor

    Posted: November 23, 2011

    26,603 Views | 02:58

 


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>