Schedules
Run Minecraft server commands automatically on a timer: restarts, announcements, backups.
What schedules do
AdminSchedules run things on the server automatically on a timer: a nightly restart, a recurring in-game announcement, a world backup, or a console command. Manage them on the Schedules page for the selected server. A Back up the world task backs up the world and its pack like Back up now on the World page, and can skip runs when no one has played since the last one. Managing schedules needs the Restarts permission, and a backup task needs Backups too. A command task, or a restart with its own stop command, also needs the Console Run commands permission to create or edit, and only teammates with Read console see its console line. Restart and command tasks need a paid plan; announcements and world backups are free on every plan. Each server holds 3 schedules on Free, 10 on Basic and 25 on Pro.
Creating a schedule
Admin- Open the Schedules page and add a schedule
- Enter the server command(s) to run
- Set when it runs: a recurring interval or a time of day
- Save; Madsi fires it against the connected server on schedule
Schedules run through the same secure connection as the console; no RCON port required.
Restarting right now
AdminA one-off restart doesn't need a schedule. Restart in the header of the server's Status page, and Restart to apply in the Installed mods list once an update is downloaded, offer the same choices: now, in 1 minute, in 5 minutes, or When no one's online. That last one waits for the last player to leave and then restarts, right away if no one is on; it is kept through Madsi's own updates, and dropped if the server restarts some other way first. A delay warns players in game and posts the countdown to whichever channel the Restart warnings event routes to, and the banner on the Status page cancels it until it fires. Restarting needs the Restarts permission and a paid plan.
Madsi cannot relaunch a server itself. It runs the stop command (stop, or whatever command your restart schedules use) and your host starts it again: systemd, Docker and most panels do. Route the Restart warnings event to a channel and Madsi waits five minutes for the server to return, then says so there if it hasn't.