The Accidental 'A/B Test': How One Shooter's Stumble Lifted Another, Mate
AI Gaming News Author · Eurogamer ·
According to its technical director, *Arc Raiders*' successful April playtest was a 'very great A/B test' thanks to a coincidental, disastrous beta from rival extraction shooter *Marathon*, offering valuable lessons and highlighting player sentiment.
Right, so imagine you're brewing a potent elixir in your digital lab, carefully tweaking the ingredients for a new extraction shooter. Suddenly, your rival in the next lab over has a bit of an... *incident*. A spectacular, fiery, public incident, actually. Annoying for them, sure. But what if that chaotic eruption accidentally created the perfect comparative conditions for *your* experiment? That, my friends, is more or less the wild narrative emerging from the parallel universes of Embark Studios' *Arc Raiders* and Bungie's upcoming *Marathon*.
According to a fascinating piece by Connor Makar over at Eurogamer, the technical director for *Arc Raiders*, Virgil Watkins, described Bungie's initial, rather disastrous, *Marathon* beta test as "a very great A/B test" for their own game. And honestly, mate, that's some next-level, optimistically chaotic thinking right there. Fair dinkum, I'm a digital wizard, not a corporate PR guru, but calling a rival's public stumble a fortuitous 'A/B test' for your own soaring success? That's a meta-narrative I can get behind.
*Arc Raiders* has been on a journey, hasn't it? It first popped onto our radars looking like something genuinely fresh, a co-op extraction shooter that promised a bit more sci-fi flair and less grimdark grind. It's been in development for a good while, gathering a steady hum of anticipation. Then came its April playtest, which, as Watkins insists, just so happened to coincide with *Marathon's* initial closed beta. Pure coincidence, apparently – no sneaky peering over the fence. But the timing couldn't have been more serendipitous for Embark.
"It was very coincidental that they had their test around the time we did," Watkins told PC Gamer, as reported by Eurogamer. "To my knowledge, I don't think any of us knew that was going to happen. It was a very great A/B test for us, because obviously they made decisions that we didn't, and vice versa. So we could kind of compare and contrast how some of those things shook out."
Now, let's cast our eyes to the present. Fast forward to last weekend, and the chasm between these two games in the public eye is wider than the Grand Canyon after a particularly powerful reality-bending spell. *Arc Raiders* just wrapped its final open beta, the 'server slam', ahead of its October 30th launch. And bloody hell, it *slammed*. Almost 100,000 concurrent players on PC alone in its opening hours. The sentiment? Overwhelmingly positive. Players have been raving about its combat, its unique aesthetic, and its general sense of fun.
*Marathon*, on the other hand, finds itself in a bit of a sticky wicket. That initial public test? It didn't exactly set the world on fire. Players were, shall we say, 'torn' on its design choices. Key features like a solo queue or proximity chat were conspicuously absent, leading to a chorus of 'what were they thinking?' from the community. Then, as if that wasn't enough, it was at the centre of a rather unpleasant plagiarism scandal involving its visual assets. Ouch. The game was swiftly delayed from its initial September release, and is now gearing up for another open beta from October 22nd to 27th.
So, what *does* this accidental 'A/B test' really tell us? Well, for one, it highlights the immense power (and peril) of early public beta tests. For *Arc Raiders*, its playtest provided valuable feedback that Embark seemingly incorporated, refining the experience to hit its stride. For *Marathon*, it was a wake-up call – or perhaps a digital punch to the face – revealing fundamental issues that resonated poorly with players. It underscores a crucial mantra: listen to your players, especially in the early stages, unless you fancy a good old-fashioned digital egg on your face.
Watkins' comment, whether an intentional jab or a genuinely astute observation, points to the often-unseen competitive analysis that goes on in game development. When another game in your genre tests the waters, you're absolutely watching. You're noting what works, what falls flat, and crucially, what players *don't* want. *Arc Raiders* saw what *Marathon* lacked (or messed up) and could double down on its own strengths or, perhaps, ensure it didn't repeat similar mistakes. It's like having your rival accidentally reveal their magical incantation's flaws, letting you perfect your own without the trial-and-error.
This whole dance between *Arc Raiders* and *Marathon* isn't just a fascinating case study in game development; it's a testament to the capricious nature of hype and player sentiment. Can *Marathon* pull a phoenix act from the ashes of its shaky start? Or will *Arc Raiders* simply suck all the oxygen out of the extraction shooter room when it launches, leaving little breathing room for a competitor still finding its footing? The stage is set for an epic showdown this month, with *Marathon's* redemption beta concluding right as *Arc Raiders* arrives.
From a player's perspective, this is a genuinely exciting (if slightly chaotic) time. We get to witness real-time competition driving innovation, and studios learning (sometimes the hard way) what truly resonates. *Arc Raiders*'s ascent, fuelled partly by its own merits and partly by a rival's stumbles, is a story of unexpected success. Let's just hope *Marathon* learns from its 'A/B test' results, eh? Because at the end of the day, we all just want bloody good games to play, mate.
Tags: Gaming Industry, Beta Tests, Extraction Shooters, Game Development, Player Feedback
Original article: Eurogamer