X

Bodycount Latest News - PC

Bodycount
  • Publisher:
  • Genre:
  • Developer:
  • Release Date:Jan 1, 0001
  • # of Players:1 player
  • ESRB:Rating Pending
  • Platforms:
G4TV Rating
2 / 5
  • Avg User Rating
    N/A
  • Rate This Game

Bodycount News

Displaying 1–1 of 1 articles

  • Bodycount Dev Studio To Be Shut Down By Codemasters

    Codemasters' Guildford Studio recently celebrated the launch of Bodycount, a fast-moving first-person shooter that offered some cool ideas but failed to resonate with the majority of the gaming audience. The game's publisher, Codemasters, is now moving to shut the studio down, shedding 66 employees as it embraces a newly narrowed focus on...

    Posted September 14, 2011

    Bodycount Dev Studio To Be Shut Down By Codemasters
  • Bodycount Gameplay Trailer

    Posted: June 29, 2011

    8,450 Views | 01:49

  • BodyCount Preview

    Posted: July 15, 2010

    14,914 Views | 02:34

  • E3 2010: Bodycount Interview

    Posted: June 24, 2010

    2,724 Views | 03:36

  • E3 2010 Live: Bodycount Hands-On Demo

    Posted: June 17, 2010

    8,421 Views | 05:00

  • E3 2010: Bodycount E3 Pre-Alpha Gameplay Reveal Trailer

    Posted: June 14, 2010

    2,838 Views | 01:36

 


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>