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



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

The S1 DedicatedServerMod exposes commands through three channels — pick whichever fits the moment:

1. **In-game chat** — type `/<command>` if you're an operator or admin with permission
2. **XGamingServer panel → Console tab** — send commands without being connected to the game
3. **RCON** — if you've enabled remote console (see [Operators, Admins & RCON](/docs/schedule-1/operators-admins))

<Callout type="info">
  Commands and exact syntax can shift between DedicatedServerMod releases. The authoritative current list is at [docs.s1servers.com/commands](https://docs.s1servers.com/). This page covers the common ones you'll actually use.
</Callout>

***

Server commands [#server-commands]

Run these from the **Console** tab in your panel — they work even when no players are connected.

| Command         | What it does                                                                    |
| --------------- | ------------------------------------------------------------------------------- |
| `help`          | List every available command on your current build                              |
| `save`          | Force-flush the world to disk (good before any risky config change)             |
| `stop`          | Graceful shutdown — players get a kick reason, save flushes, then server exits  |
| `restart`       | Stop + start (use this instead of force-killing from the panel for clean saves) |
| `reload`        | Re-read the DedicatedServerMod config without restarting the server             |
| `say <message>` | Broadcast a message to every connected player                                   |
| `status`        | Print server uptime, player count, MelonLoader version, loaded mods             |

> The panel also has a **Restart** button that runs `stop` + start under the hood — it's safe to use instead of running `restart` manually.

***

Player management commands [#player-management-commands]

These need operator or `kick` / `ban` / `mute` permission (see [Operators, Admins & RCON](/docs/schedule-1/operators-admins)).

| Command                     | Example                         | Effect                                       |
| --------------------------- | ------------------------------- | -------------------------------------------- |
| `list`                      | `list`                          | Print connected players + Steam IDs          |
| `kick <player>`             | `kick BobTheBuilder reason=AFK` | Disconnect a player; reason is shown to them |
| `ban <steamid>`             | `ban 76561198000000000`         | Permanent ban by Steam ID                    |
| `tempban <steamid> <hours>` | `tempban 76561198000000000 24`  | Time-limited ban                             |
| `unban <steamid>`           | `unban 76561198000000000`       | Lift a ban                                   |
| `mute <player> <minutes>`   | `mute Bob 30`                   | Block chat for N minutes                     |
| `unmute <player>`           | `unmute Bob`                    | Lift a mute                                  |
| `tp <a> <b>`                | `tp Alice Bob`                  | Teleport Alice to Bob's position             |
| `whisper <player> <msg>`    | `whisper Bob be careful`        | Private message                              |

***

Admin / permission commands [#admin--permission-commands]

For managing who gets to run what.

| Command                       | Effect                                                               |
| ----------------------------- | -------------------------------------------------------------------- |
| `op <steamid>`                | Grant full operator (use sparingly)                                  |
| `deop <steamid>`              | Revoke operator                                                      |
| `admin add <steamid> <group>` | Add an admin and assign them to a permission group defined in config |
| `admin remove <steamid>`      | Remove admin                                                         |
| `admin list`                  | List current admins and their groups                                 |
| `perms list`                  | List permission groups defined in your config                        |

***

Save / world commands [#save--world-commands]

| Command                | Effect                                                                                                          |
| ---------------------- | --------------------------------------------------------------------------------------------------------------- |
| `save`                 | Snapshot to disk now                                                                                            |
| `save-on` / `save-off` | Toggle autosave (re-enable before shutting down or you'll lose recent state)                                    |
| `world reset confirm`  | Wipe the current world. **Destructive — back up first.** See [Reset Your Server](/docs/schedule-1/reset-server) |

***

Sending commands from the panel [#sending-commands-from-the-panel]

<Callout type="info">
  You don't need to be in-game to administer the server. The XGamingServer panel's **Console** tab pipes directly into the DedicatedServerMod stdin.
</Callout>

1. Open your Schedule 1 server in the panel
2. Click **Console** in the sidebar (or scroll to the bottom of the Dashboard — there's an inline console)
3. Type the command (no `/` prefix needed from the panel console; that prefix is only for in-game chat) and press Enter
4. Output appears in the same console — including any error messages

The panel logs every command sent, so you have an audit trail of who ran what (per panel sub-user).

***

Scheduling commands [#scheduling-commands]

Use the panel's **Schedules** feature to run commands on a cron:

* Warning broadcasts before scheduled restarts (`say Server restarting in 5 minutes`)
* Nightly forced saves
* Daily `kick` of anyone idle (via a custom script)

See [Scheduled Restarts](/docs/schedule-1/scheduled-restarts) for the cron syntax and task setup.

***

Related Guides [#related-guides]

* [Operators, Admins & RCON →](/docs/schedule-1/operators-admins)
* [Web Panel →](/docs/schedule-1/web-panel)
* [Scheduled Restarts →](/docs/schedule-1/scheduled-restarts)
* [Troubleshooting →](/docs/schedule-1/troubleshooting)