Argomenti trattati
My familiarity with classic strategy games shaped why I wanted to revisit Koei’s earliest tactical effort. As someone who grew up enamored with Sid Meier’s Civilization, I first experienced that franchise through a SNES port made by Koei, at a time when PC compatibility was unreliable and DOSBox did not exist; console ports were often the most practical route to play. That background made me both curious and skeptical about Koei’s larger catalog, which today looks far broader and more Japan-centric than I appreciated in the 1990s.
Koei churned out a huge number of titles for Japanese PCs, many of which never left Asia. Their breakthrough grand strategy, Romance of the Three Kingdoms (1985), is well known, but the company’s documented earliest surviving work is a tactical wargame called Kawanakajima, originally for microcomputers like the PC-8001 and PC-8801. A Steam re-release surfaced an “original” mode emulating the PC-8801, though it omits a particularly punitive mechanic. Thanks to a translation by RPG Codex member Helly I was able to play in English while deliberately enduring the version’s authentic frustrations.
How the battlefield is presented and why it matters
The game presents a narrow window onto a much larger battlefield: a 400 by 400 view inside a 2000 by 2000 playfield, centered on Takeda Shingen. Distances are conveniently measured in units I call Chō (about 360 feet or 110 m), and movement is capped: infantry travel 200 Chō per turn while cavalry can go 500 Chō. That scale shapes every decision, but the more crippling design choice is the way the view updates. A unit must spend its action to refresh the display and report what it can see, so a force that moves cannot simultaneously reveal its surroundings. Worse, initiating an attack reveals enemy locations in textual form only, not by updating the graphical map.
Because of that constraint I relied heavily on external tracking: a spreadsheet where I logged coordinates and calculated trajectories. Units in the game move freeform and the system uses a polar-style notation that I tracked as θ/Δs; with many elements moving simultaneously, the Excel sheet functioned as command-and-control. That bookkeeping is anachronistic but unavoidable given the interface: a unit that scouts and a unit that fights are mutually exclusive from an information standpoint.
Reconnaissance, early clashes, and the scent of the enemy
The initial plan focused on locating Uesugi Kenshin by sweeping the northern half of the map while keeping two reserve companies in hand. The first few turns were pure reconnaissance: horse companies pushed far forward and spearmen and gunners probed more cautiously. On turn two several of my forward companies reported contact and were quickly pinned, including the 10th spearman and the 17th infantry. I attempted to rally support while keeping scouts moving, but the lack of a live overview cost me precious reactions.
By turn three the scouting probes had escalated into pitched fights. Three infantry were lost in the north and three spearmen in a southern clash; a gun company nearly collapsed. The pattern continued: turn four saw both gun companies destroyed and enemy fire on Shingen’s rearguard, while my cavalry reached the northern edge. A lucky alert revealed that horse company #8 was engaged by enemy unit #1 at the map’s north rim, confirming Kenshin’s position. From that moment the fight began to coalesce around a finite number of enemy stacks rather than a fluid screen of contact.
Concentration, attrition, and the final approach
With the enemy identified I shifted to a concentrated assault. I massed troops near Shingen’s northwest guard and ordered a delayed converging move: mobile elements would close to a point roughly 500 Chō south of the enemy and then strike together. The clustered defense proved effective on turn six; units that drifted too close were shredded while those who held back could only fire ineffectually. Several Uesugi infantry companies were destroyed and my guards absorbed rudimentary counterfire, including a grazing hit on Shingen himself.
The middle turns became a grinding exchange of limited gains and heavy casualties. I lost cavalry and archers during the rushs and the defenders at the gate took heavy punishment, but my horse companies eventually linked up with the main column. On the penultimate turns my forces eliminated remaining units at the gate and stacked 230 Chō south of Kenshin. The enemy guards delivered lethal volleys that killed a few companies, but in the end a concentrated assault on turn eighteen killed Uesugi Kenshin and ended the engagement despite the stubborn defense.
Design strengths and frustrations
Kawanakajima is an instructive artifact. It shows early ambition in merging strategic scale with tactical positioning, and the game contains moments of cleverness in range and movement mechanics. Still, the interface choices—principally the need to spend an action to update the visual window—create a gameplay rhythm that feels dated and punishing. The Steam re-release removes that particular pain point, and during a follow-up attempt I found the map’s limitations less obvious. Overall I give the title a below-average GAB rating: not hateful, but primitive and shallow compared with later Koei efforts.
What comes next
This battle was a warmup for bigger historical systems: Nobunaga’s Ambition awaits, and because it was never officially translated I will try it in Japanese. Kawanakajima fed my curiosity about Koei’s evolution from compact microcomputer wargames to the sprawling grand strategies they later popularized. The experience reinforced how translation, emulation choices, and a little spreadsheet work can convert an awkward historical simulation into a satisfying, if bruising, playthrough.