Host and Manage a ReSkate Dedicated Server

Choose the operating-system-specific server package

The stable v2.1.2 release offers ReSkateServer-2.1.2.zip for Windows and ReSkateServer-Linux-2.1.2.tar.gz for native x86_64 Linux. Neither is a playable client. A server does not need the full game or Steam application, but it does need its bundled Steam networking libraries. The documentation sometimes calls the Linux archive a ZIP; use the actual release attachment.

First run, configuration and administrator access

Extract the selected server package into its own directory. On Windows, run ReSkateServer.exe once to create ReSkateServer.json, stop it, edit at least server.name and restart. The source documentation warns that changing settings in the running server can write the config back, so manual edits while it is active can be overwritten. Keep steam_api64.dll, steamclient64.dll, tier0_s64.dll, vstdlib_s64.dll and world-layers.json with the executable.

role <your SteamID64> admin

The settings most hosts need first

Begin with discovery, access and a map choice. The documented nested fields below are enough to orient a first setup without reproducing the entire configuration. Role permissions and moderation belong to the server’s own role documentation; assigning yourself admin is separate from setting a join password.

Install a custom map and preserve its package name

Copy the complete custom map mod folder from the game’s Mods into Mods next to the server, including reskate-levels.json and manifest.json. Keep its Thunderstore Owner-Name or Owner-Name-Version identity so missing-map offers can identify the package. The server and player need the same map content. A Park Editor park mod has a different setup: it is configured for the map where it was built and distributes supported Build Kit objects rather than a whole new level.

1. Copy the map mod folder into the server’s Mods directory and preserve its identity and metadata.
2. Select the map by the documented name and include it in maps.pool when you want it available for rotation or votes.
3. Check the joining client’s exact ReSkate version and map package. Use the custom-map guide for declined, unavailable or slow map downloads.

Networking, restarts and keeping versions compatible

The documented Steam relay connection does not require port forwarding. Optional UDP 27015–27016 forwarding improves browser ping display and joining speed; those ports are not a universal fix for a version mismatch. With anonymous sign-in the server gets a new Steam identity and code after each restart, while its name remains discoverable. A private game-server login token is an advanced upstream option, not a password to publish in a guide.

Both players and server need stable 2.1.2; it cannot connect to the earlier 2.1.2 prerelease. Servers can declare plugins.required. The join card groups missing plugins and the map; GET ALL downloads, installs and applies them before joining.

Timed kicks and per-player tool locks

Version 2.1.1 supports timed kicks and individual tool locks for noclip/teleport, No Bail, boosts or physics tuning. Use the upstream admin command reference for the intended duration, player identity and tools. A player’s local settings can be restricted by the host; tool locks last until lifted or the server restarts.

Stable 2.1.2: required plugins and GET ALL

A dedicated server can list plugins.required. If a player lacks those plugins or the server’s map, one join card lists them together. GET ALL downloads, installs, applies and joins without restarting, according to the release notes. Server plugins can also show cards and polls, manage park mods, hide players or mute them. Both sides must use stable 2.1.2.