Skip to content
CatalystCatalyst Docs

Console

The Console tab shows everything your game server prints — startup messages, player joins, errors — as it happens. It keeps up to 2,000 lines in its buffer; older output scrolls away.

Prerequisites

Section titled “Prerequisites”
  • A server you can access, with the console.read permission to watch output and console.write to send commands.
  • A running server to send commands — the command box is disabled otherwise.

The status pill at the top left tells you where the live stream stands: Live, Connecting, Reconnecting, or Disconnected.

Run a command

Section titled “Run a command”
  1. Type into the command box at the bottom ($) and press Enter, or select Send.
  2. Commands run as the server itself, exactly as if you typed them into its own terminal:
    • Minecraft: say Hello, whitelist add Notch, tps
    • Source games: status, changelevel de_dust2

The box is disabled unless the server is running, the stream is connected, and you have the console.write permission. Press the Up and Down arrows to step through recent commands, or Tab to complete from history.

Console controls

Section titled “Console controls”

The toolbar above the output has one control per stream plus a few view tools:

  • stdout / stderr / system / stdin — toggle which streams are shown. On a narrow screen they collapse into a Streams menu with the active count.
  • Find (the magnifier, or Ctrl+F while the console has focus) — search the visible output; Enter jumps to the next match, Shift+Enter to the previous one.
  • Buffer size — how many lines the terminal keeps in view: 500, 1K, or 2K (1K by default).
  • Follow — auto-scroll as new output arrives. Scrolling up turns it off and shows a Follow button to resume.
  • Copy output and Download output — copy the visible lines, or save them as a .log file.
  • Clear console — clears the view (it does not delete stored logs).
  • Expand — full-screen the console; Esc or Collapse returns.

Read a crash

Section titled “Read a crash”

When a server will not stay up:

  1. Press Start and watch the first 50 lines — the real error is usually near the top, not at the end.
  2. Use Find to jump to ERROR, Exception, missing, or port already in use.
  3. Common causes and fixes live in server issues.

Console vs. logs

Section titled “Console vs. logs”

The console is a live view, not permanent storage. For history, use the Activity tab (who did what), Download output for the current buffer, or download log files from the Files tab (usually under logs/). Realtime integrations should use the event streams API rather than scraping the console.

Section titled “Related”