Schedules let you automate recurring tasks on a server without manual intervention. Each schedule has one or more triggers that define when it runs, a set of actions that execute in order, and optional pre-conditions that must be true before the actions begin.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/calagopus/panel/llms.txt
Use this file to discover all available pages before exploring further.
Creating a schedule
Set the trigger
Choose a trigger type. The most common is a Cron trigger — enter a standard five-field cron expression (minute, hour, day of month, month, day of week). For example,
0 4 * * * runs daily at 04:00.Enable or disable
Toggle the schedule on or off. A disabled schedule is saved but never runs automatically. You can enable it later from the schedule’s detail page.
Schedule triggers
Triggers define when a schedule executes. Multiple triggers can be added to a single schedule, and the schedule runs whenever any trigger fires. The current trigger types are:| Trigger | Description |
|---|---|
| Cron | Fires according to a cron expression evaluated in the server’s configured timezone |
Adding actions
Actions define what the schedule does when it runs. Navigate to the schedule’s detail page and click the Actions tab, then click Edit to open the actions editor. Actions execute in the order they are listed. Each action runs after the previous one completes or after an optional delay.Available action types
Send power action
Start, stop, restart, or kill the server.
Send command
Send a command string to the server console, as if you typed it manually.
Create backup
Trigger an immediate backup. Optionally specify a backup name and ignored file patterns.
Sleep
Pause execution for a specified number of seconds before running the next action.
File operations
Copy, rename, move, delete, compress, decompress, or write files.
Update startup
Change a startup variable value, Docker image, or the full startup command.
Wait for console line
Pause the schedule until a specific string appears in the server’s console output.
Match regex
Assert that a value matches a regular expression. The schedule stops if the match fails.
Example: daily restart with backup
A common pattern is to create a backup before restarting the server each night:- Create backup — take a backup before stopping
- Sleep — wait 30 seconds for the backup to complete
- Send power action — restart the server
Pre-conditions
Pre-conditions let you add logic that must be satisfied before the schedule’s actions run. Open the Conditions tab on the schedule detail page to configure them. If a pre-condition is not met when the schedule fires, the entire action list is skipped for that run. This is useful for avoiding unnecessary restarts when a server is already offline, or skipping a backup when no players are online.Triggering manually
You can run a schedule immediately from its detail page without waiting for the next scheduled time.The Trigger button is only available when the schedule is enabled and has at least one action configured.