Ultimate General: Civil War

There is a specific kind of cowardice in strategy game design, and it looks like a hex grid. For forty years, the wargame has protected itself from outsiders with a wall of counters, stacking rules, and combat-resolution tables — a genre that mistook opacity for depth. Ultimate General: Civil War, released July 14, 2017 by Game-Labs, is the rare entry that looked at that wall and decided to knock a door in it.

The pitch is simple on its face. You take command of the Union or Confederate army across a branching grand campaign of major and minor engagements, from Bull Run through to the war’s grinding conclusion. You fight in real time with pausable command. And instead of clicking individual units and issuing movement orders like it’s 1998, you draw — a line across a ridge to form a defensive front, a sweeping arrow around a treeline to send a division on a flanking march. The army reads your intent and executes it.

That single design decision is why this game still matters years after launch. Game-Labs didn’t simplify the wargame. They found a better interface for it.

Market positioning is unambiguous. This is not Total War, which wraps its battles in a 4X empire-builder and sells on spectacle. It isn’t the Scourge of War school of hardcore simulation either, where you squint through a colonel’s field glasses and accept that confusion is the point. UG:CW occupies the middle — operationally serious, historically rigorous, and mechanically legible — at a price point well under a AAA release, from a small studio. It is single-player only, on Windows and macOS via Steam, with no console or mobile version and no multiplayer of any kind. In 2017 that was a conspicuous omission. Today it reads as a deliberate statement about where the studio’s finite resources went: into the battles themselves.

• Draw-to-Command Control: The headline mechanic. Drag a line to deploy a brigade along a front; draw an arc to order a flanking maneuver. You express intent rather than micromanaging waypoints, and the game translates it into coordinated regimental movement. It is the design’s defining strength.
• Delegated Division Command: Assign high-level objectives to division commanders and they execute semi-autonomously. This is the feature that makes multi-corps late-game battles playable rather than a carpal-tunnel endurance test — you stop being a company clerk and start being an army commander.
• Persistent Army & Officer Corps: Surviving soldiers convert from green recruits into veterans between battles. Officers earn promotions, take wounds, and die permanently. Your army accumulates a biography, and losing a veteran brigade hurts in a way no casualty counter can manufacture.
• Hand-Drawn, Map-Accurate Terrain: Battlefields built from period maps and satellite data, spanning hundreds of square miles. Hills grant genuine sightlines. Forests conceal movement. Rivers and fences anchor a line. Terrain is not decoration here; it is the primary variable.
• Branching Grand Campaign: Major battles plus dozens of minor engagements, with outcomes shaping what you fight next and how large an army you’re permitted to field.
• Period-Accurate Procurement: Between battles you recruit brigades, buy weapons by make and model, and assign officers — scaling from a handful of regiments to multiple corps as your reputation grows.

The Gameplay Loop

UG:CW runs on two clocks. The fast one is the battle: real time, pausable, typically thirty to ninety minutes, occasionally stretching across multiple in-game days. The slow one is the campaign, where the consequences of each battle compound into an army you either built carefully or hollowed out through attrition.

The battle loop is where this game earns its reputation. You arrive on a map you cannot fully see, with a rough objective and an enemy somewhere beyond the treeline. Scouting matters. Elevation matters enormously — getting a battery onto a ridge with clear sightlines can decide an engagement before the first infantry contact. You form a line, you anchor the flanks on something solid, and then the AI probes you.

And it probes. This is not a scripted opposition that marches obediently into your guns. It tests flanks, finds the seam between two divisions, and goes after supply lines with genuine malice. Leave a wagon train lightly covered and a brigade that was winning its firefight ninety seconds ago can find itself out of ammunition. The AI’s aggression is the most consistently respected element in the game after the control scheme, and it is the reason this title has held an audience for years.

Morale is the real resource. Units don’t fight to the last man; they break. A brigade taking fire from the front while a regiment appears on its flank will rout long before its casualty count justifies it — which is precisely, historically correct. Your job is not to kill the enemy army. It is to convince it to leave. Once that clicks, the entire game reorganizes itself in your head, and the flanking arrows stop being a control gimmick and become the whole thesis.

The Control Scheme, Seriously

It’s worth being specific about why drawing works, because “intuitive controls” is the kind of phrase that gets thrown at anything with a tutorial.

Conventional RTS command is a translation problem. You have an intention — this division should swing right through the woods and hit their exposed flank — and you must decompose it into a sequence of unit selections, move orders, and formation toggles, then babysit the execution. Every step leaks intent. UG:CW removes the translation layer. You draw the arrow. The division goes.

The second-order effect is what matters: because issuing orders is cheap, attention goes to reading the battlefield instead of operating the interface. That is a profound shift in where the cognitive load sits, and every wargame released since should have stolen it. Most didn’t.

Delegation extends the idea upward. By the late campaign you may field multiple corps across an enormous map, and hand-steering that is neither fun nor plausible. Handing a division commander an objective and letting them work it — imperfectly, sometimes frustratingly — is both better design and better history. Your subordinates are not extensions of your will. They are people with partial information doing their best, which is exactly the problem every Civil War general actually had.

Where It Falls Down: The Campaign Economy

Now the bad news, and it’s real.

The between-battles layer is opaque to the point of hostility. You manage recruitment, weapon procurement, officer assignment, and army expansion through menus that tell you what things cost but not what they’re worth. How much does army size scale with reputation? What’s the actual trade-off between a large green brigade and a small veteran one? Should you spend on rifles or bodies? The game declines to say. The community has reverse-engineered the answers across years of forum posts and wikis, which is a polite way of saying the game outsourced its own documentation to its players.

This isn’t difficulty. It’s missing information, and the distinction matters. A hard game tells you the rules and dares you to beat them. UG:CW hides the rules and then punishes you in battle forty-five for a procurement decision you made in battle six, with no indication of where you went wrong. New players can build structurally unviable armies, wonder why the war suddenly became unwinnable, and restart.

The tutorial is thin — it covers the click-and-drag basics and then abandons you. Nothing prepares you for the campaign layer at all.

Difficulty balance is the other genuine fault line. Colonel, the entry tier, is too soft for anyone with strategy experience. The upper tiers don’t just get harder — they snowball. Because the AI’s force pool scales against your performance, a strong early run can inflate enemy strength faster than your veteran core can absorb losses, producing a mid-campaign wall that feels less like escalating challenge and more like being punished for competence. Some players love the pressure. Others, reasonably, find it arbitrary.

And there is no multiplayer. Not a stripped-down mode, not asynchronous play — nothing. For a game whose core mechanic would make head-to-head command genuinely thrilling, that absence stings more than the feature list suggests.

The aesthetic is a deliberate bet, and it pays off. Rather than chase 3D armies the studio couldn’t afford to animate convincingly, Game-Labs went with hand-drawn maps rendered in a restrained, period-appropriate palette — something closer to a general’s campaign map than a cinematic battlefield. Zoom out and you’re reading a historical document. Zoom in and unit blocks maneuver across terrain that is legible at a glance: where the ridge is, where the trees end, where the fence line runs.

That legibility is a functional achievement, not just an artistic one. In a game where terrain decides engagements, being able to instantly parse elevation and cover is worth more than any particle effect.

Performance is the upside of that restraint. A 2D-forward game of this scope is light on hardware by design, and the engine was built to handle thousands of men without the frame-rate collapse that afflicts more ambitious 3D approaches.

The UI is the weak link, and it was dated on arrival. The campaign screens are dense, small-text, low-contrast panels that look like internal tooling — functional, unloved, and badly suited to high-DPI displays where text gets uncomfortably cramped. Information you need constantly sits two clicks deep. Information you barely need occupies prime real estate. With limited post-launch support, the UI’s problems are now permanent features rather than things to wait out. Form didn’t lose a war to function here; form never showed up.

Steam, Windows and macOS, single-player only. There is no console or mobile version, and given how thoroughly this design depends on a mouse, that’s the right call.

The draw-to-command scheme is fundamentally a precision pointing device mechanic. Sweeping a flanking arc across a mile of ground, adjusting a defensive line by a few degrees, dropping a battery on exactly the right contour — these need pixel accuracy and a clean click-drag-release. A thumbstick cursor would gut it. Touch would be closer in spirit but fails on precision and on the constant hover-to-inspect reads the interface expects.

Mouse and keyboard is therefore not a concession; it’s the platform the design was built for. Play windowed or at a moderate resolution if your display is 4K — the UI does not scale gracefully, and on a high-DPI panel brigade stats get hard to read.

The macOS build is a genuine inclusion rather than a checkbox, which is notable for a wargame; this is a historically Windows-exclusive genre, and Mac strategy players have few alternatives this serious.

Steam’s side of the ledger: no Workshop, but a healthy modding scene distributes elsewhere, and mods have meaningfully extended the game’s life in the absence of developer updates. Cloud saves and achievements work as expected. A single campaign runs long — dozens of hours — so the cost-per-hour math at $29.99 is generous even before a sale.

• Hardcore strategy fans who want operational depth without memorizing a combat-resolution table — this is the genre’s strongest case that rigor and accessibility aren’t opposites.
• Civil War history enthusiasts who care that the ridge at Gettysburg is the actual ridge, and who will feel something when a veteran brigade they’ve shepherded for a long campaign breaks.
• Lapsed Total War players frustrated that battles have become set-piece spectacle. The tactical layer here is deeper, and nothing is wasted on campaign-map politics.
• Mac strategy gamers, who have almost nowhere else to go for a wargame this serious.
• Not for players who need multiplayer, want a polished onboarding ramp, or expect the game to explain its own systems. Budget ten hours to stop being bad at it, and read a community guide before your first campaign — that’s an indictment of the game, but it’s also the correct advice.

Ultimate General: Civil War is a flawed game with one important idea, and both halves deserve the description.

The flaws are structural and will never be fixed: an economy that hides its math, a tutorial that quits early, a UI that looked tired in 2017, and a difficulty curve that can turn on you for doing well. Years of thin post-launch support mean every one of those is now load-bearing. Anyone who bounces off this game in the first five hours has a legitimate grievance, not a skill deficiency.

But the thing at the center matters. Game-Labs identified that wargaming’s barrier to entry was never conceptual difficulty — it was interface friction, decades of it, mistaken for depth. Then they built a control scheme that removes the friction without removing a single tactical consideration, and proved the theory across historically faithful battlefields where terrain, morale, and a nasty flanking AI do all the work that rules overhead used to pretend to do. The draw-an-arrow mechanic should have become the genre standard. That it mostly hasn’t is the industry’s failure, not this game’s.

What you’re buying, then, is a sharp tactical engine wrapped in an unfinished management layer. For the right player, the engine is worth the $29.99. A single campaign will take dozens of hours, the army you build will feel like yours, and specific ridges tend to stick in the memory. Go in expecting to consult a wiki and write off your first playthrough as tuition.

Push through the first ten hours. The game on the other side is the one worth recommending — to the right audience only.