ReSkateSETUP DESK

PC mod support / evidence workbench

ReSkate setup checklist

Build a clear support note before following mixed setup advice. Choose your document basis, platform and intended mode; get six dated notes that separate published rules from what still needs checking.

A completed checklist is a generated note, not a successful installation, repair or multiplayer connection. No account, folder, file or game is inspected.

01 / Your setupManual choices

Label the setup you mean.

Choose an answer for each applicable field. An explicit unknown is a valid answer.

Choose the actual basis. Main and a release note are kept separate.

This is your selection, not a hardware detection.

Server pairing is relevant only to multiplayer.

No folder path or file is accessed.

Only the captured 2.0.7 pairing rule is evaluated.

This is recorded in your note; it is not read or diagnosed.

No checklist yet. No files or accounts are accessed.

02 / Evidence notesSix boundaries

Keep the unknowns visible.

Your checklist will connect each choice to a dated source instead of declaring the setup fixed.

  1. Choose your basisMain, a release note or unknown.
  2. Compare one prerequisiteFolder and platform scope; paired versions only for multiplayer.
  3. Copy a precise noteAdd an exact version and redacted observation yourself.
Read the version boundaries →

03 / Read before changing files

Follow the right evidence.

Main is a moving document. A released build, an older fan guide and an issue from another version are different evidence. Keep those labels together before changing your setup.

01

Main or release?

A protocol note is not a verified install guide. Keep the document date attached to your build.

Compare document bases →
02

Folder and Proton

The new main folder flow is untested on Proton. Older reports do not validate the new method.

Read platform limits →
03

Client meets server

Both marked 2.0.7 satisfies one captured prerequisite. It does not prove a working connection.

Review the release rule →