Wardogs: the 100-player tactical shooter, explained

Updated 27 September 2026. Prices and review counts read from Steam's own API on that date; a live early access game moves, so every figure below is dated.

Wardogs is a first-person shooter from Bulkhead, a studio in Derby, England, published by Team17 and built in Unreal Engine 5. It reached PC early access on 10 September 2026 after a closed beta on 22 August. PlayStation 5 and Xbox Series X and S versions are scheduled for 2028, and Bulkhead expects early access to last roughly one to two years.

The pitch is one sentence and everything follows from it: one hundred players, three teams, one control zone. It is set in Eastern Europe, the ground is destructible, and it sold over two million copies in five days. It is also, three weeks in, a game whose store badge and whose current reviews say noticeably different things - which is the part most articles miss, and the part this page spends the most time on.

Contents

• The mode, and why the map is so large
• The three factions, and the blue team problem
• Money instead of a battle pass
• What you actually do in a round
• Progression, and the rebalance that annoyed people
• The engine work underneath it
• Price, editions and system requirements
• The two review numbers, and which one to believe
• Performance problems and the official advice
• Servers and regions
• The two launch stories
• How it compares to Battlefield, Squad and Arma
• Frequently asked questions
• What is still unknown

The mode, and why the map is so large

A server holds 100 players in three teams. The map is about 256 square kilometres, but a match is not fought across all of it: a 2 by 2 kilometre control zone is placed somewhere on it, and that is where the fighting happens. Inside that zone a smaller Hot Zone multiplies what holding ground is worth, so the map has a centre of gravity that moves.

Three teams rather than two is what changes the feel. A two-sided push has one answer; a third force arriving in the middle of it does not. Holding a position means watching a direction you did not choose to fight in, and the moment a team commits everything to one side it has invited the other two to trade with each other at its expense.

The three factions, and the blue team problem

The three are not currently even, and this is the single most discussed thing about the game. It is not a community theory - the developer says it too. Joe Brammer of Bulkhead told GamesRadar on 18 September: "We definitely have a balancing issue... But it's green team who win most of the time. Green and red are fairly even, and that's been the same way since pre-alpha. But blue getting destroyed is definitely a problem with mixed reasons."

Speaking to PCGamesN the same day, he agreed with a player that the map layout works against blue because their closest towers sit on lower ground, and said Bulkhead is not planning temporary measures such as randomising team spawns between matches. Players have built a whole subreddit around it, r/BlueTeamWARDOGS, which describes itself as "the team nobody wants to join".

There is a second, more mechanical complaint alongside it. The intended split is 33 / 33 / 34, uneven by one by design. Players report worse in practice - one live 100-player server was counted at 35 / 35 / 30. In a mode scored by who is standing in a zone, a five-player gap is not cosmetic. The official position is that one extra player does not confer an unfair edge, which answers the one-player case and not the five-player one.

Players have their own diagnosis, and it is specific enough to be worth recording even though none of it is confirmed by the developer:

• The uniform. Blue is bright against khaki ground, while green blends into foliage and red sits comfortably in shadow. The argument is that blue players are simply easier to see.
• Fixed spawns. With spawns in the same place every match, whatever disadvantage the layout gives blue is handed to it again every round - which is the change players most often ask for and the one Bulkhead has said it is not making as a stopgap.
• Where blue sits in the menu. Blue is the leftmost option in team select, which players argue affects who ends up on it.

Set against all that, blue does win - one player reports a 100-99-5 round in their favour. The imbalance is real and acknowledged; a guaranteed loss it is not.

Money instead of a battle pass

Every account starts with $10,000 of in-game cash, and that balance carries between matches rather than resetting each spawn. Equipment is bought with it, so a wasteful round costs something and a careful one compounds.

There is no battle pass and there are no microtransactions. Cosmetics are bought with gold bars, exchanged from in-game cash, and cash and experience reset seasonally. For a game at this scale in 2026 that is the unusual part, and it is what positive reviews mention most.

What you actually do in a round

• Building and destruction. Cover can be put up and taken down, so a position that worked an hour ago may not exist now.
• Vehicles. Tanks and helicopters are on the field, which is what makes a map this size navigable at all.
• Proximity voice chat. You hear the people near you, including the ones trying to kill you. It is responsible for a large share of the clips that travel.
• Scoring that pays for teamwork. The work that keeps a squad alive is rewarded, not only the kills.

Progression, and the rebalance that annoyed people

A progression rebalance on 9 September, the day before early access opened, made levelling substantially slower - reaching level 20 was reported as 124.2% slower than before the change. Complaints about grind build through the community from about 15 September onward.

It is tempting to draw a line from that change to the review slide described below, and the timing fits. It is a plausible chain and not a demonstrated one; nobody has measured it, so treat it as a coincidence worth noticing rather than a cause.

The engine work underneath it

Bulkhead did not ship stock Unreal. Their own Steam announcement of 18 February 2026 puts it plainly: "Our custom 'WAR DYNAMICS FRAMEWORK' enhances UE5 to handle high-density 100-player All Out Warfare!" If you see it written as "War Tech Framework" somewhere, that spelling is an invention of content farms; the developer's own wording is above.

Price, editions and system requirements

Steam lists the game as Windows only. Note that 16 GB appears in both columns: the entire gap between minimum and recommended is the graphics card, which is what you would expect from a game drawing a hundred players and a town that can fall over.

The two review numbers, and which one to believe

This is where a reader gets misled most easily, because both numbers are real and they are measuring different things. Read from Steam on 27 September 2026:

Split by day, the recent sample runs 64.7% positive on 25 September and 60.0% on 26 September. Roughly two thousand reviews a day are still arriving, which is why the lifetime average is sliding rather than sitting still.

So: the store badge is a lifetime average, dominated by launch week and filtered to your language. What people are writing this week is fifteen to twenty points below it. Neither number is a lie and quoting only the first one is how a three-week-old game keeps a launch-week reputation. If you quote one, quote both.

One absence worth stating rather than leaving to be noticed: as of this date no outlet has published a scored review. Metacritic, OpenCritic, IGN and Game Informer are all still marked as to-be-decided. That is normal for early access and is not a sign anything is wrong.

Performance problems and the official advice

Crashes and stutter are the most common technical complaint, and Team17 support has posted specific advice rather than boilerplate:

It does not work for everyone. One widely endorsed reply reports that on an RTX 5080 none of the suggested fixes helped. Support ticket queues were long enough in the first fortnight that a player tracked their position moving 200 places in 36 hours and projected 25 days to a first response.

Separately, three players tie launch-time and map-load shader freezes to Nvidia driver 616 / 616.92 - the Game Ready driver dated 9 September, which is to say the one that shipped day-one support for this game. A reply in the same thread argues the supposed fix is placebo and the freezes are ordinary real-time shader compilation. Both readings are on the record and neither has been measured; treat it as a player attribution, not a finding.

One small practical note: the error codes carry a per-session suffix, in the shape WD-L020-3fbd8827f84e. The part before the dash is the fault; the hex after it is your session. Two reports with the same prefix are the same problem even though the full strings differ.

The two faults people are still waiting on

The launcher. A recurring report is that the game will not start reliably without running a launcher repair and restarting the machine first. One player calls it the single thing keeping the game from being technically stable, which is otherwise a generous verdict.

Gunner desync. Vehicle gunners appear to face somewhere other than where they are actually looking. The description players give is exact: you peek, the gunner is looking away, you commit to the shot with a launcher, and you are killed instantly because the gunner was facing you the whole time. A developer is reported to have acknowledged it around 26 September, though the evidence for that is a screenshot rather than a post anyone can link. Some players argue the vehicle should be pulled until it is fixed, citing the mobile anti-air that was removed for early access.

Servers and regions

Cross-region play is common and it is worth being precise about why, because the usual assumption is wrong. Players are not being routed to distant servers by a queue - they are choosing them. As one put it, the reason players from China appear on EU and even US servers is to get away from their own region. A Japanese player describes the opposite side of it: being pooled under regional restrictions and losing the population that makes matches work.

OCE is referenced by players as an existing region. The Middle East is confirmed absent. A September thread about region choice ran to 267 comments, which is a fair measure of how live the topic is.

The two launch stories

The one everybody repeats is the queue controversy: server queues at launch were perceived to favour livestreamers, a share of the negative reviews are about that rather than about the game, and the developers acknowledged it through in-game announcements. The mechanism players describe is a loop rather than a conspiracy - you reach the front, your login ticket has expired, you get an error and you rejoin at the back.

A fuller account circulates from Brammer's launch-day video, and it is worth reading with care because it is one player's relay of a video, not a statement anyone can quote directly. In that telling, demand far exceeded the estimate, the queue broke, a denial-of-service attack hit at the same time, and parts of the server infrastructure went stale, which is what produced the mid-match disconnections. A commenter in the same thread separates the two fairly: the queue was their own mistake, the server side was the attack. Treat all of it as a lead.

The one that actually travelled further is the crunch story, which reached the wider gaming subreddits on 15 September and was picked up by outlets quoting Brammer saying he expects people to crunch. Measured by reach outside the game's own community, that is the defining launch story, not the queues - which is the opposite of what most summaries assume.

A useful negative finding sits alongside it: the technical complaints did not travel. Checking the general PC gaming and games subreddits turns up no large performance or server thread outside the game's own community. What escaped was sales milestones and the crunch story.

How it compares to Battlefield, Squad and Arma

The honest comparison is by what each one asks of you. Battlefield gives you two teams, a short time-to-kill and a match that resets cleanly. Squad and Hell Let Loose ask for communication and punish a lone player hard. Arma asks for preparation. Wardogs sits between the first and the second: the shooting is conventional enough to pick up in a round, and the three-team structure plus a persistent bank account is what makes it different rather than any simulation depth.

Gunplay is the most praised element in most places, so it is worth recording the dissent: the one substantive critique to surface on a general FPS forum attacks exactly that - gunplay feel, animation and sound.

Frequently asked questions

What is still unknown

Things that are asked often and that no public source answers reliably, listed so nobody mistakes the gap for an oversight: the bleed-out timer, the proximity voice range in metres, the gold bar exchange rate, the full attachment list, the exact vehicle count at launch (sources disagree between 21 and 27), the definitive list of progression tracks, the exact Unreal Engine point version, which FSR version shipped, the Season 2 reset date and the full wipe rules, and whether there is a day and night cycle.

Sources

• Wardogs on Steam - description and requirements. Price and review totals were read from Steam's appdetails and appreviews endpoints with the US region on 27 September 2026, because the page itself serves a regional price.
• Bulkhead announcement, 18 February 2026 - the WAR DYNAMICS FRAMEWORK wording
• Wardogs on Wikipedia - development, factions, sales and player figures
• GamesRadar and PCGamesN, 18 September 2026 - Joe Brammer on team balance
• Team17 support posts on the Steam discussion boards, 12 to 18 September 2026
• Green Man Gaming and GameWatcher