ReSkate Wiki

Launch ReSkate and begin with offline play to confirm that the base game and ReSkate setup are working correctly.

• Use offline play for the first setup check
• Verify that the game loads before adding more mods

Use the ReSkate in-game menu to access available ReSkate features while playing.

• Open the menu after entering the game
• Review the available ReSkate options
• Return to gameplay after confirming the setup

Use the mod manager to review installed content and control which mods are active for the current session.

• Check installed mods before launching a modded session
• Enable only the content you want to test
• Disable recently added content when troubleshooting

Once offline play is working, move on to multiplayer and use ReSkate features with other players where supported.

• Test the base installation before joining multiplayer
• Use compatible mods for shared sessions
• Keep the mod setup consistent when playing with others

Use the launcher to start ReSkate, the in-game menu to access features, and the mod manager to organize installed content.

• Launcher: start ReSkate
• In-game menu: access ReSkate features
• Mod manager: review and control installed mods

Goal: Keep source files, test builds, and released packages organized

• Create a project folder outside the live game installation
• Maintain a clear source directory for editable files
• Keep a separate build or staging directory for files that will be copied into Mods
• Record the target ReSkate release and required dependencies

Goal: Make the mod recognizable by the ReSkate mod system

• Create the mod's top-level directory
• Place content in the folder structure expected by the relevant asset or script type
• Avoid unnecessary nested folders when packaging the mod
• Use consistent names for files, folders, and entry points

Goal: Start with a small, easy-to-verify content change

• Choose one supported resource or custom content target
• Add only the files required for that change
• Preserve the expected file paths and naming conventions
• Document what the mod changes and which files it replaces or extends

Goal: Add behavior through a Lua-based mod component

• Place the script in the mod's script location
• Keep the first script small and focused on one behavior
• Use clear entry points and avoid modifying unrelated systems
• Add basic logging or visible test output where appropriate

Goal: Combine multiple content changes without creating conflicts

• Identify files shared by more than one mod
• Merge compatible changes into a deliberate final structure
• Keep backups of the unmerged versions
• Test the merged package separately from the original projects

Goal: Test the package in the same environment used by players

• Copy the packaged mod into the ReSkate Mods directory
• Confirm that the package is not wrapped in an unintended extra folder
• Start ReSkate and check whether the mod is detected
• Use logs or in-game behavior to confirm that the intended change loaded

Goal: Find whether a failure comes from structure, content, or compatibility

• Test the mod by itself before combining it with other mods
• Remove the latest change if the game stops launching
• Check file paths, script entry points, and required dependencies
• Compare the result against a known working minimal package
• Record the first error shown in the relevant log

Goal: Make the mod understandable and repeatable for other players

• Add installation instructions and a clear description
• List required ReSkate versions, dependencies, and known conflicts
• Keep the package limited to the files needed by the mod
• Test a clean installation from the final distributable package
• Publish the project through the intended ReSkate mod distribution channel