Schedule 1 Dedicated Server Commands and Admin Permissions (Full List)

Schedule I dedicated servers run on the community mod S1DedicatedServers (S1DS), and it comes with its own set of admin commands: kick and ban players, save the world, change the time of day, and hand out staff roles. Access is controlled by a permissions file with groups and permission nodes, so you decide exactly who can do what. This page lists every S1DS command with its syntax and default group, explains the permission system, and shows where to type the commands.

If you do not have a server yet, start with how to make a Schedule 1 dedicated server or the hosted quick start.

Where to type commands

S1DS commands have no slash in front of them. The same command works in all of these places, as long as whoever types it has permission:

There is also a built in web panel, but it only listens on the server machine itself (loopback) and cannot be reached from another computer.

Make yourself operator first

The quickest way to become admin is from the server console. Join the server once so it knows you, then type:

op YourSteamName

You can use your in game name while you are online, or your SteamID64 (the 17 digit number starting with 7656) at any time. op puts you in the built in operator group, which has every permission. Check it worked with:

listops

You can also do it by hand in UserData/permissions.toml, then run reloadpermissions or restart:

[user.76561198012345678]
groups = ['operator']
allow = []
deny = []

Server commands

settime takes a four digit 24 hour clock value. The S1DS docs describe settimescale as a diagnostic or recovery tool for operators, not a way to tune normal gameplay. To make days pass faster or slower permanently, change timeProgressionMultiplier in server_config.toml instead.

Player moderation commands

Run listplayers before kicking or banning, and copy the name or ID from it so you hit the right person. Use a SteamID64 for players who are offline, and for unban. Bans are stored in permissions.toml, so they survive restarts. Put quotes around names and reasons with spaces:

kick "Some Player" "stop blocking the door"
ban 76561198087654321 griefing
unban 76561198087654321

Staff and permission commands

op, deop, admin and deadmin are shortcuts kept for convenience. group and perm are the main tools, and they work with any group, including ones you create. For example, to make a friend a moderator:

group assign "Friend Name" moderator

Or to let someone save the world for the next hour only:

perm tempgrant "Friend Name" server.save 60 "covering while I am away"

How the permission groups work

S1DS stores all access rules in UserData/permissions.toml, not in server_config.toml. It is created on first boot with five built in groups. Each one inherits everything from the group before it:

Permission nodes

Every command checks a permission node. The built in commands have their own named nodes, such as server.save for save, server.stop for shutdown and player.kick for kick. Commands without a named node, such as settime, settimescale, logs and tail, check console.command.<command>, for example console.command.settime.

Two nodes are worth knowing about:

• console.open decides whether a player may open the console in game at all. By default only operators have it, so a moderator cannot use their moderation commands in game until you grant it: perm grant "Mod Name" console.open.
• console.command.* covers every generated command node. Operators also use it to run the game's own console commands (such as give, changecash, teleport or spawnvehicle) through S1DS, which relays them to the server after the permission check.

Wildcards such as permissions.*, console.command.* or plain * are allowed.

When rules conflict

When more than one rule matches, S1DS decides in this order:

1. A more specific rule beats a wildcard.
2. A rule on the user beats a rule on their group.
3. A higher priority group beats a lower one.
4. If everything else is equal, deny beats allow.

Staff also need to outrank the person they act on. A moderator holding player.kick still cannot kick an operator.

Editing permissions.toml

The file groups sections by what they describe: [group.<name>], [user.<steamid>], [tempallow.<id>], [tempdeny.<id>], [tempgroup.<id>] and [ban.<steamid>]. A custom group looks like this:

[group.helper]
priority = 15
inherits = ['support']
allow = ['player.list', 'player.kick', 'console.open']
deny = []

Save the file and run reloadpermissions. Unknown sections and comments are kept, so hand edits survive when the server rewrites the file.

Using commands in game

1. Get a group with console.open, which means operator unless you granted it to another group.
2. Join the server with the S1DS client mod installed (see how to join a Schedule 1 dedicated server).
3. Open the game's console and type the command without a slash, for example listplayers.

If you get "You do not have permission to use" a command, your group lacks the node for it. Ask an operator to run perm info on you to see your effective rules.

Using the TCP console

The TCP console lets you run commands from another machine without joining the game. It is off by default. Enable it in server_config.toml:

[tcpConsole]
tcpConsoleEnabled = true
tcpConsoleBindAddress = '127.0.0.1'
tcpConsolePort = 4050
tcpConsoleRequirePassword = true
tcpConsolePassword = 'pick-a-long-password'

With the bind address left at 127.0.0.1, only the server machine itself can connect. To reach it remotely, change the bind address, open or forward TCP 4050, and always keep the password on, since the TCP console has full host access. Connect with any raw TCP client, such as nc or telnet:

nc your.server.ip 4050

You get a Password: prompt, then can type commands. TCP sessions do not stream the live log, so use logs 50 or tail 50 to see recent output. Type exit or quit to close the session.

Using commands on a GamezServers panel

On a hosted Schedule I server, the Console tab is the server's own console, so you type commands straight in, without a slash, and they run with full host access. There is no need to set up the TCP console or forward any ports.

The panel also has one click buttons for the everyday jobs: Save world, Players online, Server info, Set morning, Make operator and Kick player. Buttons that need a player or value ask for it first. You can add up to 12 of your own console buttons for commands you use often, such as settime 1800 or vanish. server_config.toml and permissions.toml are editable in the file manager, followed by reloadconfig or reloadpermissions.

FAQ

How do I become admin on a Schedule 1 dedicated server?

Type op followed by your name or SteamID64 in the server console, or add groups = ['operator'] under [user.<your steamid>] in permissions.toml and run reloadpermissions.

Why does the console say I lack permission?

Your SteamID64 is not in a group with the right node. Assign yourself operator or administrator in permissions.toml, then run reloadpermissions or restart the server.

Why can my moderators not open the console in game?

Only the operator group has console.open by default. Grant it with perm grant <name> console.open, or add it to the moderator group's allow list.

What is the difference between op and admin?

admin adds the administrator group: moderation plus save, reload config and vanish. op adds operator, which also covers shutdown, permission changes and every console command.

How do I change the time on a Schedule 1 server?

Use settime with a four digit time, for example settime 0700 for morning. For a permanent change in day speed, edit timeProgressionMultiplier.

Do Schedule 1 server commands use a slash?

No. Type them without a slash in every console, for example save or kick PlayerName.