DayZ logs

The Logs page is a read-only viewer for the newest supported DayZ log files under the server’s profiles directory. Use it for startup failures, script errors, crashes, and events that are no longer visible in the live Console.

Available log types

Log	What it commonly contains
Console Log	General server console output recorded to a file.
Crash Log	Crash report details generated after an abnormal process failure.
Admin Log	Administrative and gameplay events recorded by DayZ logging settings.
RPT Log	Startup, configuration, engine, and script/runtime messages. This is often the best first log for a startup problem.
Error Log	Error-specific output when DayZ produces a separate error file.
Script Log	Script diagnostic output, including mod script problems when script logging is enabled.

Scroll to see all columns →

The panel opens the newest available file for each type. A disabled type marked Not available means no matching file currently exists; it does not mean the feature is broken.

Open and filter a log

1. Open Logs for the correct server.
2. Select a log type in the left list.
3. Check the file name, captured time, path, and size above the viewer.
4. Enter text in Filter lines to show only matching lines.

Filtering is case-insensitive and happens in your browser. It does not modify the file. Search for a specific exception, mod name, player identifier, or timestamp rather than a broad word such as error.

Select the refresh icon to discover the newest files and reload the current log. If the server has just crashed, allow the host time to finish writing the file before refreshing.

A practical troubleshooting order

For a server that fails during startup:

1. Open RPT Log and inspect the final startup lines.
2. Check Script Log for a named mod or script failure.
3. Check Error Log and Crash Log if the process exited.
4. Compare the first named mod/file with the current Mods load order and Config.
5. Change one cause at a time, restart, and check the new log.

For a gameplay or administrative event, start with Admin Log or Console Log and filter by player, action, or time.

Share the smallest useful excerpt

When contacting support, include the server’s external ID, approximate event time and timezone, log type, and only the lines around the failure. Remove player personal data, passwords, tokens, and private addresses before sharing.

Logs versus Console

Tool	Use it for
Console	Live output, current actions, RCON, and short-term performance metrics.
Logs	Persisted DayZ profile files and investigation after an event.

Scroll to see all columns →

The Console’s Clear action only clears your current browser view. It does not delete the files shown on the Logs page.

If no logs are found

• Confirm that the server has started at least once.
• Check that logging is enabled in the relevant DayZ/Advanced settings.
• Confirm the server uses the expected profiles directory in its launch parameters.
• Refresh after the server has had time to write and close the file.
• If the server runs but all supported types remain unavailable, ask VYKIX on Discord.