Battle of the Bulge - Tigers in the Snow

It's supposed to be a battle, yet practically nothing happens on screen. That's the impression Battle of the Bulge – Tigers in the Snow gives when you first launch this 1982 strategy game. The game field is a bare map, units are small square symbols, and everything looks like someone drew a war on graph paper with a pencil. What's missing? Animation, colors, anything to keep the eye engaged.

It's a simulation of the German offensive in the Ardennes from 1944, one of the Third Reich's last major offensives. As commander, you either control German units and attempt to break through the Allied defense, or stand on the side of the Americans and British in the role of defender. The game accounts for logistics, weather, troop quality, and terrain. It all makes sense – it's one of the first computer games to attempt simulating strategy at such a detailed level.

You play in turns. You issue orders, the game calculates the result according to its internal rules, and then it's your turn again. Visually it's nothing special – but that's precisely why the game forces you to think. You don't see animated tanks rolling across the map with fancy explosions. You see numbers, distances, and logic. Control is cross-based, sometimes you have to input commands textually. Today that would cause a revolution in geriatrics, but in the eighties it was simply all that was available.

This game isn't fun in the modern sense of the word. It's not an adrenaline rush. It vaguely resembles playing a board game through correspondence – sometimes it takes hours before you figure out where you went wrong tactically. Yet that's precisely its charm. There was a breakthrough once in the eighties – someone figured that a computer didn't have to be just entertainment, but could be a tool for experimenting with military logic.

Playing it in a browser today means one thing: you want to understand how strategy was written on computers back when even a video card couldn't handle color. The game can't be played casually. Demanding, lengthy, and coldly coded – exactly what engineers and soldiers expected from a computer in 1982, not kids who wanted their eyes to light up.