ReSkate on Steam Deck & Linux — Documented Proton Setup

What is supported by the evidence?

A desktop Linux test is not a Steam Deck verification badge. The upstream README names one older client, one distribution and Proton Experimental, and describes launcher and multiplayer checks. It does not establish compatibility for the current v2.0.2 release on every Linux system.

For Steam Deck, treat the instructions below as the project’s documented route to investigate on your own device. We have no hands-on result for SteamOS, Gaming Mode, controller navigation, suspend/resume, battery life or frame rate. We will not invent a successful Proton-version table.

Before changing launch options

Install your Steam copy of skate. and identify its local game folder. The Linux route uses the existing Steam installation; the README does not describe the separate-folder Windows path as its Proton recipe. Extract ReSkateLauncher.exe and ReSkate.dll beside Skate.exe.

On a Steam Deck, use the desktop environment if you need a file manager to extract and place the archive. That is a practical way to perform the file step, not a claim that we have tested the Deck’s interface. Keep a copy of your original launch options and any data you want to preserve before editing.

The project says to launch from skate.’s existing Steam library entry. This keeps the game’s app ID and Proton prefix. Adding the launcher as an unrelated non-Steam shortcut may create a different prefix, so do not silently substitute that route for the documented one.

Use the project’s exact Steam launch option

In Steam, open skate. → Properties → Launch Options. The README supplies the command below. Preserve its quotes and %command% when copying it; do not translate the executable names. Save your previous option so you can restore it.

Then use Play on skate. in your Steam library. The option substitutes ReSkateLauncher.exe for the executable Steam would otherwise invoke. The launcher should then follow its supported-build verification flow. If authentication or verification fails, keep that precise failure instead of assuming it is a rendering problem.

bash -c 'exec "${@/EAAntiCheat.GameServiceLauncher.exe/ReSkateLauncher.exe}"' -- %command%

Why EAAntiCheat can show E111000B

The README explains that Steam starts EAAntiCheat.GameServiceLauncher.exe and that this launcher refuses Wine, Proton and Steam Deck with E111000B. The documented launch option replaces that invocation with ReSkate’s launcher, which starts the game itself.

If you still see the same EA anti-cheat screen, compare the option character for character and confirm you edited skate.’s own Steam entry. Confirm both ReSkate files are beside Skate.exe. This is a check of the documented routing, not a guarantee that another launch failure cannot occur.

Do not turn this into a claim that EA’s normal online game supports Proton, or into a console installation guide. The project’s unofficial route and the official game’s launcher are separate contexts.

Menu access and controller expectations

The documented menu shortcut is Insert; the console shortcut is grave/tilde. Both can be changed in the launcher Settings. If your handheld controls have no convenient Insert key, you need a way to send that configured key, such as a keyboard or your own Steam Input binding.

No controller layout is supplied here as a tested preset. Check your chosen binding while the game is focused, record what happens, and keep it separate from any question about the launcher opening. The README mentions a controller-friendly parks screen, but that is not evidence of an end-to-end Steam Deck interface test.

We also have no measured graphics preset or FPS target. Avoid treating a desktop user’s video as a battery-life or stability benchmark for your own Deck. Large map packages have their own resource requirements and may behave differently from the plain game.

Known report: black screen after changing maps

The README links Linux issue #31 and describes a black screen when a custom map is loaded before joining a server using a different map. Its suggested workaround is to load the server’s map first. We have reviewed that advice; we have not reproduced the problem or the workaround.

Issue #31 was opened for ReSkate 1.0.8, and includes reports from specific Linux setups. Those reports are historical observations, not proof that v2.0.2 has exactly the same failures. When searching the tracker, compare client version, game build, distribution, Proton version and map.

If the plain offline session opens but a server or custom map fails, keep those outcomes separate. They help distinguish launch routing from mod loading or multiplayer. Do not declare the entire platform either working or broken based on one stage.

Undo the option and gather a useful report

Close the game before changing files. Restore the launch option you saved if you want to return to the previous Steam launch behavior. This reverses your option edit; it does not certify that the normal EA launcher will run under Proton.

Back up profile data within the appropriate Proton prefix before deleting or recreating that prefix. The Windows-style %LOCALAPPDATA% locations in the README refer to the Windows environment used by the game, not necessarily a matching directory on the Linux host. This guide has not verified one universal prefix path for all setups.

For a report, include your distribution or SteamOS version, Proton version, ReSkate version, game build, folder route, active mods, exact message and the last successful stage. Remove authentication material and personal paths before sharing logs. Search the original tracker before creating a new issue.