It is NOT pure developer laziness! The BF6 developers/EA had no choice but to implement these new requirements because of constant hacks cheats and exploits by unethical people. Gamers complain when game makers don't try hard enough to stop cheaters and then when those devs try to do the right thing people like you chime in that they are lazy without actually knowing why Linux has this issue and go straight to blaming the wrong people.
I'm no IT pro but it took only an hour trying to find proper TPM 2.0 firmware update and proper update tool to patch TPM vulnerabilities. I Simply patched current 2.0 module to most current version which took 5 minutes to update the module. Then took 5 min to download and update my UEFI firmware for my motherboard. Then 15 minutes to enable both secure boot functions and TPM and TMP and confirm everything was working properly. Total of not even 2 hours to do my part for the benefit of BF6 Anti cheat by implement secure boot and the bonus is my pc is now more secure for things not related to games!
I'm sure some companies devs would rather just sit on their *** and take the EZ route but NOT but bad actors gave them no other choice. So rather than being lazy/greedy by creating yet another crappy prematurely released buggy exploitable cheat ladened game just to sell more copies and get richer they decided on quality over quantity instead of lining their pockets. The additional toolset of secure boot and TPM is needed to better enforce or investigate cheat reports leading to a more enjoyable user experience. What BF6 is doing is setting a higher standard for themselves and will result in better future cheat blocking mechanisms/detection methods to keep up with modern advanced cheat methods. It minimizes the risk and the number of cheats getting past in the first place and a solid foundation to any good Anti cheat system. This deters & helps properly monitor to better ensure dishonest players are not easily getting around the Anti cheat by loading modified unofficial uncertified drivers at boot time.
By the way it's not the fault of EA or the DEVS that Linux don't properly support secure boot/TPM. Linux is open source so there are many different compilations from different dev teams and/or diff communities all together. Because of there being so many different versions and/or builds of LINUX, those Linux devs were lazy and took the EZ route and utilized exploit that at the time existed to make a workaround to load unofficial uncertified and possibly unsafe drivers by using now expiring/expired security keys which are used byTPM/UEFI Bios to properly authenticate the loading of official unmodified drivers. All Linux communities would have to work together to create a unified universal key and issue it for Linux and insure there is a list of secure certified drivers to boot to. UEFI Bios and TPM firmware would need to be updated by hardware vendors? maybe?
I'm no IT pro but it took only an hour trying to find proper TPM 2.0 firmware update and proper update tool to patch TPM vulnerabilities. I Simply patched current 2.0 module to most current version which took 5 minutes to update the module. Then took 5 min to download and update my UEFI firmware for my motherboard. Then 15 minutes to enable both secure boot functions and TPM and TMP and confirm everything was working properly.
You’re kinda missing the real issue here, and it’s making this sound way more black-and-white than it actually is.
Linux does support Secure Boot and TPM. That part isn’t up for debate. It’s been a thing for years, and plenty of distros already ship signed bootloaders, support TPM 2.0, disk encryption, measured boot, all of that. The problem isn’t that Linux “can’t do it” — it’s that Linux doesn’t just hand full kernel control to third-party anti-cheat software by default. That’s a conscious design choice, not laziness or a lack of capability.
Also, Secure Boot and TPM don’t stop most cheating anyway. They only protect the boot process. Most modern cheats happen after the system has already started — memory manipulation, external hardware, DMA devices, VM tricks, logic exploits, you name it. Windows games that require Secure Boot, TPM, and kernel anti-cheat still have tons of cheaters, so clearly this isn’t the magic fix it’s being sold as.
Your “it only took me an hour to enable TPM” story is kind of beside the point too. Nobody is arguing that turning it on is hard. The issue is EA choosing an anti-cheat approach that’s deeply tied to Windows internals instead of using solutions that already work cross-platform. Games are doing this right now — including competitive shooters — and they’re not collapsing under cheaters because of it.
And blaming Linux devs for being “lazy” just doesn’t hold up. Linux is open by design. Users control their machines. That’s the whole point. A single universal key controlled by publishers or anti-cheat vendors wouldn’t be “more secure,” it’d be a massive downgrade in trust and user ownership. The flexibility you’re calling a flaw is literally why Linux is trusted in servers, infrastructure, and security-critical systems.
At the end of the day, EA didn’t “have no choice.” They made a choice. It’s a business and tooling decision — one that favors Windows and kernel-level enforcement because it’s easier for them, not because Linux is incapable or unsafe. Calling that inevitability doesn’t make it true.
So yeah, cheating sucks and devs should fight it — but pretending this is all Linux’s fault just doesn’t line up with how the tech actually works.
Great summary of the finer points in the unfortunate decisions made that affect BF6. It's why I'm still looking for a competitive shooter that'll work on Linux.
