Your ReSkate server runs the native Linux dedicated server from the ReSkate GitHub releases. It needs no copy of skate. on the machine, it keeps itself on the latest ReSkate release, and it already has its own Steam game server token, so it shows up in the in-game server browser. Players find it by name. This is the path from checkout to your crew skating on it.
1. Find your server
Open your dashboard and select the new ReSkate service. The Overview tab shows the server's status, the live console and a How players join card: the server name to search for, the join password, and the steps to send your friends.
2. Check the Server Settings tab
The Server Settings tab holds the four things the panel manages for you:
- Server name is what players type into the browser's search box. It starts as the name you chose at checkout. Up to 64 letters, numbers, spaces and
- _ / [ ]. - Join password is optional. Leave it empty and anyone who finds the server can join; set one (letters and numbers only, up to 32) and players type it when they join.
- Show in the server browser is on by default. Turn it off for a private server: it disappears from Multiplayer > Servers and players join with the join code printed in the console instead.
- Steam token. The ReSkate browser lists only servers that sign in to Steam with a game server login token, so we created one for your server when it was built. There is nothing to do here unless you want to use your own: paste a token made for App ID 3354750 at
steamcommunity.com/dev/managegameservers, one per server. A saved token is never shown again.
The player cap comes from your plan: 16, 32, 64 or 128. Changes on this tab apply at the next start, and the tab offers a Restart now button after you save. A restart disconnects anyone who is on.
3. Start it and watch the console
Start or restart from the Overview tab and watch the console. On start the server checks GitHub for a newer ReSkate release, signs in to Steam and prints its join code. The panel shows the server as running once it reports that it is up. The status command prints the name, map, player count and join code again whenever you need them.
4. Make yourself an admin
Admins can change the map, kick, ban, start votes and run every server command in game. To make yourself one:
- Join your server from the game.
- In the console, type
players. It lists everyone connected with their SteamID64, the 17-digit number starting7656119. - Type
role <your SteamID64> admin, for examplerole 76561198000000000 admin.
Admins run commands in game by typing them in chat with a / in front, such as /map Isle of Grom. roles in the console lists every role and who has it. The five built-in roles (player, vip, moderator, admin, muted) are explained in ReSkate server settings explained.
5. Get your crew in
Each player needs:
- skate. from Steam (free to play on PC), and
- the ReSkate launcher, on the same ReSkate release as the server.
Then they open skate. through the ReSkate launcher, go to Multiplayer > Servers, search for your server's name and join, typing the password if you set one. The join code from the console works too, and it is the only way in when the server is hidden from the browser.
No ports need opening on anyone's side: players connect through Steam's relay network.
6. Change everything else
The rest of the server's settings live in ReSkateServer.json: welcome message, map and map rotation, player votes, AFK kick, object limits, anti-cheat, announcements and chat commands. Two ways to change them:
- Console commands change a setting live and save it to the file, for example
rotation 30,afk-kick 15orwelcome Welcome to the session!. Typehelpfor the list. - Edit the file: stop the server first, open
ReSkateServer.jsonin the Files tab (or over SFTP), edit, then start. The server writes its settings back to the file while it runs, so an edit made with it running can be lost.
Do not set the name, password, player cap, listing or Steam token in the file: the panel rewrites those from the Server Settings tab before every start.
7. Custom maps and park mods
Upload a custom map's mod folder into Mods with the Files tab or SFTP, keeping the folder name Thunderstore gives it (Owner-Name or Owner-Name-1.0.0) so players without the map are offered the download. Then type maps reload and map <name>. Parks built in the Park Editor work the same way, with park-mod commands. Step by step in custom maps and park mods.
8. Updates and backups
You do not need to update anything. The server checks GitHub when it starts and every 30 minutes, and installs a newer ReSkate release as soon as nobody is on, keeping ReSkateServer.json, Mods and the logs. If friends cannot join right after a release, type update in the console to install it now; anyone on is told to rejoin.
The Backups tab snapshots the server's files. Take one before you start experimenting with maps and settings.
If something is not right
- Nobody can find or join the server → Players can't find or join my ReSkate server. Start with the version check.
- A setting keeps reverting → you edited
ReSkateServer.jsonwhile the server was running, or it is one of the settings the panel manages (name, password, player cap, listing, token). - Anything else → open a ticket from your dashboard and paste the last lines of the console.
ReSkate is a community project. Connect Hosting is not affiliated with Electronic Arts, Full Circle or the ReSkate team. skate. is a trademark of Electronic Arts.