PC mod support / evidence workbench
ReSkate setup evidence and sources
These original pages were reviewed on 15 October 2026. The tool uses a static evidence snapshot; it does not fetch your game or automatically know when the upstream project changes.
- rolling documentation
Original ReSkate main documentation ↗
Current main describes a separate empty folder and explicitly says the new folder flow has not been tested on Proton. Main was 39 commits beyond the visible v2.0.7 release; the tagged README was not obtained.
- release note
Original v2.0.7 release note ↗
Visible release label: 12 Oct 01:28; the captured date did not display a year. The note requires both clients and dedicated servers to be 2.0.7 after a protocol change. This establishes one prerequisite, not a successful connection or the released installation steps.
- user request · 12 Oct 2026
Original request for stable, versioned releases · #200 ↗
A user asks for stable releases alongside rolling updates to make upgrade, rollback and reproduction deliberate. One request does not establish a general fix or the size of demand.
- user report · 12–14 Oct 2026
Original update regression discussion · #199 ↗
Reported mod/settings regressions and save concerns remained under discussion. The cause and a safe migration path were not independently established; this page does not diagnose them.
- older issue · 6–7 Oct 2026
Original Proton / Steam identity discussion · #88 ↗
The contributor comparison used version 1.1.3 and different launch-entry types. It is dated context for asking for help, not proof of the current main folder flow or current multiplayer account requirements.
- older issue · 4 Oct 2026
Original Linux map-loading discussion · #31 ↗
An older 1.0.8 map-loading loop was reported under Proton. It does not prove that current Linux or Steam Deck setups work, or that all map issues have been fixed.
What the snapshot does not establish
The research used readable original public documentation and reports. The tagged v2.0.7 README was not obtained, and no binary, installation, hardware, server or game was tested. An open issue establishes a reported problem, not a verified cause or remedy. Main versus release boundaries are deliberately kept visible.
When upstream changes
Compare the original page date and your build before applying a note. An upstream update may require a new evidence review. The tool will not silently replace a dated rule with a guess or claim that generated notes prove a setup is working.