Rust on Linux

How to judge Rust on Linux

Rust currently shows Proton borked, anti-cheat denied, and desktop Linux broken. No working Linux path; Facepunch does not enable EAC for Proton and treats Linux as a cheat vector, so use Windows. Treat the current record as more reliable than old launch anecdotes.

Facepunch dropped Linux/Proton EAC support; the COO stated there are no plans to re-enable it, so online play is blocked. If this is a must-play title, keep a supported fallback on Windows, console, or cloud until the publisher-supported path changes.

• Read the current signal together: Proton borked, anti-cheat denied, desktop Linux broken.
• Test the exact launcher, account, input, saves, and online mode you actually use.
• Keep a supported fallback for ranked, social, or money-linked play.

What Rust decides for a Linux gamer

Rust should be evaluated as part of the user’s real library, not as an abstract Proton example. The current page labels it as Broken, with Proton tier Borked and anti-cheat status Publisher blocked. Those three signals together matter more than any single rating because games fail through different layers.

If Rust is a daily or multiplayer title, it can decide whether Linux becomes the main gaming OS or only a secondary environment. The migration decision should be based on actual launch, account, online, save, controller, and performance testing on your own hardware.

Proton and launcher expectations

For Rust, Proton is part of the decision. Start with the default Proton version, then test Proton Experimental or GE-Proton only when current reports suggest a benefit. Record the working version and launch options so the setup can be rebuilt after a driver, kernel, or game update.

Launcher behavior matters. Steam, Epic, EA, Ubisoft, Battle.net, and custom launchers can each introduce separate login, overlay, update, DLC, or cloud-save problems. A game is not fully ready until the launcher path is stable too.

Anti-cheat and account safety

The anti-cheat label for Rust is Publisher blocked. Treat this as a hard warning. If online play is blocked or publisher-denied, do not rely on unsupported workarounds for a main account.

For competitive games, the safest rule is simple: check anti-cheat status before launch, avoid unsupported setups, and keep Windows, console, or cloud gaming available for any title where the publisher has not enabled Linux support. Account safety is more important than proving that a workaround can boot the menu.

Hands-on test plan

A useful Rust test includes single-player launch if available, multiplayer or online services, controller or keyboard/mouse input, graphics settings, fullscreen and display scaling, audio devices, cloud saves, DLC, mods, overlays, and a normal update cycle. Do not stop after the title screen.

If the game works cleanly, keep it on the approved list but still recheck after major game, launcher, anti-cheat, or driver updates. Linux gaming quality is improving, but it remains a moving target.

How it changes the full migration plan

If Rust is one of your main games, keep Windows, console, or cloud gaming in the plan. Linux can still be useful for work and other games, but this title should not be treated as solved.

The best gaming migration is not ideological. It is a library-by-library decision. Move the games that work, keep a fallback for the games that do not, and avoid buying new hardware or deleting Windows until the must-play titles are understood.