Foxhole

Most multiplayer shooters hand you a rifle and a full magazine. Foxhole hands you an empty factory and a country to lose.

Developed by Siege Camp — the Toronto studio formerly known as Clapfoot, which spent a long stretch in Early Access before its 1.0 launch on September 28, 2022 — Foxhole is a persistent, top-down, massively multiplayer war game in which thousands of players split into two factions, the Colonials and the Wardens, and fight a single continuous conflict that can run for weeks. There is no campaign. There are no NPCs. There is no matchmaking queue that dumps you into a ten-minute skirmish and resets the scoreboard. There is a map of hundreds of towns, a front line that moves, and a war that ends only when one side is broken.

What separates Foxhole from every other entry in the multiplayer-shooter category is the closed loop of its economy. Every rifle, artillery shell, fuel canister, sandbag, and armored vehicle in the war is manufactured by a player, moved by a player, and fired by a player. Nothing spawns. Nothing respawns. If your frontline garrison runs dry of 7.62mm, it is because somebody a hundred kilometers behind the line didn’t refine enough salvage, or a truck convoy got ambushed on a coastal road, or the rail line into the region was never built. The consequence is that Foxhole is not really a shooter with logistics attached. It is a logistics simulation with a shooter attached, and the sooner a new player internalizes that, the sooner the game stops feeling broken and starts feeling coherent.

Its market position is strange and enviable: it has no direct competitor. Eve Online is the nearest philosophical cousin, and Eve is a spreadsheet with spaceships rather than a sandbox with trenches. Its Steam reception sits at Mostly Positive — a split that says less about quality than about the gap between the players who found their regiment and the players who bounced off early.

• A Fully Player-Driven War Economy: Scrap is mined by players, refined into components and construction materials by players, converted into weapons and vehicles at player-run factories, and hauled to the front by players. There is no infinite ammo box anywhere in the game. This single design decision drives everything else.
• Persistent, Multi-Week Campaigns: Territory captured tonight is still yours tomorrow. Craters stay cratered. Bunker networks stay built until somebody shells them flat. A war is a continuous historical event with a beginning, a middle, and a documented end — not a match.
• Genuine Combined Arms: Tanks require a driver and a dedicated gunner. Artillery requires a forward observer calling coordinates over voice. Battleships and submarines contest coastlines. Aircraft scout and strike. None of these systems can be soloed effectively, and that’s the point.
• Player Construction and Terraforming: Trench lines, concrete bunker complexes, rail networks, roads, and bridges are all built by hand, in-world, by people with shovels and hammers. The map you fight over in week three is a map players made in weeks one and two.
• Regiment-Scale Organization: Large clans coordinate offensives over voice comms and external planning tools. The most decisive weapon in Foxhole is a spreadsheet and a Discord call.

The Gameplay Loop

Foxhole doesn’t have a gameplay loop. It has four or five of them, running in parallel at different tempos, and the experience depends almost entirely on which one a player chooses.

The combat loop is the shortest and, honestly, the least interesting on its own merits. Top-down shooting with a limited vision cone, heavy weapon sway, and lethal time-to-kill produces tense, chaotic firefights, but the moment-to-moment mechanics are serviceable rather than exceptional. Taken in isolation, the gunplay would rate a six. Nobody plays Foxhole for the gunplay in isolation.

The logistics loop — “logi,” in the local dialect — is the game’s true engine and its most divisive feature. You drive to a scrap field, mine, haul to a refinery, wait on production timers, load crates onto a flatbed, and run a long convoy to a frontline stockpile. It is repetitive. It is slow. Players describe it, without much exaggeration, as a second job. And yet it is also the source of the game’s most unusual emotional payload: when a player delivers shells to a garrison that has been holding under fire for hours, and the defense holds because of what they brought, they have contributed something no other game’s economy can meaningfully replicate. The reward isn’t a loot drop. It’s causality.

The construction loop sits between the two. Digging a trench line ahead of an anticipated push, then watching that line save a region a day later, is strategy played in geology.

And above all of it sits the command loop: officers reading the map, calling where the next offensive lands, negotiating between regiments who don’t answer to anyone. Foxhole’s meta-game is essentially player-run political science, and it works better than it has any right to.

Onboarding Friction Is the Central Design Problem

Let’s be blunt about the failure. Foxhole’s onboarding is bad. Not “hardcore games are supposed to be opaque” bad — genuinely, correctably bad. The tutorial gestures at movement and shooting and then abandons new players inside a war machine with dozens of interlocking systems it never mentions. Nothing in the game explains stockpile management, public versus private storage, facility layouts, or the unwritten social contracts that govern who gets to take crates out of a frontline base. New players learn Foxhole through humiliation and hearsay: doing something wrong, getting yelled at in region chat, and asking a stranger why.

This is the single largest tax on the game’s audience, and it explains the shape of its reception. The players who survive the first week almost universally love it. The ones who don’t leave convinced the game is unfinished. Both readings are defensible.

Where the Structure Strains

Three structural problems are real and worth stating plainly.

Population imbalance can decide a war before the fighting matters. When one faction significantly outnumbers the other, no amount of tactical skill compensates for an enemy that can field twice the trucks and twice the shells. Queue times on contested hexes compound it.

Griefing and time destruction. Because everything is player-built and player-owned, everything is player-destructible — including by your own side, whether through incompetence or malice. Hours of work can evaporate to a single bad actor with a hammer. Siege Camp has added mitigations over the years; the exposure hasn’t gone away.

Time as a hard gate. Foxhole doesn’t respect your schedule. Offensives happen when they happen, often overnight for your timezone, and the person who plays four hours a night simply matters more than the person who plays four hours a week. That’s not a bug — it’s the honest cost of persistence — but it should be named for what it is before spending money.

The recent 30-day Steam trend, sitting at Mixed, reflects a more acute set of complaints: balance revisions that unsettled established metas, update-related bugs, and server congestion during the exact large battles the game exists to produce. That last one stings the most. A game engineered for thousand-player sieges is strained by the arrival of a thousand-player siege, and the netcode has not been built to absorb it.

The art direction is quietly accomplished and probably under-discussed. Foxhole runs a muted, dieselpunk World War I–into–World War II palette — mud browns, gunmetal, olive, oxidized industrial reds — rendered top-down with detailed sprite-and-model work that reads clearly at a glance. It’s a functional aesthetic. A vehicle silhouette, a fortification type, and a faction uniform can be identified in a half-second, which matters more than fidelity at this camera height.

The environmental storytelling is the real achievement. Late in a war, a contested region looks it: cratered to the horizon, littered with burned-out husks, trench scars cutting across ground that was farmland two weeks earlier. No artist authored that. The players did, and the map remembers.

The UI is where craft gives way to accretion. Inventory management, stockpile transfers, and facility configuration are handled through dense, clunky, heavily nested menus that feel like they were extended repeatedly rather than redesigned once. Moving crates around is one of the most common actions in the entire game, and it remains one of the least pleasant.

Performance is conditional by design. A top-down game of this scope is light on hardware in quiet regions and mid-size engagements. Massive sieges — the game’s marquee moments — are where server-side lag, rubber-banding, and desync are most likely to surface, and that’s a recurring theme in negative reviews rather than a one-off.

Steam is the only home, and mouse-and-keyboard is the only sane input. Foxhole demands simultaneous map reading, radio chatter, inventory shuffling, and precise aiming — a controller would strangle it, and there’s no meaningful controller path here anyway.

The Steam integration is more than incidental. Regiment recruitment, war-by-war community documentation, and the workshop of external tools and maps that orbit the game all live in and around the Steam ecosystem and Discord. Expect to run a browser or a second monitor alongside it; the game assumes external coordination software exists, and plays worse without it.

One practical note: Foxhole runs on separate shards with independent wars. Which shard you commit to determines your community, your regiment, and your war’s tempo. Choose deliberately — it’s a bigger decision than any settings menu in the game.

Foxhole is a good game with flaws that matter, and the flaws are structural rather than cosmetic. The systems design is ambitious — a closed player economy at this scale arguably shouldn’t work, and Siege Camp has kept it working, war after war, since launch. When a Foxhole battle peaks, when the trucks are rolling and the artillery is walking onto coordinates called by a scout on the other side of the map and the bunker line holds because everyone did their jobs, it produces something no single-player game and no matchmade shooter can manufacture: the feeling of being one person inside a real war effort.

But the same design that generates those highs generates the lows, and Siege Camp has not solved the two problems that most limit its audience. The onboarding remains a wall rather than a ramp, and the technical performance falters at precisely the moments the game promises to deliver. Neither is unfixable. Both have been true for years.

We recommend it if the description of running a supply convoy for hours sounds appealing rather than absurd. If it sounds absurd, believe your instinct — this game will not change your mind, and it will not meet you halfway. Foxhole isn’t for everyone. It’s rewarding for the people it’s for.