Drive on Moscow

I have a soft spot for wargames that respect your intelligence without demanding a 400-page rulebook, and Drive on Moscow sits squarely in that narrow band. The premise is Operation Typhoon, late 1941: the German push to seize Moscow before a Russian winter swallows the Wehrmacht whole. You pick a side, manage a sector-based map of roughly 600 kilometres of front, and live or die by decisions made at the impulse level. That last word matters more than anything else in this game. The impulse-based activation system is the mechanical heart of the whole thing. Each turn you activate a single sector, moving and attacking with whatever units occupy it, and once that sector is spent it is done for the turn. Miss a unit, forget a flanking panzer, and that mistake echoes. The rhythm is closer to chess than to the IGO-UGO conventions most wargame veterans grew up on, and it takes a couple of sessions to stop second-guessing the sequencing. Once it clicks, though, the decisions cascade in genuinely interesting ways: do you push the armour forward to threaten supply, or consolidate infantry to hold a forest zone? Germans face a hard clock as weather shifts from offensive conditions to frost and then deep snow, progressively restricting movement to one zone per turn and bringing Soviet Siberian reserves onto the board. Russians, meanwhile, are historically outgunned at the start, but fast cavalry can harass overextended German supply lines and a patient Soviet player can grind the Wehrmacht to a crawl through attrition rather than direct combat. The asymmetry is deliberate and historically grounded, and it produces two genuinely different strategic experiences under the same ruleset. The four scenarios deserve mention specifically. Three shorter campaigns cover the initial German assault, the final push, and the Soviet counteroffensive as standalone sessions, each completable in a single sitting. The fourth combines all three into a full campaign of roughly twenty turns for anyone wanting the complete picture. That structure is smart design: it gives newcomers a low-commitment entry point while giving veterans something substantial to grind through. The map changes visually with weather conditions, shifting hue from autumn mud to frost to snow, and the seasonal sound design adds genuine atmosphere without becoming intrusive. The UI itself won awards on the original iOS release and that pedigree shows; reading the board, checking odds, and committing attacks are all handled cleanly without extra clicks. The AI holds up better than in many indie wargames. Multiple AI personalities exist for both Axis and Soviet commanders, each behaving differently enough that early sessions feel genuinely competitive. Experienced players will eventually start reading the AI's tendencies, which is the genre's oldest problem and not unique here. The real longevity comes from PBEM-style online multiplayer through Slitherine's servers, where human opponents close that gap entirely. The tutorial leans text-heavy, which will frustrate visual learners, and there is a known terminology inconsistency where impulses are sometimes labelled as turns within the UI itself, creating confusion for newcomers who have not read the manual carefully. These are real friction points, not dealbreakers. For anyone asking whether a wargame this focused is worth your time in 2025: the answer depends entirely on appetite. This is not a grand-strategy sandbox. It does one battle, at one scale, with four scenario lenses. If that sounds limiting, look elsewhere. If it sounds like exactly the kind of concentrated, historically grounded decision-making that most sprawling strategy games dilute, Drive on Moscow earns its place on the shortlist without difficulty. Diego, Scout Team

Runs flawlessly on Linux out of the box. Based on 3 ProtonDB community reports.

Be the first to comment on Drive on Moscow.