DayZ logs

Use Logs to investigate startup failures, script errors, crashes or events no longer shown in Console. This read-only viewer opens the latest supported DayZ log files from the server’s profiles directory.

Available log types

Log	What it commonly contains
Console Log	General console output saved by the server.
Crash Log	Reports written after an abnormal process failure.
Admin Log	Admin and gameplay events captured by DayZ’s logging settings.
RPT Log	Configuration, startup, engine and script/runtime messages. Start here when investigating a startup failure.
Error Log	Dedicated error output, if DayZ writes a separate error file.
Script Log	Script diagnostics, including mod script errors when script logging is enabled.

Scroll to see all columns →

For each type, the panel selects the newest available file. Not available means no matching file was found. Check whether DayZ has written that log before treating it as a panel fault.

Match the file and its event timestamps to the startup or incident you are investigating. The newest file may belong to a later restart. DayZ’s native -adminlog option enables admin logging; -profiles selects its output directory. Additional admin-log settings decide which gameplay events are recorded.

Open and filter a log

1. Select the server you need and open Logs.
2. Choose its log type from the list on the left.
3. Above the viewer, verify the file name, capture time, path and size.
4. Type in Filter lines to limit the view to matching lines.

The filter matches without case sensitivity inside your browser and leaves the log file unchanged. Use an exception, mod name, player identifier or timestamp to narrow the results instead of a broad term like error.

The refresh icon discovers new files and reloads the selected log. After a crash, give the host time to finish writing before refreshing.

A practical troubleshooting order

If the server fails during startup:

1. Check the startup sequence in RPT Log, including the entries before the failure.
2. Look in Script Log for a mod name or script failure.
3. If the process exited, inspect Error Log and Crash Log.
4. Check the first named mod or file against the current Mods load order and Config.
5. Address one possible cause, restart and inspect the newly written log.

For gameplay or admin events, open Admin Log or Console Log and filter for the relevant player, action or time.

Keep the lines around the first relevant error when you filter. A warning such as Unknown object class can occur during a run that completes startup. A normal termination line confirms shutdown, but you’ll still need to check whether each mod configuration loaded. Fix the error tied to the failed behavior and compare the next run before removing mods or changing persistence.

Even when the panel shows Online, check for Errors during XML parse and skipped event/type entries. Resolve those messages before relying on the intended loot or event definitions.

Share the smallest useful excerpt

Send support the external server ID, approximate time and timezone, log type and a short excerpt around the failure. Remove player personal data, passwords, tokens and private addresses from the excerpt. Inspect startup headers and launch commands for credentials before sharing them.

Logs versus Console

Tool	Use it for
Console	Current output and actions, RCON and recent performance samples.
Logs	Saved DayZ profile logs for investigating past events.

Scroll to see all columns →

Clear in Console empties the browser view. The log files displayed on the Logs page remain intact.

If no logs are found

• Check that the server has completed at least one start.
• Verify the relevant DayZ/Advanced options have logging enabled.
• Check the profiles directory specified in the server’s launch parameters.
• Give the server time to finish writing and close the file before refreshing.
• If the server runs and every supported log type remains unavailable, ask VYKIX on Discord.