Kicks and bans
A
<player> is the start of their name (one word) or their SteamID64. players lists who is on, with their SteamID64s. A player is told how long when they are kicked and when they try to join again.
Nobody kicks or bans a player of their own rank or above; the server’s window can.
Bans are kept in data/bans.json. The ReSkate team’s own list of players banned from multiplayer is separate: with access.use_global_bans on (the default), the server reads it from api.reskate.dev at startup and every ten minutes, and turns those players away too.
Chat words
The ReSkate team keeps a list of words not allowed in chat at all. A message with one is never passed on, and its player is warned. Afterplayers.word_warnings warnings (1 to 10, default 3), the next one gets them kicked; they can join again, and are kicked again at the next. Warnings last until the server restarts. With 0, nobody is warned or kicked, and the message is still not passed on.
The server has two word files of its own in data/, made empty the first time it starts. One word to a line; a line starting with # is a comment. Edit them and type words reload.
players.use_global_word_filter: false (or words global off) leaves the team’s lists out, so only words_blocked.txt is refused. Each player’s own game still stars out the team’s filtered words for a player with their chat filter on, and hides a server whose name has one of the team’s words from the browser.
To keep one player quiet, give them the muted role.
Away players
Withplayers.afk_kick_minutes (or afk-kick <minutes>), the server removes a player who has been away that long. Away is not moving, speaking, typing in chat, changing objects or using the game’s controls: a player flying a plugin’s drone, whose skater stands still, is not away.
They are warned in chat a minute before, and can join again at once. Admins, and roles with no_afk_kick, are never removed for it.
Locking a player’s tools
lock <player or SteamID64> <tools|all> takes tools from one player while everyone else keeps what the server allows. The tools are noclip (with teleporting), nobail, boosts and tuning (their own physics tuning), joined by commas.
- It takes effect at once, and is kept for their SteamID until unlocked or the server restarts: leaving and joining again does not lift it.
- A player who is not on is locked by their SteamID64.
- Their role cannot give a locked tool back.
unlock <player or SteamID64> [tools]gives them back (all when none are named), also to a player who left.lockslists the players with locked tools.
players.throwdown_locks (or throwdown-locks <tools>|off) locks tools for a throwdown’s players while it runs, for fair games on a server that allows the tools for free skating. They are locked when the throwdown starts, and unlocked when the player quits it, it ends, or they leave. Such as ["nobail", "boosts", "tuning"].
The log has a [lock] line for each lock and unlock.
Anti-cheat
Each check isoff, warn or kick. Players whose role has anticheat_alerts are told in chat what the checks find.
kick removes the player instead.
For a server that runs on a scoring mod everyone installs, score-check (with no argument) lists each player’s scoring fingerprint, and score-allow <fingerprint> accepts it like the game’s own (anti_cheat.allowed_scoring_mods).
What else the server holds every player to:
Players who place objects far too fast, more than twice the object limit plus 100 in a minute, have theirs deleted for everyone and nothing shared for a minute. Admins are exempt.