Gary Grigsby's Pacific War

The game manual opens with words that sound like a warning today: "To understand the war in the Pacific, you must understand logistics." In the nineties, that was bad news. Gary Grigsby's Pacific War from 1992 sells you logistics so thoroughly that you'll be taking notes on paper during the first hour.

It's an ambitious simulation of World War II in the Pacific region — from Hawaii to the Australian coast. Your task is either to defend American positions or seize them for Japan. The game won't let you scribble anything into a pre-made mission. All the technological aspects, industrial production, supply transport, ship repairs, the time needed to move units — it's all part of the calculation. The computer remembers every tank, every duck in the fleet, and every liter of fuel in storage.

You play on hexagonal tiles on a large-scale map. Top-down view, cumbersome menus, boredom from monochrome DOS window colors. Animations don't exist. A single turn can take ten minutes if the computer is calculating maneuvers. Even though you're used to turn-based strategy, here you miss chained commands and automation. You have to click manually, over and over again. When a soldier moves across the ocean for five weeks, you watch him step by step.

Yet — and this is crucial — the game draws you in. There's no glamour here. No animated scenes, no trumpet fanfare. Just black and white tactics that make you think. A logistics mistake will cost you another month. Underestimating air power means losing control over the archipelago. The decision of whether to send ships to Guadalcanal or Bougainville has no single right answer.

Today, Pacific War is still playable in a browser via DOSemu. The graphics won't entertain you even in a figurative sense — it's a work desk. But when you understand why that form exists, when you feel the weight of every decision, the game becomes interesting. It's not a board game converted to a computer. It's a computer that doesn't care if you like it.