The DayZ Killfeed, Leaderboard and Survivor Profiles

Where It Is, and What Makes It Possible

Your server's DayZ Tools page has a Killfeed tab. It holds the leaderboard and the feed of deaths, and a survivor profile opens over it from any name you click.

DayZ gives an ordinary server no kill report. The admin log records that somebody died, in free text, with no identifier for who killed them — and for some deaths it writes two lines for one death, so anything counting those lines counts wrong. GameGrid's own server-side mod is what makes a real killfeed possible: it is told about the death by the game at the moment it happens, and it reports the victim, the killer, the cause, the item in the killer's hands and the distance between them. Your players install nothing for it.

Deaths Are Kept

Deaths are recorded as they happen and stored, not held in your browser. Reload the page, restart the server, come back next week — the feed and the board are still there.

• Deaths are kept for a year. The all-time totals on the board are counters that keep going after that, so a server older than a year can honestly show a bigger all-time total than the last 30 days would suggest.
• Sessions are kept for 90 days, which is what the playtime column is measured from.
• A death is recorded once, whatever happens. A restart, a reconnection or a re-read never doubles a line up.
• The feed starts the day GameGrid started watching. The tab says so: "We have been recording deaths on this server since …". There is no history from before that, for anybody.

If events were lost before we could read them — a server down for a long time, for instance — the tab says so above the board rather than presenting an incomplete record as a complete one.

What a Killfeed Line Carries

Every death is classified by the mod at the moment it happens:

A player kill also carries the weapon — the class name of the item in the killer's hands — and the distance between the two of them.

Two players with the same name

Because "Survivor" is DayZ's own default name, two players in one line can genuinely be called the same thing. When that happens, and only then, the line adds each one's short code so it still means something. Every other line reads plainly.

Why a kill sometimes shows no weapon

The weapon is the item the killer had in their hands. Someone who kills with their fists has no item in hand, so there is nothing to name and the line shows the kill and the distance without a weapon.

That is the honest answer rather than a gap: the admin log's MeleeFist is the kind of damage, not an item, and writing it into the weapon field would hand you a name that resolves to nothing in your item list.

The filter

A Player kills only tick box hides everything the infected, animals and the world did, and leaves the deaths caused by another player.

The Leaderboard

Four periods, switched with the buttons above the board: This session, Last 7 days, Last 30 days and All time. All time is what you land on.

Ranking is by kills, then by fewest deaths.

• Only a player killing another player scores a kill. The infected, animals, falls and suicides count as deaths only, so a server with no PvP has a board full of deaths and no kills, which is correct.
• K/D is hidden until a player has 10 kills, and shows as — until then. A single lucky kill should not put somebody at the top of your board.
• Playtime is all-time on every period. It is not re-cut per window, and the column shows — on the windowed boards rather than a number that would be wrong.
• This session means since the server last started, so it empties on a restart. That is what a session is; the other three periods keep their history.

The board is capped at the top 50 on the panel.

Survivor Profiles

Clicking a name anywhere — the board, the feed, the survivor table, the map — opens that player's profile over the page. The profile is a link. It lives in the address bar as ?player=…, so you can copy the URL into a support ticket or your staff Discord and the person who opens it lands on the same profile.

Every section names its own source on the page, because "where did this number come from" is the first question anybody asks about a stat.

Things the profile deliberately does not have: any history from before GameGrid started watching, a player's inventory, hit zones or headshots (the mod does not report them), and any ban, kick or teleport button — those live where they belong, on the survivor table and the map.

A survivor with no profile

A name that has never joined or died on this server has no profile, and the page says exactly that rather than showing an error: "No record of this survivor on this server. A profile appears once GameGrid has seen them join or die here."

Who Can See What

Reading the board, the feed and a profile needs the View permission on the server. Acting on a player needs Manage.

• The board, the feed and the events list carry no identifiers for anybody, whatever your permission. They carry the name and the short code, and that is all.
• A profile's Identifiers section, and the IDs on the survivor table, are shown only with Manage, because those are what a ban, a whitelist entry or a priority-queue line is written with. A view-only member of your staff sees the board and the profile, and is told plainly why the identifiers are not there.

The short code is derived per server, so it is the same for one player everywhere on that server's pages and identical for every viewer — but it is not a DayZ ID and it cannot be pasted into ban.txt. See Steam64, DayZ Player ID and BattlEye GUID for the real ones.

Paying for Kills

If you run the in-game economy, kills and deaths can move a player's wallet on their own. The rules are not identical to the board's, on purpose — see Paying DayZ Players for Playtime, Kills and Deaths.