Skip to content

stop Action

Stops a server using the configured control API.

Control API required

All server management actions require:

See Servers for configuration details.

Shell Control API

When using the Shell Control API, the stop_command is required in the server's control API configuration.

MOTD caching

Before stopping a server, AutoStartStop automatically caches the server's MOTD (Message of the Day). This cached MOTD can be displayed when the server is offline using the respond_ping action with use_cached_motd: true.

Configuration

action:
  - stop:
      server: survival  # Required: Server name

Configuration fields

Field Default Description
server - The server name to stop

How it works

When the stop action is executed, AutoStartStop caches the server's MOTD (while the server is still online) and sends the stop command to the server using the configured Control API.

Example

rules:
  stop_empty:
    triggers:
      - empty_server:
          empty_time: 15m  # Trigger after server is empty for 15 minutes
          server_list:
            mode: whitelist
            servers:
              - survival  # Only monitor survival server
    action:
      - stop:
          server: survival  # Stop the empty server
This rule will automatically stop the server after it has been empty for 15 minutes.