ReSkate Server Settings Explained (ReSkateServer.json)

Every ReSkate server is configured by one file, ReSkateServer.json, written next to the server the first time it starts. It is grouped into sections: server, access, maps, players, anti_cheat, network, votes, announcements and commands, with who-runs-what kept separately in data/roles.json. This post walks through the settings that shape a server: admins and roles, passwords and reserved slots, map rotation and votes, and the player rules most owners change in the first week.

It is a guide, not the full reference. The ReSkate server README in the project's repository lists every key; this covers the ones that matter and what they actually do.

How to change settings safely

Two rules first:

• Never edit the file while the server runs. The server writes its settings back to ReSkateServer.json whenever an admin changes one, so a hand edit made in the meantime can be overwritten. Stop, edit, start.
• Most settings have a console command. password, listed, rotation, votes, afk-kick and many more change the setting live, and the server saves it to the file for you. That is usually easier than editing JSON.

A file from an older ReSkate version, with every setting at the top level, is read as it is and rewritten into sections the first time a newer server starts.

server: name, password, listing

chat_color and chat_text_color set the colours of the server's own lines in chat, and activity_log (default true) logs joins, throwdowns and object placement, which is handy when something gets griefed.

Admins and roles

Who may do what lives in data/roles.json, beside the bans. The first start writes five roles:

• player: everybody without a role. Chat, votes, parties, private messages, no commands.
• vip: a reserved slot and a VIP tag.
• moderator: kick, ban, unban, messages, tphere and giving out the roles below it, plus a reserved slot, anti-cheat alerts and polls.
• admin: every command and every permission.
• muted: no chat or private messages.

Give a role from the console with role <player or SteamID64> <role>, take it away with role <player> none, and list everyone with roles. You can edit roles.json to change a role's tag, colour, rank, commands and permissions, then type roles reload; a file with a mistake in it is not loaded, and the server says what is wrong.

Rank matters: nobody can kick, ban or change the role of a player whose rank is equal to or above their own. Players use their role's commands in chat with a / in front, such as /kick or /map, and the game shows them the menu controls their role allows.

access: reserved slots and bans

reserved_players_slots is a list of SteamID64s that can join when the server is full. Each of them, and each online player whose role has a reserved slot, adds a slot beyond max_players that only they use. With 32 players, 2 admins and 2 listed, anyone can join until 32 are on and those four can still join after that, up to 36, so the browser shows 33/32 and so on. Nothing is held back from everyone else.

use_global_bans (default true) turns away players the ReSkate team has banned from multiplayer. Your own bans, managed with ban and unban, are kept in data/bans.json and apply either way.

maps: the map, the pool and rotation

• map is what everyone skates: San Vansterdam (default), Isle of Grom, Super Ultra Mega Resort, Stadium 1, or a custom map's name.
• pool is the maps players may vote for and the rotation walks through, in order. Empty allows every map the server knows.
• rotation_minutes (default 0, off) moves to the next map on a timer. Players get a minute's warning, the clock waits while nobody is on, and it starts over whenever the map changes.
• rotation_vote lets players pick the next map when time is up: three from the pool, "Random map" or "Stay here". rotation_vote_seconds (10–120, default 30) is how long that vote runs, and rotation_extend_minutes (default 15) is what "Stay here" adds.
• rotation_announce (default true) tells players on a card at 10, 5 and 1 minutes left.

Custom maps, Thunderstore updates and park mods each have their own settings in this section; they are covered in custom maps and park mods.

players: what players may do

• allow_noclip, allow_no_bail, allow_boosts (default true): admins can always use them.
• afk_kick_minutes removes a player who has been away that long (1–1,440; default 0, never). They get a minute's warning in chat; admins are never removed.
• allow_voice_chat and voice_range (50–1,000 m) for proximity voice.
• object_placement: everyone, admins or nobody. object_limit caps placed objects per player (default 100, 0 for no limit).
• allow_parties and party_size (2–8) for parties.
• kick_minutes: how long an admin kick lasts (default 0, until the server restarts).

votes: let players decide

Each vote except extend_map is off until you turn it on, and each has a percent of the votes cast that "yes" needs:

"votes": {
  "map": { "enabled": true, "percent": 60 },
  "kick": { "enabled": true, "percent": 60 },
  "time_of_day": { "enabled": true, "percent": 50 },
  "extend_map": { "enabled": true, "percent": 50 }
}

Players start them with /vote map <map>, /vote kick <player>, /vote tod <time> and /vote extend, and answer with /yes and /no. A kick always needs two yes votes and admins cannot be vote-kicked. time_of_day needs world_layer_sync on; extend_map needs a rotation running. Each vote can carry its own seconds, cooldown_seconds and min_players.

custom adds votes of your own that run a server command when they pass, up to 16, such as a vote to reload the current map or spawn a park for 30 minutes. polls decides who may ask everyone a question with up to six answers.

anti_cheat, network, announcements, commands

• anti_cheat: speed_hack, pinned_board and modified_scoring each take warn (the default), kick or off. warn keeps the player on the server but out of throwdowns and coop challenges (or, for a pinned board, hides their board from everyone else).
• network: the defaults suit most servers. use_steam_relay (default true) routes players through Steam's relays so nothing needs opening.
• announcements: messages are lines posted on a card in turn, every interval_minutes while players are on.
• commands: chat commands of your own, such as /discord or /rules, each with a reply, a server command, or both. Up to 32.

On Connect

On ReSkate server hosting, the server's name, password, browser listing and Steam token are fields on the Server Settings tab, and the player cap comes from your plan. The panel writes those into ReSkateServer.json before every start, so change them there, not in the file. Everything else on this page is yours: use the console commands, or stop the server and edit the file in the Files tab or over SFTP. Plans start at $3.99/month for 16 players.

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.

Frequently Asked Questions

Where is the ReSkate server config file?

ReSkateServer.json, next to the server. The first start writes it with every setting at its default. Roles are in data/roles.json and bans in data/bans.json.

Why did my edit to ReSkateServer.json disappear?

The server was running. It writes its settings back to the file whenever an admin changes one, so stop it before editing, or use the matching console command.

How do I make someone an admin?

Type role <SteamID64> admin in the server console. roles lists every role and who has it.

How do I give my crew a guaranteed place on a full server?

List their SteamID64s in access.reserved_players_slots, or give them a role with a reserved slot such as vip. Each adds a slot beyond max_players.

Can players vote to change the map?

Yes. Turn on votes.map and set maps.pool, and players start one with /vote map <map>. For timed changes, use rotation_minutes with rotation_vote.