Updated 11 October 2026

Every DayZ server on Nitrado keeps an admin log: a text file with a line for every kill, hit, death, connection and placed item. Killfeed bots, Law's KillFeed included, work by reading it. On Xbox and PlayStation it is the only window into what happens on your server, since console servers can't run mods.

The log is on by default, so the kill feed works without changing anything. One setting, Player List Logging, adds every player's position to it. This guide shows where the log is and why that setting matters.

What the admin log records

  • Kills and deaths: who killed whom, with what weapon, from how far, and PvE deaths such as zombies, falls and bleeding out.
  • Hits: every hit a player takes, with the body part and damage.
  • Connections: players joining and leaving.
  • Building: items placed, built and dismantled.
  • Unconscious players: when someone is knocked out and when they come round.

Where to find it

The admin log is a file ending in .ADM in your server's config folder on Nitrado. The one being written right now is DayZServer_X1_x64.ADM on Xbox and DayZServer_PS4_x64.ADM on PlayStation. Every restart starts a new log, and the older ones stay in the folder with the date and time in their name.

You don't need to open it yourself. The Server Files page in the dashboard shows your logs read-only, and on the paid plan /getlogs downloads them from Discord.

Turn on Player List Logging

  1. Log in to Nitrado and open your DayZ server.
  2. Go to the server's General settings.
  3. Turn on Player List Logging and save.
  4. Restart the server. Positions show up from the next log onwards.

With it on, the server writes every online player's position to the admin log. Law's KillFeed needs that for player locations, map images and heatmaps, online player lists, player trails on the live map and the paid plan's zone entry checks. Without it, the kill feed and other feeds still work, but those stay empty.

From log to Discord

Law's KillFeed reads your admin log through your Nitrado account every two minutes and turns new lines into Discord posts: the kill feed, PvE deaths, connections and the build log, each in its own channel. That is why a kill shows up a few minutes after it happens, not instantly. Set up the killfeed to get started.

// Survivor intel

Questions

Do I have to turn on admin logs for a killfeed?

No. Nitrado writes the admin log by default, and the kill feed reads it as it is. Only player positions need Player List Logging.

Why do maps and online lists show no players?

Player List Logging is off. Turn it on in your Nitrado server's General settings and restart: positions appear from the next log.

Why does a kill take a few minutes to post?

The server writes the kill to the admin log first, and the bot reads the log every two minutes. If nothing shows up at all, run /troubleshoot in Discord.

// Loadout

Features in this guide

Server Logs

PvE deaths, connections with combat-log checks, and a build log with location links.

Maps & Tracking

Player positions, map images, PvP heatmaps and movement paths on Chernarus, Livonia and Sakhal.

Kill Feed

PvP kills with weapon, distance, hit zone and damage, plus long-distance and streak feeds.

// More intel

More guides

Killfeed setup for Xbox & PS5

Connect your Nitrado console server to Discord and get kills, deaths and joins posted for free.

Safe zones on console

Draw a zone around your trader or spawn and ban or unwhitelist anyone who kills inside it.