Bomberman Latest News - PSP

  • Publisher: Konami
  • Genre:Action
  • Developer: Hudson Soft
  • Release Date:Sep 13, 2006
  • # of Players:4 players
  • ESRB:E - Everyone (Mild Cartoon Violence)
  • Platforms:
Game Description:Experience a new adventure with an old favorite as Bomberman makes a heroic debut on PSP! Things aren't looking up in Bomberman's galaxy. Neighboring planets have been attacked by a robot army, and a sinister dark shadow is moving closer to Bomberman's home. Join Bomberman on an interstellar journey to save his planet! Follow the story through 100 levels, where a new item stock system lets you strategically collect and use tons of new items. Revive the old-school vibe in Classic Mode, which features over 50 levels from the original Bomberman. Up to four players can join in wirelessly for 20 stages of battles or compete in no-time-limit party games.
G4TV Rating
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game

Bomberman 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?


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