1,000 Player Bomberman is Actually More Ridiculous than You Think

Wed, Feb 27, 2013

Arcade, Frisky Misc, PC

They say the definition of insanity is doing the same thing, over and over, and expecting different results. They’re wrong: the definition of insanity is Bombermine, where up to a thousand players share the same gigantic map and play Bomberman together. Imprecise controls and mild latency be damned — this is glorious.

If you’re unfamiliar with Bomberman, first of all, that’s not okay. But, if you need to be told, it involves scrambling around on a grid of paths and blocks and dropping bombs which explode in all four cardinal directions, in an effort to carve out more blocks and kill the other players. Now, imagine the grid is hundreds and hundreds of squares, contains hundreds of players, all trying to race for treasures and kills. You heard right; there’s treasures now, which gives the players a good reason to cluster together into the iconic split-second squabbles that define Bomberman.

Sounds a bit chaotic, right? Okay, now imagine that there are powerups that turn you into an uncontrollable Nyan Cat, or spawn a dozen bombs at once, or set off nuclear detonations several squares wide. And then imagine that once the match starts to wind down, hundreds of Pac-Men appear and start to eat the level.

There’s social gaming, and then there’s giving a thousand people high explosives and seeing what happens. You need to witness this madness for yourself.

Be Sociable, Share!

Related posts:

  1. Want to Play Halo on the Go? Spawn Labs May Have Your Solution
  2. Blockolicious is Now Free on Facebook and Also Very Juicy
  3. Meteor Games Introduces Player Avatars to Ranch Town
  4. FreeAppADay for 05/07/10: Sudoku 2
  5. Hospital Havoc 2 Raises Over $10,000 with Appbackr
, , , , , , , , ,

This post was written by:

- who has written 1010 posts on Frisky Mongoose.


Contact the author


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0