# Schedule 1 Server Commands Reference (/docs/schedule-1/commands-reference)



import { Callout } from 'fumadocs-ui/components/callout';

The S1 DedicatedServerMod exposes a focused command set. Run them from the panel **Console** tab — or from the TCP console if you've enabled remote admin (see [Operators, Admins & TCP Console](/docs/schedule-1/operators-admins)).

<Callout type="info">
  This is the command list as documented at [docs.s1servers.com/commands](https://docs.s1servers.com/). The list is intentionally small in the current release — the mod doesn't ship `say`-style broadcasts, teleport, or in-game whisper commands. Behavior changes by mod version; cross-check upstream for the latest.
</Callout>

Access to each command is governed by the permissions system. Default groups grant access to a subset — operators get all of it.

***

Server commands [#server-commands]

| Command             | Syntax              | What it does                                                              |
| ------------------- | ------------------- | ------------------------------------------------------------------------- |
| `help`              | `help`              | Show command help. Available to everyone by default.                      |
| `serverinfo`        | `serverinfo`        | Print server status — uptime, player count, build version.                |
| `save`              | `save`              | Trigger a manual world save.                                              |
| `reloadconfig`      | `reloadconfig`      | Re-read `server_config.toml` without restarting.                          |
| `reloadpermissions` | `reloadpermissions` | Re-read `permissions.toml`. Group / user / ban changes apply immediately. |
| `listplayers`       | `listplayers`       | List connected players (names + Steam IDs).                               |

***

Player commands [#player-commands]

Need `player.kick`, `player.ban`, or `player.unban` permission (the `moderator` group and up has these by default).

| Command | Syntax                              | What it does                                          |
| ------- | ----------------------------------- | ----------------------------------------------------- |
| `kick`  | `kick <player_name_or_id> [reason]` | Disconnect a player. Reason is shown to them.         |
| `ban`   | `ban <player_name_or_id> [reason]`  | Ban a player. Reason is logged in `permissions.toml`. |
| `unban` | `unban <steamid>`                   | Remove a ban entry.                                   |

***

Permission commands [#permission-commands]

| Command | Syntax                                                    | What it does                                         |
| ------- | --------------------------------------------------------- | ---------------------------------------------------- |
| `group` | `group <list \| assign \| unassign> ...`                  | List groups, assign or unassign a user.              |
| `perm`  | `perm <info \| grant \| deny \| revoke \| tempgrant> ...` | Inspect or mutate direct permission nodes on a user. |

These are the raw permission-system commands. For most admin work the compatibility wrappers below are easier.

***

Built-in group wrappers [#built-in-group-wrappers]

These exist for ergonomic admin without editing `permissions.toml` directly. Each is a thin wrapper that adjusts the user's group membership.

| Command             | Effect                                 |
| ------------------- | -------------------------------------- |
| `op <steamid>`      | Add user to the `operator` group.      |
| `deop <steamid>`    | Remove user from `operator`.           |
| `admin <steamid>`   | Add user to the `administrator` group. |
| `deadmin <steamid>` | Remove user from `administrator`.      |

***

Running commands from the panel [#running-commands-from-the-panel]

<Callout type="info">
  You don't need to be in-game to administer the server. The panel's **Console** tab is wired directly to the server's command interface.
</Callout>

1. Open your Schedule 1 server in the panel.
2. Click **Console** in the sidebar — or scroll down on the Dashboard, the console is also embedded there.
3. Type the command and press Enter. Output appears in the same window.
4. The panel logs every command sent for the per-user activity log.

Use `Up` / `Down` arrows to cycle through your last 32 commands. `Ctrl+F` opens an in-console search.

***

Running commands remotely (TCP console) [#running-commands-remotely-tcp-console]

If you've enabled `[tcpConsole]` in `server_config.toml`, connect over TCP (default localhost:4050). Any line-based TCP client works — Netcat, custom scripts, or a dedicated tool.

See [Operators, Admins & TCP Console](/docs/schedule-1/operators-admins) for the tunneling guide.

***

Scheduling commands [#scheduling-commands]

Use the panel's **Schedules** tab to run commands on a cron — typical patterns:

* Nightly save before peak hours
* Weekly `reloadpermissions` if you batch-edit the TOML

See [Scheduled Restarts](/docs/schedule-1/scheduled-restarts) for cron syntax and how to add a "Send Console Command" task.

***

What's not a command [#whats-not-a-command]

People often ask for these — they don't exist in the documented command set:

* `say` / broadcast — no built-in chat broadcast command
* `tp` / teleport — no teleport
* `mute` / `tempmute` — no chat mute
* `restart` / `stop` — not documented; use the panel **Dashboard** Stop / Restart buttons
* `world wipe` — no wipe command. Wipe via file manager. See [Reset Your Server](/docs/schedule-1/reset-server)

If you need any of these, watch the upstream releases page — features land in new versions.

***

Related Guides [#related-guides]

* [Operators, Admins & TCP Console →](/docs/schedule-1/operators-admins)
* [Server Config Reference →](/docs/schedule-1/server-config)
* [Scheduled Restarts →](/docs/schedule-1/scheduled-restarts)
* [Troubleshooting →](/docs/schedule-1/troubleshooting)