An independent ReSkate guide, with clear limits.

What this ReSkate guide is

ReSkate Companion is an independent, documentation-led guide for people deciding whether and how to use the ReSkate fan project with their own Steam copy of skate. It is not affiliated with EA, Full Circle, Dingo-Shenanigans or the ReSkate maintainers. Names such as Steam, skate., GitHub and Thunderstore identify the services and projects being discussed; they do not indicate sponsorship, approval or a warranty.

The guide has a practical purpose. It turns the upstream installation notes, release metadata, privacy notes and issue context into readable choices: which archive is the player, where the files go, what the launcher is documented to do, and which questions still require judgment on your own computer. It does not turn a third-party guide into an official support channel.

How the evidence is gathered

The primary evidence category is upstream documentation. The current README was reviewed at commit 63955e51ffe03ae77913a7b15b69c6322e705050, reviewed at 2026-10-10T07:06:47Z. That pinned commit is the reference for installation language, controls, data locations, privacy statements and the project’s own platform notes. A commit pin makes the review reproducible; it does not mean the repository will remain unchanged.

Release evidence is kept separate from README evidence. The reviewed release tag is v2.0.2, published 2026-10-09T21:18:31Z, with supported game build 25414733 and an empty release body. The official GitHub Releases API record identifies the player archive as ReSkate-2.0.2.zip and reports SHA-256 cf0ef2fd5ee42e2017ef67c5abd5df66506416159bc44e8117067f0bb5e442c5. That digest is an asset identity reference from the release record, not a security certification.

Community evidence is useful for context, not a replacement for project documentation. The ReSkate issue tracker, including Linux map-loading report #31, can show what users have reported and how maintainers responded. Thunderstore pages show community package names and author-provided details. A report or mod listing is attributed to its author or reporter; it is not presented as a controlled test by this site.

Each claim is assigned the narrowest category that fits: upstream documentation, release metadata, a maintainer or user report, community listing, or this site’s interface behavior. When a sentence describes what the README says, the wording keeps that attribution. When it describes a limitation of this guide, it says so directly. This prevents a project statement from quietly becoming a promise about every device or file.

Browser privacy and external requests

The setup assistant is a local checklist. It stores the route you selected, the current step and the completion you reported in this browser’s local storage. Changing the setup clears that progress. The assistant does not inspect the game, read a private folder, upload a log or verify that a checkbox is true. A completed checklist therefore means that you marked it complete.

This site uses Google Analytics 4 to measure page visits, traffic sources and website interactions. Google Analytics may use cookies and browser identifiers. Advertising personalization and Google signals are not enabled by this site. Checklist selections, build numbers and pasted file hashes are not sent as custom analytics events. This site has no account form, feedback collection backend or crash-report upload. Ordinary page delivery still involves the hosting provider, Vercel. Fonts are requested from Google Fonts, and normal browser requests may also reach services you open through an external GitHub or Thunderstore link. Those services have their own policies and are outside this guide’s control.

The guide does not ask for Steam credentials, QR codes, Steam Guard codes, private paths or session tokens. If you copy an error into a public issue, remove account details and personal directory names first. The project’s own launcher privacy settings belong to the upstream application and should be read separately from this website’s browser behavior.

The optional checkbox checklists save only whitelisted step identifiers, separately for the existing-folder and separate-folder routes. Their reset buttons clear the recorded selections. The build comparison and SHA-256 helper work on the text you enter in this page; they send no request to a verification server and do not upload the archive. FAQ search also runs locally. These helpers do not establish a successful game session, authenticate an account, or change files on your computer.

Where to take a setup question

Use the FAQ for terminology and documented first checks, then use the installation or troubleshooting page for a step-by-step route. For a game or launcher bug, search the original ReSkate issue tracker with the client version, supported build, operating system and exact symptom. This website does not collect reports, diagnose a private machine or post to the project on your behalf.

A useful report separates facts from guesses: identify the release archive, folder route, last successful step, exact message and whether optional mods were present. Do not attach Steam credentials or an unredacted private path. Maintainer replies and issue reports remain evidence about that report, not a universal fix for every installation.

Artwork, fonts and guide presentation

The homepage scene is original AI-generated concept art. It is not a screenshot, benchmark, capture from a running game or evidence that ReSkate launched successfully. Folder diagrams explain placement with a visual shorthand; they are not photographs of a verified installation. The guide keeps these presentation assets separate from claims about the upstream software.

The interface uses Google Fonts when the browser can reach them, with system-font fallbacks when it cannot. Original project links lead to GitHub, and community package links lead to their listed Thunderstore pages. A link is provided so that you can inspect the source in its own context; its appearance here does not change that source’s ownership or terms.

What a documented guide can answer

A documented guide can explain the route the project publishes: use the Steam game it names, select the player archive rather than a dedicated server package, place the client beside the game or choose the separate-folder route, and understand the launcher’s stated verification and update behavior. It can point to the project’s profile locations, key bindings, crash-report controls and mod warning. It can also tell you which release tag and supported build were reviewed so that your own comparison starts with a concrete record.

It cannot answer questions that require observing your machine or independently inspecting a binary. Whether your antivirus alert is a false positive, whether a particular GPU maintains a frame rate, whether a Proton prefix has the right files, whether an account consequence will occur, and whether a release is harmless all need evidence this guide does not possess. A matching SHA-256 digest establishes that an archive matches the cited reference. It does not prove the reference itself is safe, signed, or suitable for your situation.

The useful next step depends on the unknown. For a missing file, compare the documented folder route. For a release mismatch, compare the tag and supported build. For a crash, preserve the exact message and consult the issue tracker. For a security alert, pause and investigate provenance. For a platform question, keep the upstream Linux and Proton report distinct from an untested Steam Deck claim. The page should help you choose that next check without pretending it already happened.

Review dates, stale data and corrections

The release record is maintained manually from the original tag, the official release API response and the pinned README review. v2.0.2’s release body is empty, so this guide does not invent a changelog from asset names, download counts or someone else’s gameplay video. The fixed archive digest helps identify the reviewed asset; it does not make the archive interchangeable with a DLL, a repack or a later build.

A review timestamp is a point-in-time record, not continuous monitoring. The page may be stale for a release, README edit, deleted asset, changed issue or changed hosting behavior that appeared after the timestamp. Before installing, open the original release page and compare the tag, asset name and any new maintainer notice. If the source has moved, follow the source’s current instructions and treat this guide as historical context until reviewed again.

Corrections are made by tracing a statement back to its source category. A changed upstream fact should link to the current primary record. A community report should remain labeled as a report. A claim about this site’s wizard should be checked against the visible interface. This approach is slower than copying a new version number everywhere, but it keeps unrelated pages from implying that they were all rechecked.

The guide does not claim hardware compatibility, frame-rate performance, malware safety, a clean antivirus result, a valid code signature, a ban guarantee or a successful Steam Deck session. It also does not use word count, search position or a generic “safe” label as evidence. Those limits are part of the methodology because a clear unknown is more useful than a confident unsupported answer.

A Linux report is not a Steam Deck verification

The pinned README attributes launcher, server-browser and lobby checks to ReSkate 1.1.3 with Proton Experimental on CachyOS. That is the project’s own reported test context, not a session performed by this website. The same paragraph says Steam Deck is untested. Neither observation becomes a v2.0.2 SteamOS compatibility certificate when a new client release appears.

Linux issue #31 was opened for an older client and contains user reports about map transitions and loading. The README points to it with a suggested map-loading workaround. We retain the issue number and version context so readers can compare their setup with the original report. We have not reproduced the failure or confirmed the workaround. A page update does not silently change either status.