Bomsy (tuxdb.com)

Bomsy is a fast, aim-based, multiplayer arena brawler with destructible maps. Take out your opponents by launching bombs in their direction, breaking the ground from under them, or pushing them off the edge! Go after your enemies right off the bat or dig around and hoard upgrades before you decide to engage. The map is your playground; swing off blocks, blast jump to high ground, or quickly roll to safety. With so many ways to get around, Bomsy is made to feel smooth, responsive, and rewarding. Round up your friends and start playing in the bright and colourful world of Bomsy!
FEATURES

7 different maps, each with unique level mechanics!
70+ block layouts!
Lots of items and per-round upgrades!
6 player local multiplayer!
6 player online multiplayer!
Play against bots! (available in local play only and in certain game modes)
Create online lobbies just for you and your friends or join public games!
Tons of skins to unlock! (gift boxes containing skins are dropped at random by destroying blocks in game)
Multiple game modes!
Customize your matches! Control item counts, round time, rounds to win, comeback, etc.

Known Issue: Clients are unable to connect to hosts using IPv6 (Fixed)

[strike]A new issue popped up today where when connecting to certain lobbies it would seemingly take forever to connect. After investigating with the help of players, we discovered it is because our current setup doesn't allow for clients to connect to IPv6 addresses.

We are aware of the issue and are exploring possible solutions - short term and long term.

In the meantime if friends are having problems connecting to your lobby there are steps you can take to make your computer use IPv4.
1. Open the Control Panel.
2. Go to Network and Internet.
3. Go to Network and Sharing Center.
4. On the left, go to Change adapter settings.
5. Choose the network adaptor your computer is currently using.
6. Right click the network adaptor and go to Properties.
7. Look for Internet Protocol Version 6 (TCP/IPv6) and disable it.
8. Click OK!

Sorry for the inconvenience![/strike]

This issue has been fixed in 1.0.9