Scheduling Commands from Discord

What /command-schedule does

/command-schedule puts the Command Manager in your Discord server. Same schedules, same execution engine, same audit trail as the panel - you are looking at one thing through two windows.

You need the bot linked to your GameGrid account first. See Discord Bot Setup if you have not connected it.

Every reply is ephemeral - only you see it. Scheduled commands and their output can carry admin passwords and player IP addresses, so nothing from this command is posted into the channel.

You usually do not need the server ID

Every subcommand takes an optional server-id. Leave it blank and the bot uses the server bound to the channel you are typing in.

/command-schedule list

If the channel is not bound to a server, or you want a different one, start typing in server-id and the bot autocompletes from the servers you actually have.

/command-schedule list server-id: Community Survival

Binding a channel to a server is the setting that makes this whole command comfortable to use. It is covered in Discord Bot Setup.

The nine subcommands

Those two Discord roles map to the same API scopes the panel uses: command_schedules:read for the reads, command_schedules:write for create, edit, delete and toggle, and command_schedules:control for run.

Start with `catalog`. It is the authoritative list of command IDs for the command: option, and it reports how many commands the game has. Guessing a command ID is the most common way a create fails.

Creating a schedule

create takes a name, a command ID, and a cron expression. Parameters and timezone are optional.

/command-schedule create
name: Hourly Save
command: saveworld
cron: 0 * * * *

A command that takes parameters gets them as JSON in params:

/command-schedule create
name: Daily Notice
command: say
cron: 0 12 * * *
params: {"message":"Happy hunting!"}

The timezone default catches people out. The Discord command does not pick up the timezone on your GameGrid profile, so if you think in local time, pass timezone: explicitly.

What you can and cannot set from here

A schedule created from Discord is not missing those settings - it takes their defaults. It runs on schedule regardless of server state, skips an occurrence if the previous run is still going, will still fire up to 15 minutes late, does not spread its start, and is flagged late after one missed run.

Schedules built in the panel work here in full. list shows them with their next run, history numbers each step of a multi-step run, and run fires the whole sequence.

Cron in one table

Five fields: minute, hour, day-of-month, month, day-of-week.

The expression is read in the timezone you pass on timezone:, or UTC if you pass none.

The timezone on a schedule is now actually used when it fires. Before September 2026 it was stored and never read, so every schedule ran on UTC whatever it said. If you set schedules up before then and worked around it by shifting the hour, open them in the panel and check the "next five runs" preview.

Minecraft examples

/command-schedule create name: Auto Save command: save-all cron: */30 * * * *

/command-schedule create name: Restart Warning command: say cron: 0 4 * * *
params: {"message":"Server restarting in 10 minutes"}

/command-schedule create name: Daily Daylight command: time-set cron: 0 6 * * *
params: {"value":"day"}

/command-schedule create name: Clear Skies command: weather cron: 0 * * * *
params: {"type":"clear"}

/command-schedule create name: No Griefing command: gamerule cron: 0 5 * * *
params: {"rule":"mobGriefing","value":"false"}

Anything the catalog does not list goes through custom:

/command-schedule create name: Player Check command: custom cron: */10 * * * *
params: {"command":"list"}

Minecraft runs show as Sent, unconfirmed rather than a green tick. Its console carries no reply, so we can confirm delivery and nothing more. That is honesty, not a fault.

7 Days to Die examples

/command-schedule create name: Hourly Save command: saveworld cron: 0 * * * *

/command-schedule create name: Evening Airdrop command: spawnairdrop cron: 0 20 * * *

/command-schedule create name: Roster Log command: listplayers cron: */30 * * * *

/command-schedule create name: Friday Horde command: spawnwh cron: 0 21 * * 5

/command-schedule create name: Coffee Round command: buffplayer cron: 0 18 * * 5
params: {"player":"172","buff":"CoffeeStaminaBoost"}

Palworld examples

/command-schedule create name: Auto Save command: save cron: */30 * * * *

/command-schedule create name: Restart Warning command: broadcast cron: 50 3 * * *
params: {"message":"Server restarting in 10 minutes"}

/command-schedule create name: Event Alert command: pdalert cron: 0 19 * * 6
params: {"message":"Event starting now"}

/command-schedule create name: Weekly Wood command: pdgiveitem cron: 0 18 * * 5
params: {"playerId":"steam_76561198000000000","itemId":"Wood","count":50}

Player IDs are platform-prefixed - steam_, gdk_ or ps5_. Find them with ShowPlayers on the Console tab.

Five of Palworld's eleven commands are PalDefender commands (pdalert, pdreloadconfig, pdgiveexp, pdgiveitem, pdgivepal) and fail if PalDefender is not installed. And if every Palworld schedule is failing, check AdminPassword - without it there is no REST API to send anything to.

Valheim examples

/command-schedule create name: Hourly Save command: save cron: 0 * * * *

/command-schedule create name: Restart Warning command: broadcast cron: 0 4 * * *
params: {"message":"Server restarting in 10 minutes"}

/command-schedule create name: Bridge Health command: health cron: */5 * * * *

/command-schedule create name: Daily Wood command: spawn cron: 0 18 * * *
params: {"player":"PlayerName","item":"Wood","quantity":10}

Valheim runs through the GameGrid Bridge plugin, not RCON or telnet. The catalog is seven entries: broadcast, save, spawn, players, info, health, and a custom that accepts only those same six.

A Valheim world save can hold the game for up to 90 seconds on a large world, and scheduled saves are given that time. They used to be cut off at 15 seconds and recorded as errors even though they had completed.

Windrose examples

Read this first. Windrose has no broadcast, say or chat command of any kind, so no Windrose schedule can put a message in front of players. Restart warnings have to go out in Discord or in the server description.

What Windrose scheduling is good at is keeping a record:

/command-schedule create name: Hourly Status command: status cron: 0 * * * *

/command-schedule create name: Uptime command: uptime cron: 0 * * * *

/command-schedule create name: Entity Count command: entities cron: 0 */6 * * *

/command-schedule create name: Perf Snapshot command: perf cron: 30 */6 * * *

/command-schedule create name: Support Snapshot command: doctor cron: 0 5 * * 1

/command-schedule create name: Version Log command: version cron: 0 5 * * 1

Seven Windrose Plus commands are deliberately absent from the catalog. Each was measured against a live server:

custom will still send them, and they will still not do what you want. See Windrose Admin Commands Reference.

Checking what happened

/command-schedule history schedule-id: 3f9c1a2b

Shows the last 10 executions. A multi-step run is numbered, so a five-step schedule reads as five step rows and a summary rather than six identical ones.

Every execution is logged wherever it was triggered from - the schedule itself, the panel, or run here. All of create, edit, delete, toggle and run are recorded in the audit log.

When something is not behaving, Command Manager Troubleshooting goes through each status and what to check.

The same schedules, elsewhere