EA is permanently banning Linux players on Battlefield V
Some context. This is running through Wine (and DXVK, a DX9-11 → Vulkan layer) on Linux.<p>Seems EA is doing —like a lot of very lazy anti-cheats— balls-simple stack inspection. They determine whether people are cheating by looking for known signed drivers, known hardware, known bad processes and input drivers. It&#x27;s cheap and scales well but it&#x27;s brainless. They have to know about a hack to detect it in the future. Version checks are constantly slackened off because legitimate updates come out all the time.<p>Battlefield is seeing Wine and the drivers Wine reports (which are a mix of real and fake) and baulking out. It&#x27;s to be expected from such plastic anti-cheat software. Many games do this.<p>There are better options.<p>CSGO&#x27;s overwatch allows the community to self-moderate by <i>replaying</i> a player&#x27;s gameplay. They literally record the player&#x27;s input and rebuild what the player could see in the reviewer&#x27;s client. Reviewer determines whether or not their gameplay was possible. It sounds hardcore but it&#x27;s simple, and adds no latency because it&#x27;s done after-the-fact. Makes it super-simple to detect most wall-hacks and aim helpers.<p>So why isn&#x27;t it everywhere? Logging data costs money. And EA, for all their moneybags are cheapskates.<p>And you could automate this. You could do a server-side render to determine whether or not a user is tracking players that are not physically visible to the player, or tracking impossibly tight hitboxes, or is triggering massive killcounts far too regularly (ie exploiting a bug). But that&#x27;s more money.<p>But I&#x27;d expect a better response shouting into the wind than asking EA to be better. They&#x27;re a trash company.