Two shooter betas, one weekend - and only one of them is a real stress test

My download queue had two shooters in it on Friday night, and I genuinely could not tell you which one more people were waiting on. Wardogs and Call of Duty: Modern Warfare 4 both went live within hours of each other, both sitting near the top of the Steam charts, both asking for money before they ask for feedback. That last part is worth chewing on.

But the thing that actually interests me is that these two betas are not the same kind of event at all. One is a genuine load test. The other is a vibe check.

Wardogs is the one with something to prove

BULKHEAD's shooter, published by Team17, runs 100 players split across three teams fighting over a single control zone - King of the Hill logic, first side to 100 points takes it. Add destructible buildings, tanks, helicopters, fortification mechanics and proximity voice chat on top, and you have the hardest netcode problem anyone is shipping this year. Three-way objective fights are already a nightmare for spawn logic. Doing it while the map is falling down around you is another category entirely.

Look at the spec sheet and you can see the studio knows it. Minimum is an i5-8600 or Ryzen 5 3500 with a GTX 1660, targeting 1080p Low at 60fps. Recommended jumps to an i7-12700K or Ryzen 7 5700X with an RTX 3070 or RX 6700 XT - for 1440p Medium at 70fps and up.

That CPU gap is the tell. You do not go from an i5-8600 to a 12700K because of shaders. You do that because a hundred players, vehicles and live destruction are hammering the simulation thread. And I appreciate that they quoted 70fps rather than rounding it up to a marketing-friendly 144, because anyone who has played a large-scale destruction shooter knows exactly where the frametime spikes live: not in the quiet opening minute, but at the ninety-second mark when three squads collapse the same building. Average fps will look fine. Your 1% lows will tell the truth.

Modern Warfare 4 has an easier job

Activision has solved 6v6 a dozen times over. The Early Access weekend that opened Friday at 8PM CEST runs through Tuesday for people who pre-ordered, on Steam and Battle.net, and the free Open Beta follows on August 28 - which is the one I would actually wait for. Not because the early build is worse, but because a beta populated exclusively by people who already paid is a rigged sample. It is a sanity check on TTK and map flow, not a server test.

Wardogs at least handles the paywall with some spine. Pre-ordering at 39,99 euros guarantees you in, there is a Playtest route for random access, and the developers have openly said that if you did not have fun, go get a refund. I would rather have that than a studio pretending a paid beta is a favour they are doing you. Early Access proper lands September 10, with the studio signalling it could sit there for a year or two.

What I would say to anyone judging either game off this weekend: do not. Launch-window beta servers are the best conditions these games will ever see - freshly provisioned, lightly loaded, full of motivated players. The number that matters is not what you get on Saturday. It is what your ping and your 1% lows look like in week six, on a Tuesday, when the marketing budget has moved on.

Image: Brian Wong / CC BY-SA 2.0, source: https://commons.wikimedia.org/wiki/File:Gaming_PC-Setup_-_Astaroth-_The_Completed_System.jpg