X

Bomberman: Act Zero Latest News - Xbox 360

  • Publisher: Konami
  • Genre:Action
  • Developer: Hudson Soft
  • Release Date:Aug 31, 2006
  • # of Players:8 players
  • ESRB:T - Teen (Fantasy Violence,Suggestive Themes)
  • Platforms:
Game Description:It's a fight for straight-out survival as Bomberman makes the leap to next-generation gaming! Humans have been reduced to lab rats. Held against their will as test subjects in a lab deep underground, they train as soldiers. Each is given an armored battle suit for a fight for survival, where the final survivor will become the Final Human Weapon. Play as a male or female Bomberman and reach the surface by battling through 99 levels. Upgrade your armor and weapons, avoid bomb blasts, and get aggressive thanks to a new life bar and item system. Battle against eight other Bombermen online, where you can become the world's ultimate weapon.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Bomberman: Act Zero News

Displaying 1–1 of 1 articles

  • Nugget From The Net: Bombershock-Man?

    I'd like to apologize for ruining Bioshock 2 for you by posting the below image I caught on Game-Rave, by way of Reddit: Sorry.

    Posted February 3, 2010

    Nugget From The Net: Bombershock-Man?
  • Microsoft Floor Report

    Posted: October 15, 2008

    1,879 Views | 02:28 | 4 Comments

 


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>