Skip to content

Console and power controls

Open Console to start, stop or monitor the selected server. It shows the current state, command progress, live RCON/RPT/system messages and recent performance samples.

  • Notify players before planned downtime.
  • Save changes open in Config, Advanced or the file editor.
  • Take a current backup before updates or configuration changes that could affect service.
  • Let an existing Starting or Stopping state complete.

Power and RCON availability are set by your service policy. A disabled button can indicate an incompatible state, another command in progress or an action your service does not permit.

Control What it checks When to use it
Check status Asks the host whether the selected server exists and what state it is in. The displayed state is stale, Unknown, or does not match player reports.
Check version Compares the installed server version against the game-title version on the host. A game update has landed or clients report a version mismatch.
Scroll to see all columns →

Check version compares files already on the host. It neither searches Steam for a new release nor installs updates. Its result can indicate:

  • Server and host title versions match.
  • The server has a different installed version.
  • A host download is in progress or title files are locked.
  • The host returned no usable version comparison.

Rate limits may apply to version checks. Sending more requests will not speed up an update.

If the versions match, the server matches the files on its host. Those files may still need a Steam update. Follow Update a DayZ server for the steps that fit your hosting type.

Control Effect Typical use
Start Starts the server from an offline state. Bringing service back after maintenance.
Restart Tracks the stop and start of an online server as one action. Applying saved settings or mod changes during scheduled downtime.
Stop Ends the running server process. Work that cannot be done while the process writes data.
Scroll to see all columns →

Wait for the progress message after requesting an action. It may move through accepted, connecting, dispatching, waiting, completed or failed stages. Verify the final server state before sending another request.

Confirm that the shutdown log reports normal termination before changing persistence files or copying an offline backup. If the process stalls, ask support how the host will stop it; the Stop button alone won’t tell you.

Use RCON to send an administration command while the DayZ server is online.

  1. Check that the server is Online.
  2. Type a complete command into the RCON field. For example, say -1 Server restart in 5 minutes sends a BattlEye message to all players. This announces a restart; it does not schedule or perform one.
  3. Press Send once.
  4. Read the system message and console output to verify the result.

An offline server cannot receive RCON, and service policy may also disable it. Treat command text as logged: the game server, RCON client or service may retain it.

The live view includes these message sources:

Source Content
RCON Player and server messages received on the RCON stream.
RPT DayZ runtime reports, including startup and script output.
System Status, action and connection messages created by the panel.
Scroll to see all columns →

Select sources with the checkboxes; hiding one does not delete its lines. Enter Filter text to match a line’s content, source, channel or timestamp.

Control Meaning
Follow Scrolls to the newest matching line. Disable it to read earlier output.
Pause Holds the visible lines in place while collection continues. It does not pause the server.
Clear Removes visible console lines and metric samples from this browser view. DayZ log files remain intact.
Scroll to see all columns →

If messages stop arriving, inspect the header’s connection indicator, refresh once and select Check status. Read the Logs guide to inspect saved profile files beyond the current live session.

If the host provides samples, Console displays recent trends in:

  • CPU usage
  • Memory use
  • Network traffic
  • Player count and maximum players
  • Disk read and write counters

These samples cover recent operation rather than long-term monitoring. An empty chart can reflect pending or unavailable host data. Check the process state, saved logs and a player connection before diagnosing downtime.

Look for repeated behaviour across samples. If CPU use keeps reaching its limit during the same gameplay event, investigate that event. One short peak tells you less about the cause.

Problem Check
An action button is disabled Let the current state or action finish and confirm that your service permits the operation.
Server is Online but players cannot connect Verify address and ports in Network, then read the RPT/error logs.
Version mismatch remains Run one version check, wait for any host download to finish and restart during maintenance.
No RCON output appears after a successful command Some commands return no visible response. Check the intended effect or saved logs.
Console has too much output Pause the view, show the relevant source and filter for an error, player or timestamp.
Scroll to see all columns →