How do me and my friend play?
Battle City Multiplayer
A downloadable game for Windows and Linux
Battle City Multiplayer is a remake of the 1985 Namco's classic game, but with TCP/IP support and a deathmatch mode.
If you've been living under a rock, or didn't have the privilge to witness this true classic, Battle City is a challenging game where you must face hordes of enemy tanks that will relentlessly try to destroy your base; and it's up to you (or you and a buddy) to outsmart them and stay alive through 35 stages of pure nostalgia/adrenaline.
Some features of the game:
- 4 different types of enemies.
- 6 different power-ups.
- 35 stages.
- 20 enemies per-stage
- Different types of terrain that pose different challenges.
Features of this version includes:
- TCP/IP support.
- More than two players (toggleable through config file).
- Level editor (in a separate download).
- Deadly Friendly fire (toggleable in-game).
- Setting the number of lives per player.
- Setting the starting level.
- Custom arcade or death match maps.
- Built-in chat.
If you like the game please consider donating so I can keep making better games!
|Updated||24 days ago|
|Release date||Oct 26, 2017|
|Tags||Arcade, Co-op, deathmatch, Multiplayer, Pixel Art, Retro, Singleplayer, Tanks, Top-Down|
|License||GNU General Public License v2.0 (GPL)|
|Average session||A few minutes|
|Multiplayer||Local multiplayer, Server-based networked multiplayer, Ad-hoc networked multiplayer|
|Player count||1 - 2|
Click download now to get access to the following files:
Log in with itch.io to leave a comment.
Start a new game, give your ip to your friend and have him join a game with that ip. If you're behind a router or firewall, ports TCP 2596/UDP 2597 must be open.
Me and my friend keep getting in a game but it lags very bad and i keep getting disconnected. note we are on same wifi.
That's weird. I've tested it live many times through wifi, same local network, internet, etc, and never had serious lag issues or disconnects. If you play other games, those work okey? Try executing the jar through the command line and see what errors you get.