GloriousEggroll shipped a hotfix barely 12 hours after GE-Proton 11-10 to stop Easy Anti-Cheat from kicking Linux players out of their own games. Here's what broke, what the fix reveals about running Windows games on Linux, and the Proton hygiene drill that keeps your library playable through the next hotfix.

Linux gaming has a release cadence that would make a DevOps team jealous. On October 19, 2026, GloriousEggroll published GE-Proton 11-11 at 1:20 PM Central Time — about 12 hours after GE-Proton 11-10 had landed at 1:21 AM the same morning. The release notes carry a single word up top: "Hotfix Release." No Wine, DXVK, or VKD3D version bumps. No new features. Just targeted repairs to damage introduced days earlier.

If you run Linux on a gaming rig, this cadence isn't a bug. It's the whole operating model of the compatibility layer. And 11-11 is a perfect specimen to study.

The headline: Easy Anti-Cheat stood down

Since GE-Proton 11-7, Easy Anti-Cheat had been kicking Star Citizen players with "Violation 8 — Untrusted system file" (error 30033, flagging StarCitizen_Launcher.exe). The same behavior hit Hunt: Showdown when launched outside Steam. For a multiplayer game, that's not a minor glitch — it's a lockout from everything you play with friends.

The root cause is almost poetic in its specificity. VKD3D-Proton — the Direct3D 12 over Vulkan layer — had started reading the parent process's executable to detect Unreal Engine games. Easy Anti-Cheat saw an unfamiliar binary poking around the process tree and did exactly what anti-cheat is paid to do: it assumed the worst and threw players out.

The fix is equally telling. VKD3D-Proton no longer reads the parent process's executable, and 11-11 reverts a Star Citizen AMD AGS override that 11-10 had shipped as a guess — with the honest note that it "was not the cause of the EAC violation." GloriousEggroll guessed, the community tested, the guess was wrong, and the rollback is in the changelog for everyone to read. That transparency is the actual feature.

Warhammer 40,000: Space Marine 2 gets a footnote too: reported broken in 11-10, working again after these changes. When you ship every few hours, the blast radius stays small.

The quiet half: video playback repairs

Hotfixes like this also tend to mop up media regressions, and 11-11 is no exception:

  • Games freezing when a video is skipped or closed while MPEG-1 audio plays through DirectShow — a deadlock in the MPEG audio decoder, a regression since 11-8.
  • MPEG-1 videos rendered upside down through AMStream — a regression since 11-1.
  • Heap corruption and crashes when video frames get converted or scaled, which was taking down Target Bravo: Operation G.H.O.S.T. at stage select (fix contributed by @aderumier).

There's a lesson buried here for anyone who thinks of Proton as "just a compatibility layer." Half of what makes a Windows game feel native on Linux is the media stack — DirectShow filters, codecs, frame conversion. GE-Proton rebuilds FFmpeg and carries those patches so your cutscenes don't become crash vectors.

Proton hygiene: the operator's drill

You can't control GloriousEggroll's release cadence. You can control your exposure to it. Here's the drill I run on my own machines, and what 11-11 reinforces:

  1. Keep two or three Proton builds installed. ProtonUp-Qt makes this a two-click job, and Steam lets you keep old versions alongside the new one. When a hotfix lands, you're never more than a dropdown away from the last known-good build.

  2. Pin the version per game, not globally. In Steam, game Properties → Compatibility → force a specific GE-Proton version. Set your competitive, EAC-gated titles to the build you verified last week, and let single-player games ride the bleeding edge.

  3. Test new GE builds on something disposable first. A 12-hour turnaround means regressions get fixed fast — but it also means they ship fast. Launch a non-competitive game, skip a few cutscenes (yes, really), and check ProtonDB before pointing a new build at a game with anti-cheat.

  4. Read the "Hotfix" label as information, not warning. A build tagged "hotfix" with no component bumps, like 11-11, is telling you exactly what changed. That's the safest kind of update in this ecosystem. The riskier ones are the big feature drops — like 11-8, which took three months and broke Crimson Desert's HDR within hours.

  5. Remember the division of labor. For 99% of titles, Valve's official Proton is the right default, with real support behind it. GE-Proton is the rapid-response lane: anti-cheat triage, day-one fixes for games Valve hasn't reached, controller and codec patches that may never land upstream. Use it where it earns its keep.

Why this matters beyond gaming

Step back and 11-11 reads like a case study in how open-source infrastructure actually stays healthy. One maintainer, a test community that reports within hours, and a release process so cheap that a bad guess can be reverted the same day without ceremony. Compare that to the kernel's careful merge windows or a distribution's freeze cycle — both necessary, both slower. Gaming on Linux gets the fastest loop because the stakes are visible: people can't play their games, and they say so loudly.

The next time Steam offers you a compatibility-tool update and you hover over the version dropdown, give a nod to the 12-hour hotfix. It broke EAC, it fixed cutscenes, it admitted a wrong guess, and your Tuesday evening gaming session survived it. On Linux, that's what reliable infrastructure looks like — shipped before dinner.

Sources: GE-Proton release notes via the proton-ge-custom repository (GloriousEggroll, October 19, 2026); GE-Proton11-11 hotfix breakdown (VetTV Handheld News); GE-Proton 11-10 / Proton-CachyOS / DWProton roundup (GamingOnLinux); Linux Compatible archive, October 2026.