1988 · Famicom · Game story
Famicom Wars: The Small Map Where Every Square Has a Supply Line
Nintendo's 1988 Japanese Famicom strategy game finds drama not in heroic special powers, but in balanced armies, vulnerable logistics, and the stubborn arithmetic of taking ground.
In this story
A map that argues back
Famicom Wars looks, at first glance, like an impossibly tidy argument about war. Little tanks, planes, ships, roads, forests and flags sit in a crisp grid. Then a turn begins and the neatness becomes a provocation. Every square wants to be read twice: once as territory and once as a route. Is the forest a shelter or a delay? Is that city income, a repair stop, or bait for an infantry push? Nintendo's current Classics page frames the 1988 Japanese Famicom original as a strategy game of Red Star and Blue Moon, built around moving units, taking the enemy base, or erasing the opposing force. It is a concise premise with a long aftertaste. 1
The game earns that aftertaste by refusing to let the player separate combat from geography. It offers 16 producible unit types—infantry, tanks, aircraft and more—but the interesting question is rarely which piece looks strongest. It is whether that piece can arrive with fuel, ammunition, money, and a defensible place to stand. The two armies are deliberately equipped equally, according to Nintendo's original description. That symmetry makes the map the real personality in the room. There is no factional excuse for a loss; an awkward bridge, a distant port, or a missed capture is usually where the story begins. 2
Trivia Former Nintendo developer Satoru Okada said the project began after he became absorbed in Daisenryaku II and tried to bring that kind of strategy to Famicom with Kenji Nishizawa. SystemSoft had already licensed its console rights elsewhere, so Nintendo's intellectual-property team checked the prototype, judged it non-infringing, and the team released an original game instead. When roughly ten internal title ideas failed, Nintendo president Hiroshi Yamauchi supplied the name Famicom Wars. 7
See it in action
One day at a time
The calendar is the game’s quiet metronome. Red Star acts, then Blue Moon acts; when Blue Moon finishes, one turn—one day—has passed. In that day you may create units, move them, fight, occupy, resupply, or simply end the phase before an opportunity turns into an overextension. The pace is measured, yet it is not sleepy. A day is a packet of promises. A tank pushed too far may be stranded tomorrow. An infantry unit left alive beside a property may turn the next morning’s income into a different kind of battlefield. 3
This is what makes the original’s plain presentation feel tense instead of bare. The game does not ask for reflexes; it asks the player to hear cause and effect. Funds unused in a phase carry forward. Funds themselves arrive at the start of the phase according to the facilities you occupy. The player is therefore always choosing between a purchase now and a larger possibility later. That choice has a pleasingly old-school bluntness: no grand cinematic tells you the economy has changed. The map simply starts offering you a different future. 3
Trivia The original rules set a hard time limit of 255 turns. When that limit ends a battle, its record is not saved—an unusually stern reminder that even a slow chess match needs a clock. 3
Cities are engines, not scenery
In Famicom Wars, a property is never simply a flag to paint. A city pays 1,000 in military funds each turn and provides ground-unit production and supply; airports and ports pay 2,000 and handle their respective air and naval work; the base is the headquarters, paying 4,000 while also supporting ground forces. The manual makes the geography wonderfully literal. A town is an income statement. A port is an argument for crossing water. An airport says that a battle which looked local can suddenly have a high ceiling. 3
Capture is consequently the game’s most suspenseful non-combat action. Infantry and combat engineers can take facilities, but the headquarters itself can be captured only by infantry. The capture gauge rises according to the number of people in the unit, and requires a total of 20 people acting to fill. If the capturing unit moves away or disappears, the gauge empties. The rule makes a near-complete capture deliciously fragile. It is not enough to reach the square; you must protect the act of claiming it across the enemy’s reply. 3
Trivia A base’s 4,000 funds per turn are four times a city’s 1,000. The headquarters is therefore both the dramatic target and the strongest single economic address on the board. 3
Logistics is the plot
The original’s sharpest little cruelty is fuel. Ammunition drops when a unit attacks or counterattacks; fuel drops when it moves, and air units also consume it at the beginning of a phase. At zero fuel, a ground unit cannot move, an air unit crashes, and a sea unit sinks. Those are not decorative warnings. They make the distance between a road and a forest, or an airport and an exposed fighter, part of the calculation before the first shot is fired. A powerful unit can be a liability if the route home has vanished. 3
The answer is not a magic repair button. The command called All Supply spends military funds to replenish fuel, ammunition, and up to two machines or people for every eligible unacted unit on the player’s facilities; it may be used only once per phase. Supply vehicles can also replenish fuel and ammunition for adjacent, unacted ground units. This gives a mundane verb—resupply—the drama of a field command. Use it too early and you may waste its reach. Wait too long and the map itself has already punished you. 3 4
Trivia A supply vehicle can restore fuel and ammunition, but it cannot attack. In a game packed with weapons, one of the most consequential ground units is explicitly built to keep other units functioning. 3
Combat needs a postcode
The map’s geometry is not background art. Forests slow tanks and self-propelled guns but offer strong defence; mountains are high-defence ground for foot units; beaches also give infantry and combat engineers an unusually safe foothold; roads move units easily but offer less protection. Air units can travel over every terrain type, which sounds liberating until you remember the fuel clock. Every category of strength has an awkward square somewhere. 3
Combat itself is deliberately automatic, leaving the meaningful decisions before the animation. Direct attacks happen against adjacent enemies and invite a counterattack when the target can attack directly. Indirect attacks reach two or more squares, may not be made after moving, and do not receive a counterattack. This creates the basic rhythm of the board: armour pressing close, artillery asking to be positioned a turn early, and defenders turning good terrain into a reason the attacker hesitates. The game’s combat table is a guide, not a pardon; terrain changes the outcome. 3
Trivia A newly produced unit cannot receive orders until the player’s next phase. Building a force is therefore always an investment in tomorrow’s turn, never an emergency button for today. 3
A small army with big traffic problems
Famicom Wars is full of units that make sense only when they admit they cannot do everything. Infantry cross mountains, forests and rivers. Combat engineers hit harder than infantry but move less freely. The armoured personnel carrier takes one infantry or combat-engineer unit. Transport helicopters take one ground unit, while landing ships can carry up to two. Battleships reach three to five squares from the sea; the two self-propelled gun types fire at two-to-three and three-to-five squares. The map becomes a supply puzzle because every route has an appropriate passenger. 3
Joining weakened like-for-like units is one more way the game turns a square into a decision. A merge is allowed when at least one side has nine or fewer people or machines; the counts combine up to ten, while the better fuel and ammunition values are kept. But the merged unit is then marked as acted. The rule is modest, almost clerical, and that is its charm. Recovery costs tempo. A commander can tidy a damaged line, but cannot tidy it and also push that same piece forward. 3
Trivia The official unit list divides the arsenal into ground, air, and sea forces. The famous-looking tank is only one actor; a landing ship, a transport helicopter, or an unglamorous carrier can be the reason an infantry capture happens at all. 3
The fair fight is the drama
The most enduringly elegant choice in the Japanese original is its insistence that the two sides begin with the same equipment. Nintendo’s period description makes that equality explicit: Red Star and Blue Moon face each other across a strategic map of 15 regions with identical capabilities. That means a mission can become memorable without a character-specific trick. The distinction is authored by the place—how the islands connect, which property is exposed, who has to cross water, and who can turn an early capture into a production advantage. 2
The available battle selection supports that sense of a growing campaign rather than a single disposable puzzle. MobyGames records 17 maps in total, while Wars Wiki describes 15 maps with two additional maps unlocked by completing the campaign with either army. The numbers are less important than the feeling they produce: each island is another laboratory for the same balanced toolkit. You do not need a new rulebook every time. You need to notice a new bottleneck. 5 6
Trivia The original manual lets two human players take the Red Star and Blue Moon settings, then alternate control after every phase using Controller 1. Its rivalry is turn-taking in the most literal sense: plan, hand over the controller, and watch the other commander answer. 3
The origin still feels sharp
There is something bracing about how little this 1988 Famicom game needs to explain itself once a map opens. The icons are small, the palette is disciplined, and the objective is blunt. Yet every turn can contain a miniature story: a fighter that has enough fuel for one meaningful patrol, an infantry unit one safe square from a base, a battleship whose range suddenly matters because a landing ship has arrived, or an enemy city that is both money and a promise of future repairs. The original’s scale makes strategy legible without making it simple. 3
It also gives the game an unusual kind of warmth. Not sentimentality—its systems can be severe—but confidence in the player’s ability to infer. A property pays, a forest protects, a transport carries, an artillery piece needs an earlier decision, and a capture that is not defended can unravel. Famicom Wars turns those plain statements into personality. The pleasure is not merely winning an exchange. It is seeing the network of roads, facilities, cargo space and ammunition become a plan you can actually explain afterward. That clarity makes a defeat useful, too: the player can point to the square, the purchase, or the delayed supply decision where the campaign’s story bent the wrong way. 1 3
Trivia Donut Island's Red Star commander is not officially named Samus Aran. He is the 23-year-old Colonel Samusoon, shown in a helmet that makes the Nintendo in-joke unmistakable; the Japanese Nintendo encyclopedia treats him as a company parody while noting that the relationship is not formally stated. Blue Moon answers with Colonel Goemon, so the result screen becomes a small parade of Nintendo-flavoured aliases. 8
A few more screens
2 official imagesSources & image credits
Facts were checked against the links below. Official media remains the property of Nintendo and the relevant rights holders.
- Nintendo Classics: Famicom Wars Nintendo ↗
- Famicom Wars — Family Computer Nintendo ↗
- Famicom Wars Instruction Manual Nintendo ↗
- Virtual Console Famicom Wars: Commands Nintendo ↗
- Famicom Wars (1988) MobyGames ↗
- Famicom Wars Wars Wiki ↗
- Former Nintendo developer Satoru Okada on the creation of Famicom Wars 4Gamer ↗
- Colonel Samusoon Nintendo Encyclopedia Wiki ↗
