Skip to main content
The server detail overview includes lifecycle controls and a live console. Catalyst starts Java directly, watches output, tracks status, and sends selected events back to the renderer.

​
Status states

​
Starting a server

1

Accept EULA

If the server has not accepted the EULA, Catalyst asks for confirmation before writing eula=true.
2

Prepare Java

Catalyst uses the server’s custom Java path when set. Otherwise it picks a compatible detected or managed runtime.
3

Spawn Java

The process starts with memory flags, G1GC/Aikar-style tuning flags, and -jar server.jar nogui.
4

Watch logs

Startup changes to Online when Catalyst sees the normal ready message.

​
Console behavior

  • Console output is streamed through IPC and kept to a bounded history.
  • ANSI colors are rendered in the UI.
  • The command box is disabled while the server is offline.
  • Commands are sent without a leading slash.
  • The exact restart command is intercepted so Catalyst can perform an app-managed restart.
Use Catalyst’s restart button for restarts. It preserves the app’s state handling and can restart ngrok tunnels when needed.

​
Stop and restart

Catalyst stops servers by sending save-all flush, then stop. If Java does not exit within the timeout, Catalyst kills the process and marks the server offline. A restart is a stop followed by a fresh start. If ngrok is enabled and configured, the tunnel can be restored after the server returns online.

​
Automatic world saves

While a server is online, Catalyst periodically sends save-all flush to reduce the risk of world data loss.