Press "Enter" to skip to content

War in Russia – Ratings & Review

This image has an empty alt attribute; its file name is WarInRussia.jpg

After four games covering naval campaigns, Gary Grigsby moved to the other theme that would define his career as a designer: the Eastern Front. According to my database, by the time War in Russia was released in June 1984 there had been exactly 50 computer wargames on WW2, but only two covered the entirety of Russia (Panzers East! and Chris Crawford’s Eastern Front 1941), and of those two none covered more than one year of war. Crawford pondered covering the entirety of the Eastern Front in his game, but he soon found it better to focus only on the first year. Later, Crawford added a 1942 scenario, but as an independent module – his code never supported the transition from winter to spring.

In addition to covering a longer timeframe than its closest competitors, War in Russia digs deeper: Eastern Front 1941 was played at the Corps level, whereas War in Russia tracks units down to the division level. I estimate that on a modern computer with fast emulation, a campaign may last anywhere between 8 (early finish) and 25 hours (for a 1941-1945 playthrough). This is the same order of magnitude as the time it takes to play the latest Hearts of Iron – and that’s before taking into account the speed of 1984 computers. War in Russia may have well been the real first monster wargame on computer.

Of course, the reference Monster Wargame nowadays is Gary Grigsby’s War in The East and its 200+ hours necessary to finish the main campaign. It is a distant successor to War in Russia.

The development of War in Russia started in the summer of 1983, still in BASIC, and according to Joel Billings the game was “working at the basic level” in September 1983. The balancing values were still placeholders, as Grigsby remembers having done most of the historical research later in October 1983, during a trip to the Grand Canyon. The game was therefore ready in late 1983, and started its final QA and balancing pass while Grigsby as usual started working on the next project – Objective Kursk.

When we think “QA” nowadays, we imagine a dedicated team with cheat codes, logs and other QA tools. But of course, in 1984 “QA” in SSI meant “Joel Billings, Paul Murray and a bunch of friends playing the game as normal people“. All those people had jobs, and as I said War in Russia is long. In March 1984, the team found a critical bug in the combat formula – a bug so bad that all the tests on the balancing had to be thrown out, and the iterations restarted from scratch. Objective Kursk meanwhile had also reached the testing/balancing phase – it was after all using the same engine as War in Russia – and because it had a much smaller scope its QA and balancing was much shorter! Objective Kursk, started 6 months after War in Russia, ended up being released one month before the latter in May 1984 – though Billings ponders whether it may have been held an extra bit to let Murray finish the Atari (Assembler) port of the game – not the initial plan but given the game was already late there were benefits to releasing the two versions together.

The beginning of the 1943 scenario on Atari. Being in Assembler, it is incredibly faster than the Apple II version – if I had known I would have played this one.

Despite the scope of War in Russia and the time it took to develop it, it is obvious that Grigsby had hoped to add more and for one reason or another (balancing? lack of time? memory size?) some content was removed. This is particularly obvious in two features: supplies and division types.

Let’s first talk about supplies. It is remarkably simple: at the beginning of each turn the player has a number of “depot units” they can move through railroads and open terrain and which can once each supply all units within two squares of them. Yet, if you read the manual, this is much more complicated: each division whose fatigue is not 0 consumes “supply points” (1 for infantry, 2 for non-infantry ) and if there are no more supply points then supply time is over. This does not seem to have been implemented however, or rather it seems to have been implemented and then balanced out of the game. The Axis generates 225 supply points, for a cap of 199 divisions and not more than say 40 non-infantry divisions (I ended the game with 34) so the maximum supply you could ever possibly need is around 240. Obviously, I never reached that cap and rarely needed half that much: my units were often too spread to be all supplied, and a good chunk of my infantry was holding position and not fatigued. As for the Soviets, they generate 425 supply points every turn and of course they won’t be needing all that either.

Each star represents one supply point spent, so I was worried at first when I saw that. I shouldn’t have, and the game does not even bother telling you how many supply points you have left.

The supply system may have been effectively cut, but for my second topic – the division types – it is obvious that Grigsby could not go as far as he planned. War in Russia includes 35 division types. Some are “foreign” (Finnish, Romanian, Slovakian, etc…) but most are variants of Soviet and German units (eg Mountain Infantry vs Regular Infantry). The player does not choose which variants they build, instead they pick the general category (“infantry”, “mechanized”) and the game automatically determines whether the player receives a rifle division or an inferior cavalry division, a panzer division or an inferior motorized division… Those “inferior” divisions have no advantage over their normal counterparts, they’re just worse and in some cases will remain so until the end of the game.

The list of divisions and the list of how the computer can screw you over when you build one.
As the game progresses, most divisions upgrade to another (eg Motorized Divisions are converted to PanzerGrenadiers [PZG]), but the German mountain divisions will remain stuck in 1941.

Each type of division has its own “upgrade” rule, but otherwise their behaviour on the field is fully dependent on their type (with two exceptions: Finns refuse naval transports and the Italian Motorized division behaves like an infantry division). I suspect that Grigsby wanted to give more specific rules to specific divisions – maybe make cavalry more mobile than infantry, mountain divisions fight or move better in difficult terrain – else it was a lot of effort just to frustrate the player. In any case, Objective Kursk would certainly go down to the level of the division – and even to the individual vehicles – for combat resolution, so clearly the idea was floating in Grigsby’s head.

Me: “I need an infantry division”, Hermann Goering: “Say no more, fam”
The Luftwaffe divisions being a waste of perfectly good division slots is realistic and I liked that.

In any case, SSI knew it had something different with War in Russia and sold it at the new high price point of $79.95 (no game had passed $59.95 before that), and still at that price you did not get any goodies in the box: only the game, a manual and a map – the real value was in the disk.

1942 – Case Blue

I had a high opinion of my 1941 campaign, but it is generally easy to make Barbarossa scenarios fun: the player keeps winning and advancing and as the designer you can even have the carrot that if the player advances fast enough they may end the game here and there. That’s why I wanted to try the 1942 scenario: Case Blue. I also tested a higher level of difficulty.

The map started with a frontline spanning from Leningrad (encircled) to Rostov. The Soviets have significant mechanized reserves behind the front, the Axis have not.

The start of the scenario in June 1942.

The scenario follows the historical deployment so naturally I expected the Soviets to be weaker in the South. I spend several turns transferring all my motorized and Panzer divisions South to Eastern Ukraine, then attack. As expected, the Soviet units were smallish, sometimes 2-divisions only, and I breached easily. In August 1943, I reached Stalingrad. So far, historical.

August 1942 – I reached Stalingrad and cut its supplies with a motorized division just North of Grozny.

Instead of assaulting Stalingrad – I have seen the movie, I knew how it ends – I pivoted North. My objective was to isolate the Soviet units on the frontline from their supplies coming from the East. As soon as possible, I sent lone motorized divisions to cut the Soviet railroads. Sometimes, the Soviets chased them, more often they did not. By October 1943, only two supply depots,coming from Archangelsk reached the Soviet frontline every turn. The units I sent forward were weak, but I was building a rail lifeline. The Soviets did not really try to escape from the encirclement, all they did was mobilize new mechanized divisions and attack my breakthrough from the East.

October1942: I had to fall back a bit around Leningrad, and my corridor behind the enemy line was threatened on both sides.

This battle lasted for most of the winter, with the Soviets occasionally reaching my railroad and stopping me from building further (particularly when I am under the Very Cold effect). Still, I eventually prevailed: all my Panzer Corps were allocated to this battle whereas the Soviets had stopped bringing reinforcements for reasons I don’t understand: as I checked later, they still had the reserve to build units. Possibly the computer earmarked those reserves to reinforce existing units, but of course could not reinforce any as I had isolated so many of them.

By the end of winter in March my trains could ride as far as Gorki, East-North-East of Moscow. The last supply lifelines of the latter was cut and it was then totally isolated, along with all the Soviet units in the middle of the map.

March 1943. I opportunistically took Stalingrad and started to eliminate some of the Soviet units which had been without supply since October.

The game was effectively won. The last dynamic action took place between Saratov and Kubyshev where I surrounded and destroyed the remaining Soviet mechanized divisions. Everywhere else, I just had to attack enough: I could resupply and reinforce and they could not. I eventually won the game on October 1943, 67 turns after starting the campaign.

October 1943. Victory! Leningrad still stands, and the Russians were building up a bit in the Caucasus, but too little and much too late.

This was again fun, though not quite as much as the Barbarossa scenario – possibly because I knew how to trick the AI. I won’t be doing the 1943 scenario: the Kursk campaign is my least favourite and Objective Kursk is coming soon anyway. Let’s move to the ratings!

Ratings & Reviews

It was not really two years.

War in Russia by Gary Grigsby, published by SSI, USA
First release: June 1984 on Atari and Apple II
Genre: Land operations
Average duration of a campaign : 5-10 minutes by turn, almost 200 turns for the longest campaign.
Total time played : 25-30 hours
AAR: Part 1, Part 2
Complexity: High (3/5)
Final Rating: Three stars
Ranking at the time of review: 2/131

A. Presentation

Adequate. Not much to say here. If someone had told me to imagine a “strategy game from the early 80s“, I would have envisioned exactly War in Russia. Nothing stands out, but it does the job.

B. UI, Clarity of rules and outcomes

Acceptable. War in Russia has the typical issues of SSI games: you will need to check the manual regularly as key rules are not repeated in the game, and said manual is not as clear as it could be (information pertaining to the same copy can be distributed in different parts). The game also obfuscates some important information: you cannot check your units’ supply level when distributing supplies, you cannot see the fortification level of units you’ve just attacked.

It is also easy to make a mistake that costs you. To take the worst example: the game splits movement between tactical and strategical. Tactical orders are given through a dedicated command menu, whereas strategical commands are given “by default” from the root unit menu and override the tactical commands – so guess what kept happening after I gave tactical orders and wanted to move to the next unit.

Still, War in Russia is really playable for a game of its complexity. I appreciate some efforts to automatize supplies (you can order them to go to the last place you sent them last turn). That’s not a lot, but I don’t remember any other game doing that.

C. Systems

Quite good. The game has a lot of features, not all of them work well and some are pointless (eg you can choose where to build your industry, but there is no reason not to build them directly in Germany), but the game works and given the number of moving pieces, the hundreds of divisions, the size of the map, that’s impressive.

Do you want to build your factory somewhere where you can lose it, or somewhere where you can’t?

I feel I’ve already explained how the game works during the AARs, so I will only focus on two items that stand out:

First, the tactical part works due to the fortification rule. Each unit has 50% to fortify every turn, adding 20% to its defence at every level of fortification (maximum: 5), levels of fortification they can lose when attacked. More importantly, units that are still fortified cannot retreat, whereas units without fortification are easy to push back (a 1.5:1 ratio can be enough, which is easy to muster as attacks can be done from several hexagons and defence from only one). This means that if you put in the effort, you can push almost any unit from any location in a few turns – and so can the Soviets when Winter comes. It keeps you on your toes, makes the game dynamic and gives you theoretically a real choice on your strategy.

The two rules that make the game go round.

Of course, pushing one unit away is not going to help you much, because you need to create a passage 3-hexagons wide to have your railroad. And that brings me to the second thing I want to mention: : BOY DID I LIKE BUILDING MY RAILROADS. Every turn I laid out that new piece of railroad, I had new tactical options, new degrees of freedom. All my strategy, all my tactics became about pushing the railroad forward. I had a moment of elation every time I could chase the Soviet occupying the piece of land on which I wanted my train to pass. The railroad really tied the game together.

The game I was really playing in my head, but “East” rather than “West” and sans the financial shenanigans.

D. Scenario design & balancing

Quite good. The game comes with 3 scenarios with short/long variation which is generous for the era. Additionally, increasing difficulty triggers ruleset changes rather than simply more/stronger Soviets, which I appreciate – and even then the additional Soviets are not created from thin air but are extra Siberian divisions coming to defend the Motherland.

On the other hand, the AI is weak: it barely attacks except in cold/very cold weather (that’s one of the things I wanted to check by playing the 1942 scenario until 1943) and for a game so focused on supply lines it manages them horribly: it pushes its supply depots as far as possible (even if it means not supplying units on the way), always using the same routes (making them trivial to block) and it barely reacts when its roads are cut. That’s a bummer, but given you still need to pierce the front before falling on the Soviet supply lines, there is still an interesting challenge for dozens of turns.

E. Did I make interesting decisions?

Yes, both tactical (including on where exactly I should put my new piece of railroad) and strategic – at least for the first half of each campaign. The second half was both times mostly about grinding unsupplied units.

F. Final Rating

Three stars. War in Russia is impressive for its era and still pleasant to play nowadays, if you can stomach the UI and unclear manual. While not as well-designed and tight as Eastern Front 1941, I found it more fun as it created more interesting tactical situations, and because of course you don’t build railroads in Eastern Front 1941. However, the number of minor issues and the weakness of its AI keeps it one category below Reach for the Stars, for now the only game to which I gave four stars.

Reception

War in Russia received few reviews – I suppose few were willing to test a game of that price and size – but the few reviews it received were lavish. Russel Sipe for instance reckoned in the December 1984 issue of Games: “Without a doubt. War in Russia is the most significant computer wargame release this year.“, and Bob Curtin states in the July issue of Analog Computing: “SSI is the premier house for computer war games, and War in Russia is one of the best in the house.” I found the latter review particularly interesting: Curtin sees two drawbacks to the game: the first one is the length of the game, the second one is the length of a turn “waiting” when playing against another human. Curtin has a solution though: “There is no reason why a player couldn’t make his move, save the game and transfer the file through a modem to a player elsewhere. Your opponent could then restart the game with this file, make his move, save the game and ship it back to you over the phone. I haven’t tried this yet, but it’s something I’m looking into.” That’s forward-looking indeed!

Computer Gaming World did not review War in Russia immediately, instead it published in August 1984 an article by Jon Cheche titled “War in Russia: the view of a playtester” with mostly advice in it, some trite and some valuable. I am amused that his advice for the Zitadelle [Kursk] scenario is that you are going to lose anyway (“it is more a study in futility“). In January and April 1985, Computer Gaming World published a replay of a multiplayer 1942 campaign between Kirk Robinson and Jay Selover. They only played 12 turns, and the front did not move much, possibly because Jay Selover focused on Moscow against an opponent who knew what he was doing.

On the right, the effect of Selover’s 1942 summer offensive. I don’t think the German player has a chance against a competent Soviet player in 1942 and this AAR vindicates me.

The first “real” review came from the wargame expert Evan Brooks in his 1987 coverage of all WWII wargames (“5/5 – despite problems with the artificial intelligence in the later stages of the war, […] this is an essential addition to the serious wargamer’s library“) – this review triggered an angry letter to the editor in October accusing Brooks of double standards and pointing out that there are problems with the artificial intelligence from the onset of the game: apparently if you let the AI keep Minsk in 1941 it does not trigger its routine to defend Moscow and you can snatch it from the South.

War in Russia was also a favourite of the Computer Gaming World leadership. In March 1988, the magazine introduced the Computer Gaming World World of Fame for games which consistently ranked among the first in the Readership Surveys – War in Russia was part of that initial list.

The fact that Grigsby landed 3 of the 10 initial games says a lot about his consistency, but also about Computer Gaming World’s readership. The Action/Adventure games are all RPGs, and honestly Bard’s Tale presence is a surprise to me.

In France, the (tabletop) wargame specialist Casus Belli praised it to the sky in November 1984 “The absolute wargame, the victory by KO of the diskette on the cardboard”, the review describes a unique experience that could never replicated on board, and describes the AI as very good. Disappointedly, its generalist competitor Jeux & Stratégie only gave War in Russia a 3/5 rating a few months later in February 1985. Finally, Tilt gave it a 5/6 rating in its December 1986 article on all contemporary wargames; no game received 6/6.

The last appearance of War in Russia was in the Computer Gaming World‘s list of 150 Best Games of All Time in 1996. It is ranked “only” 126th, but I let you check below between which illustrious games it is slotted:

Gary Grigsby managed to put 5 games in that list, second only to Sid Meier (7).

Despite its critical acclaim, War in Russia did not sell that much: fewer 7 000 copies in the US (4500 Apple II, 2500 Atari) – significantly less than Carrier Force (15 500) and of course than an RPG like Questron (34 000).

We’re done with War in Russia, the first game in a long line that would lead to Gary Grigsby’s War in The East. Now I must delve into its engine again – this time for Objective Kursk!

5 Comments

  1. Andnjord Andnjord

    One has to admire Gary’s consistency. Not only he kept on developing and refining essentially the same game for all those 40 years, but he even kept the exact same price! For those curious, $80 in 1983 adjusted for inflation is equivalent to $250 today. PC gaming was an expensive hobby back then.

    Considering how complex of a topic supply is even in modern games (and how few games get it right!), one can understand why he essentially threw in the towel back in those days.

    You mention that the German player has little chance against a competent Soviet player, why is that? And do you think it’s in keeping with the historical realities (a serious wargame shouldn’t really allow the German player to run to Samara in 1941) or goes beyond where the German player wouldn’t be able to come close to replicating the successes of the Heer?

    Also am very amused that you’re reviewing this just as I’m considering buying the latest War in the East 2, a fortuitous coincidence!

    Anyways, thanks for the great review of this historical milestone of wargaming!

    • I am happy you asked those questions. There was so much to say about the game I feel I only skimmed it in my article. About supplies, I feel it actually works better this way. The fact that you only have a limited number of supply depots (5 + the one in Finland) forces to choose which units you supply. Isolated units also “cost” you more (since one of your 5 supply depots will spend its turn supplying an isolated units). The loss of efficiency in rainy/very cold weather or when moving the units in hexagons without railroads adds the historical “seasonality” of the supply conditions for the Germans. Honestly, the game would have been worse-off with bean counting.

      As for the balancing, I think the 1941 scenario is balanced, but in 1942:
      – the Soviets have better infantry units (max strength 90 (120 for guards) for the Soviets, vs 70 (60 for Tier 2 allies) for the Germans)
      – the Soviets and the Axis have roughly the same number of mobile units, with a quality advantage for the Soviets: 100 to 150 max strength for the Axis, 130 to 150 for the Soviets [Tanks and Mechanized],
      – the Soviets have more production, AND Lend-Lease, so it will be easier for them to keep their mobile units at full strength,
      – the Soviets are of course in defence and fortified. An active human player will send 1-division corps to create a second line of defence. This way, when the first line retreats, it can fall back on the second layer with level 5 fortifications. Just transfer 5 of the 6 divisions to the small corps that fortified, and now the Germans must breach again.

      As for the Germans, their only advantages, beside a strong air force, is that they can count on huge gaps in the initial layout of the Soviet forces (small or depleted units South of Moscow and in Ukraine) and a bonus of +50% when their Motorized/Panzer units attack infantry in clear terrain.

      In my opinion, a Soviet human player will mend the first issue in 3 or 4 turns and has enough mechanized units to counter-attack whatever breakthrough the Germans achieve. In the Computer Gaming World AAR, Jay Selover did not even achieve to dig more than 3 hexagons into Soviet lines.

  2. WhatHoSnorkers WhatHoSnorkers

    Now that was an EXPENSIVE game! As always, another excellent review. Kudos!

  3. Seems like, at least partially, you’re now hitting some of the good stuff. 1984 is shaping up to be the year where if you can stand the UI, it offers some pretty fun games.

    Also, wow, I did not expect to see Deathtrack on the best game list. Not sure if there was any competition to it at the time, but I wouldn’t expect it to be remembered in 1996!

  4. Operative Lynx Operative Lynx

    I wonder how much overlap there is between the group of people who like to play strategy games and the group of people who like to build railroads.

    The reader could get a sense from your AARs that Grigsby had to do some compromises, especially with the supply system, and it seems to really have been the case, which is a testament to your ability to convey essential information in your writing. In overall, this monster must have really strained the limits of 8-bit machines, thus the need for all those cuts.

Leave a Reply

Your email address will not be published. Required fields are marked *

The maximum upload file size: 128 MB. You can upload: image, video, document, spreadsheet. Links to YouTube, Facebook, Twitter and other services inserted in the comment text will be automatically embedded. Drop files here