Skip to main content
Features

Change Map, Restart and Shutdown

Map changes, restarts and shutdowns run after a countdown. Players are warned at set intervals, and the action can be cancelled at any time.

Commands​

CommandDescriptionPermission
/map <map> [delay]Change map (default delay 10s)serveradmincore.map
/mapsList available maps and aliasesserveradmincore.map
/restart [delay] [reason]Restart (default delay 60s)serveradmincore.restart
/shutdown [delay] [reason]Shut down (default delay 60s)serveradmincore.shutdown
/cancelCancel the scheduled actionserveradmincore.cancel
/statusShows the scheduled action and time leftserveradmincore.players
/map Arena
/map /Game/Maps/Desert?game=TDM 30
/restart 5m Applying update
/shutdown 120 Maintenance
/cancel

A plain number delay is seconds. Durations like 5m also work. Only one action can be scheduled at a time, and a new one replaces the old.

Countdown warnings​

Players are warned when the time left passes each value in Countdown Warnings (default 600, 300, 120, 60, 30, 15, 10, 5, 4, 3, 2, 1 seconds). The texts are configurable:

SettingDefault
Restart Warning MessageServer restarting in {Time}. {Reason}
Shutdown Warning MessageServer shutting down in {Time}. {Reason}
Map Change Warning MessageChanging map to {Map} in {Time}.

Warnings are sent as Banner announcements, and as Warning in the last 10 seconds.

Maps​

/map accepts:

  • An alias from Map Aliases, e.g. arena → /Game/Maps/Arena
  • A short map name, e.g. Arena, searched in Map Search Paths (default /Game)
  • A full path, e.g. /Game/Maps/Arena
  • Any of these followed by travel options, e.g. Arena?game=TDM
note

For a packaged server, make sure your maps are cooked: add them to Project Settings → Packaging → List of maps to include in a packaged build.

Restart modes​

Restart Mode decides what a restart does on a dedicated server. On a listen server a restart always reloads the current map, since the server is the host's game.

ModeWhat happensUse when
Relaunch Process (default)Saves, kicks everyone, starts a new server process with the same command line and exits. The new process waits until the old one is gone, so ports are free.You start the server yourself, from a terminal, a script or a shortcut
Exit ProcessSaves, kicks everyone and exits with Restart Exit CodeYour server runs under a supervisor that starts it again: systemd, Docker (restart: always), Windows services, a hosting panel
Reload MapReloads the current map, the process keeps runningYou only want a fresh map state
note

With Relaunch Process on Linux, the new server keeps printing its log to the same terminal, but it runs in the background, so typing commands into that terminal stops working after the first restart. If you want console input across restarts, run the server under a supervisor with Exit Process, inside screen or tmux.

Example systemd unit:

/etc/systemd/system/mygame.service
[Service]
ExecStart=/opt/mygame/MyGameServer.sh -log
Restart=always
RestartSec=5

Shutdown​

Saves all data, kicks every player with the Shutdown Kick Message and exits the process.

info

In the editor, exiting the process is skipped and a warning is logged instead, so your editor doesn't close.

Blueprint​

NodeDescription
Change Map (Caller, Map, Delay Seconds)
Restart Server (Caller, Delay Seconds, Reason)
Shutdown Server (Caller, Delay Seconds, Reason)
Cancel Pending Action (Caller)
Get Pending Action → ActionType, target, reason, remaining seconds
Get Available MapsFull package names
Resolve Map (Map) → Travel URL

Event: On Pending Action Changed (Action). Use it to show a countdown in a server UI.