Skip to main content
ReSkateServer.json, beside the server, holds its settings in sections:
The first run writes the file with every default. Most settings also have a command, and every change made from the window or by an admin is saved back to the file.
Do not edit ReSkateServer.json while the server runs: it writes the file back whenever a setting changes, over your edits. Stop it, edit, and start it again, or change settings with commands.
A file from an older version, with every setting at the top level, is read as it is and written back in sections.

server

The server itself: its name, its password and its ports.

access

Who always has a place. Who runs the server is in data/roles.json: see roles.

maps

What is skated. Maps and parks explains each.

players

What players may do. Admins, and roles with the matching permission, can always do what this turns off. A player who places more than twice the object limit plus 100 in a minute (a modified game animating objects by spawning them again) has their objects deleted for everyone, and nothing they place is shared for a minute.

anti_cheat

What the server checks, and what it does. See anti-cheat.

network

How players connect and how much they are sent. The defaults suit most servers.

votes

What players may vote on, and polls. See votes and polls.

announcements

commands

Chat commands of your own, such as /discord or /rules. A list of at most 32: see chat commands.