When Anti-Cheat Goes Full Thunderdome: Battlefield 6 vs. Valorant's Kernel-Level Cage Match
AI Gaming News Author · Eurogamer ·
Battlefield 6 and Valorant can't run simultaneously due to their anti-cheat systems, Javalin and Vanguard, both trying to protect the same memory regions at the kernel level, causing a digital turf war. While it's a simple fix for now (just close one game), it highlights a growing concern about future conflicts as more games adopt deep-access anti-cheat technologies.
Right, so apparently Battlefield 6 and Valorant are having a bit of a digital spat, and it's less about which game is better and more about which anti-cheat thinks it runs the show on your PC. You know that feeling when you cast a spell and it works a bit too well, accidentally summoning two identical, equally protective golems to guard the same teacup? That’s pretty much what’s happening here, only with your precious gaming memory and high-stakes shooters.
This whole proper kerfuffle, by the way, was brought to light by some clever folks over at Eurogamer, specifically Connor Makar, who first poked this particular digital hornet's nest. Turns out, if you’re one of those ambitious legends trying to run both Battlefield 6 (during its recent mega-beta, no less) and Valorant simultaneously, your PC probably threw a wobbly. And no, it’s not because your rig secretly judges your taste in shooters, mate.
The head honcho of Riot Games' anti-cheat squad, Phillip Koskinas, took to X (formerly Twitter, because of course it was) to clear up the digital dust. He confirmed that Riot’s Vanguard anti-cheat and EA’s shiny new Javalin anti-cheat aren't actually incompatible in the grand scheme of things. So, deep breaths, no need to uninstall one to play the other. That’s a relief, because nobody needs that kind of admin in their life. But here’s the rub, the digital fly in the ointment: Battlefield 6 just doesn't like having the Valorant client running at the same time.
Why? Because, as Koskinas put it, "both drivers race to protect regions of game memory with the same technique." Imagine two highly dedicated, incredibly territorial bouncers trying to guard the exact same VIP section in a nightclub. They both have the same method of checking IDs and ensuring no one dodgy gets in, and when they detect another bouncer doing *their* job in *their* space, they assume it’s an invasion. It's not a fight to the death, just a very confused, very aggressive staredown that results in your game crashing or refusing to launch. In PC terms, it's about kernel-level access – they're both digging deep into your system's core, monitoring the most sensitive bits of game memory to catch those sneaky cheaters. When they both try to do the same thing, they essentially trip over each other, thinking the other is a threat.
Naturally, the digital tea leaves started swirling during Battlefield 6’s open beta. Players were reporting error messages left, right, and centre when trying to jump into EA’s big new shooter while Valorant was still chillin’ in the background. It made sense, then, that players were quickly advised to just close Valorant completely before launching Battlefield 6. Simple fix, really, but it did spark some interesting conversations about the growing prevalence and invasiveness of these kernel-level anti-cheat systems.
Now, I get it. Cheaters are the absolute worst. They ruin the game for everyone, turning skill into a lottery and fair play into a distant memory. So, it’s easy to see why companies like EA and Riot are pulling out all the stops, diving deep into your PC's inner workings to try and catch the scoundrels. And by Jove, EA reckons their Javalin system caught over 330,000 attempted cheaters during Battlefield's biggest open beta ever. That’s a fair dinkum mountain of ne’er-do-wells, isn't it? It makes you wonder how many digital rogue wizards are out there trying to bend reality to their will.
But here’s where my gentle skepticism kicks in, mate. While those numbers are impressive – genuinely – it also highlights an emerging dilemma. As kernel-level anti-cheats become the norm, what happens when every major game decides it needs its own digital bouncer with an all-access pass to your system’s deepest, darkest corners? We've just seen two of them clash, not because one was bad, but because they were *too good* at doing the exact same thing in the exact same spot. It's like a digital traffic jam at the most critical intersection of your computer.
What does this mean for the future of gaming? Will we see more of these territorial disputes between different anti-cheat systems? Will players eventually need to have a dedicated gaming partition for each game, just to avoid conflicts? It feels a bit like the wild west of digital security right now, where every developer is building their own impenetrable fortress, but they haven't quite figured out how to share the same digital neighbourhood without bumping into each other’s walls.
For now, the fix is simple: one shooter at a time, chief. It’s unlikely either Javalin or Vanguard will be drastically changing their core approach, largely because the number of players actively trying to run two kernel-level anti-cheat-protected shooters simultaneously is probably quite low. But as the digital arms race against cheaters continues, and these deep-access systems become standard, these little conflicts between seemingly benign programs are something a curious gamer will definitely want to keep an eye on. It's a fascinating, if slightly worrying, glimpse into the digital underbelly of our favourite games – where even the good guys can end up in a brawl.
Tags: Gaming Tech, Anti-Cheat, PC Gaming, Industry Trends, Player Experience
Original article: Eurogamer