PC mod support / evidence workbench
ReSkate version support: read the evidence
The useful result is a precise description of the setup you mean and the evidence it follows. Work through the distinctions below, then generate a note on the checklist page.
Main README versus a release note
Start with the guide you actually followed. Main can change after a release: at the source check it was 39 commits beyond v2.0.7. The release note describes a protocol prerequisite, but the tagged README was not readable in the check. The tool therefore does not turn main instructions into tested release instructions. If you picked unknown, the next step is to identify that guide and the exact version displayed by your launcher.
Keep the folder rule tied to its platform and basis
Current main calls for a separate empty folder and rejects using the Steam game folder. An independent-folder selection is your statement that you checked it, not a scan by this page. For release or unknown document bases, the exact released folder flow remains open. Main also says its new folder flow has not been tested on Proton. Older Linux or Steam Deck success reports cannot remove that qualifier. Use instructions matching your build before changing files.
Client and server: one prerequisite, not a green light
The v2.0.7 release note says clients and dedicated servers must both use 2.0.7 after a protocol change. Selecting both only satisfies that captured version prerequisite. It does not test network access, a server, mods, identity or compatibility with another release. When both are marked another version, the tool keeps compatibility unknown rather than guessing that they match. Offline play has no server pairing check.
Separate offline intent from Steam identity reports
Offline with Steam closed is a documented intent in main, so a closed Steam state is not automatically a failure. Multiplayer identity reports need their actual version and launch context. The captured Proton discussion compared version 1.1.3 launch routes; it is older evidence, not a current account test or a guaranteed workaround. The checklist never signs in, reads Steam or detects an identity error for you.
Use the note to ask a more precise question
Choose every relevant field, including explicit unknowns, and generate the six notes. Use Copy checklist, then paste to check the result. Select text for manual copy is also available after generation: it exposes and selects the full note so you can use Ctrl+C or Command+C. Selecting text does not confirm a copy. Before sending anything yourself, add the exact displayed version and the observed symptom outside this tool, and redact personal account details or private logs. Original update reports describe regressions and save concerns, but they do not establish a general diagnosis or safe migration.
Why this remains a small support experiment
Existing community guides already cover installation, FAQ and troubleshooting. This page adds a compact way to keep source dates and version boundaries visible while creating a support note. Its usefulness to actual players, search traffic and any future business model have not been established. It does not replace the original authors, a tested guide for your release or a real hardware investigation.