Two tanks, one eagle, and a wall of red bricks. If you grew up anywhere a Famicom (or one of its many clones) was plugged into a TV, you probably remember Battle City — Namco's 1985 top-down tank shooter that a whole generation played with a friend on the couch. You can play Battle City in your browser with no download, and it still takes about thirty seconds to get hooked.
Background: A Tiny Cartridge With a Huge Footprint
Battle City was released by Namco for the Famicom in Japan in 1985. It builds on Namco's earlier arcade game Tank Battalion (1980), keeping the basic idea — drive a tank through a maze, shoot enemy tanks, protect your base — and adding two-player co-op, power-ups and a level editor.
What makes Battle City's story unusual is how it spread. The game never got an official Western cartridge release, yet it became one of the best-known 8-bit games across Eastern Europe, Russia, China and much of Asia, largely through Famicom-compatible clone consoles and multicart cartridges. For many players it was simply "the tank game" — no title screen memory required.
Gameplay: Defend the Eagle
Each stage is a single screen. Your base, marked by an eagle, sits at the bottom center behind a thin ring of bricks. Enemy tanks spawn from the top of the screen, and each stage has 20 of them to destroy. If an enemy shot reaches the eagle, the game is over immediately — no matter how many lives you have left.
The terrain is what turns this into a puzzle as much as a shooter:
- Brick walls can be shot apart, which means both you and the enemy can open new paths.
- Steel walls block normal shots.
- Water can't be driven across, but bullets fly over it.
- Trees hide tanks (yours included) from view.
- Ice makes your tank slide past where you meant to stop.
Enemy tanks come in four kinds: a basic tank, a fast-moving tank, a tank that fires faster shells, and a heavily armored tank that takes several hits. Some enemies flash red — destroy one of those and a power-up appears on the field.
What Makes It Great
The power-ups are perfectly designed. There are only a handful, and each one changes the situation instantly:
- Star — upgrades your tank. Collect enough and your shots can break steel.
- Grenade — destroys every enemy currently on screen.
- Helmet — a temporary force field.
- Clock — freezes all enemies for a few seconds.
- Shovel — temporarily turns the bricks around your eagle into steel.
- Tank — an extra life.
Co-op that creates stories. Two players share the screen and the same base. You can shoot your partner, which stuns their tank for a moment instead of destroying it — a mechanic that has started more sibling arguments than it has helped anyone win.
Construction mode. Battle City lets you design your own stage by placing bricks, steel, water, trees and ice. For a lot of kids this was the first time they ever "made a level" for a game.
Beginner Tips
- Guard the base first, score second. Many runs end because a single enemy slips down a side lane. Don't chase tanks to the top of the screen while the bottom is open.
- Don't blast your own walls carelessly. Every brick you remove near the eagle is one less shot between an enemy and game over.
- Prioritize red flashing tanks. The power-up they drop — especially a Shovel or Grenade — can save a bad stage.
- Use trees as cover, but remember enemies can hide there too.
- Stack stars. An upgraded tank clears armored enemies far faster and can punch through steel to create shortcuts.
- In co-op, split the screen. One player holds the left lane, the other the right. It works far better than both of you chasing the same tank.
Under the Hood (for the Devs Here)
Full disclosure: I built OnlineClassicGame, the site I've been linking to. In previous posts I wrote about emulator cores, ROM loading and mobile controls. This time I want to talk about something less glamorous that matters just as much for a site like this: URL structure and multilingual SEO.
Battle City is a good example because its audience is spread across many languages. A single English page wouldn't serve the players who know it as バトルシティー or remember it from a Chinese clone console.
Two pages per game. Every game gets a detail page at /game/<slug> (description, controls, background) and a separate play page at /game/<slug>/play (the emulator itself). The detail page is lightweight, fast to crawl and full of text search engines can understand. The play page is where the heavy emulator assets load. Splitting them keeps the content page indexable without making crawlers deal with the emulator, and it gives users a clear choice between "read about it" and "just play".
Language prefixes, not query strings. English lives at the root, and other languages get a path prefix: /cn/, /tw/, /ja/ and /ko/. So Battle City exists at /game/battle-city, /ja/game/battle-city, and so on, each with its own localized <title> and the correct <html lang>.
hreflang on every page. Each version lists all of its siblings with hreflang tags — en, zh-Hans, zh-Hant, ja, ko — plus an x-default pointing to the English page. Simplified and Traditional Chinese are tagged by script rather than by country, because the content differs by writing system, not by region. Play pages get their own hreflang set pointing to the other languages' play pages, so detail pages and play pages never get mixed up.
Self-referencing canonicals. Each language version declares itself as canonical. A common mistake is pointing every translation's canonical at the English page, which tells search engines the translations are duplicates and quietly removes them from results.
None of this is exciting code, but for a small site it's the difference between showing up for "Battle City" in one language and showing up in five.
Your Turn
Did you play Battle City on a real Famicom, a clone console, or a 9999-in-1 multicart? And did you ever build your own stage in Construction mode? Tell me in the comments — and if you want a quick round before lunch, Battle City is ready to play here.
Top comments (0)