Using the Terminal

The Terminal tab is the main screen you’ll use day-to-day — your server’s live console output, plus a command box to control it.

Power Controls

Above the output, three buttons control the server’s power state:

Start — boots the server
Restart — stops and starts it again, applying any config changes that need a restart
Stop — shuts it down gracefully (saves the world first)

Warning

If Stop doesn’t respond within a reasonable time, a Kill option appears. Only use it as a last resort — it force-terminates the process without saving, so anything since the last auto-save can be lost.

Sending Commands

Type into the box at the bottom and press Enter. Commands typed here run without a leading / — it’s already a command line, not chat.

bash

stop
say Server restarting in 5 minutes

Anything sent from here always runs with full operator/server-operator permissions, regardless of any in-game permission setup — see Granting Operator Permission if you also need specific players to have standing access in-game.

Reading the Log

The console output keeps scrolling as your server runs — startup progress, player join/leave messages, crashes, and anything your commands print back. If something’s gone wrong, this is the first place to look; most error messages point directly at the problem (a missing file, a bad config value, a port conflict).

Tip

Use your browser’s find-in-page (Ctrl/Cmd+F) to search recent output instead of scrolling manually — useful when tracking down one specific error in a long startup log.

Checking What Happened

Every command you (or a sub-user) send is logged with a timestamp and who sent it — check the Activity tab if you need to reconstruct what happened and when, not just what the log currently shows on screen.