ReSkate not working?

Documented setup correction — wrong install folder

Current main-branch documentation expects an independent ReSkate directory. If your launcher refuses Steam’s skate. folder, follow that layout and let it fetch the supported game build. The released v2.0.7 README also documents an older shared-folder option, so identify your launcher version before treating this as the cause of every startup failure.

• Identify where the ReSkate launcher actually lives.
• Compare that layout with the instructions for the launcher version you downloaded.
• For the current independent-folder workflow, start from an empty ReSkate directory and let the launcher install its copy.

Confirmed upstream fix — texture-limit crashes

v2.0.7 release notes report raising the streamed-texture limit from 20,480 to 32,764 to address freezes and crashes with heavily modded maps. Update to that release or a later compatible release. A warning now appears at 90% capacity: the maintainer advises stopping mod additions or uninstalling some. This is an upstream-reported fix, not our test result.

textures

v2.0.7 adds this console command to show streamed-texture usage. The release also reports fixes for a crash when leaving certain custom maps and a crash when content failed to load. Those notes describe specific fixes; they do not establish that every crash with mods is solved. Keep the warning message and the affected package names when reporting a remaining case.

Documented requirement — cannot join a server

v2.0.7 changed the multiplayer protocol. Players and dedicated servers must both run 2.0.7 to play together on that release. Check both ends before treating a failure as a network problem. The server README also requires matching ReSkate versions.

1. Compare your exact ReSkate version with the host/server version.
2. Confirm you copied the complete current join code; anonymous dedicated-server codes change after restarts.
3. Use the password path when the session requires one.
4. Check whether a custom map package is required and whether the host supplies an automatic Thunderstore download.

Documented behavior — a mod is skipped

Mods for an incompatible game build, or ones that cannot merge cleanly, are skipped while the rest load. Check the named warning, the package’s requirements and logs\ReSkate.log beside Skate.exe. Custom Lua files in scripts/Custom are disabled in this version; moving those files around does not enable them.

• Record the mod name in the loader warning.
• Compare the package’s target game build with the pinned Steam build.
• Review the log for the actual merge/load message; a generic “mods do not work” label hides the useful evidence.
• Check whether the package relies on disabled custom Lua.
• For multiplayer scoring exclusions, consult the server policy and restart without the flagged mod as documented.

Temporary workaround — black screen after changing maps on Proton

The README links issue #31 and advises loading the server’s map before joining if you previously loaded another custom map. Treat this as a workaround, not a confirmed general Linux fix. The issue was open at review and originally described version 1.0.8; it does not prove every listed symptom still occurs in v2.0.7.

Unverified / unresolved — new Proton setup

The checked README says the new separate-folder launcher setup has not been tested on Proton, and Steam Deck remains untested. We cannot provide a verified fix or compatibility promise. Follow the upstream Linux section and check subsequent releases for changes.

Still stuck? Report useful evidence

Record your ReSkate version, operating system, supported game build, enabled mods and the steps that trigger the problem. Review logs\ReSkate.log before sharing it and remove personal information. Search existing upstream Issues first, then report a reproducible case. No blanket antivirus-disable or unknown-DLL download advice is offered here.

ReSkate version:
Steam game build:
OS and (if applicable) Proton version:
Install folder layout:
Enabled mod packages / versions:
Steps to reproduce:
Expected result / actual result:
Relevant log lines (reviewed for personal data):