Combat and activity records
Legion turns DayZ server logs into Discord posts for combat, deaths, player movement into the server and unconscious events, then lets owners decide which channels show exact locations, nearby areas or no location links.
PVP kill posts show who killed who, the weapon, distance, time, location output and the linked player context Legion can safely display. These records also feed player stats, leaderboards, streaks, headshots and longest-kill tracking.
Owners can keep Killfeed public with reduced location detail, or route it privately with full location output. The same kill record can be useful as a public brag post, a staff audit trail and a stats update.
Hit Feed catches damage lines before they become kills. Staff can see who hit who, weapon or damage source where available, health change, distance and the logged position. It is useful for damage disputes, suspected third-partying and checking whether a fight started inside a protected area.
Because it is based on damage, Hit Feed can explain fights that never show in Killfeed: warning shots, uncon knockdowns, grenade damage, players trading hits and someone escaping before the final kill.
PVE Feed separates deaths not caused by another player: infected, animals, explosions, landmines, suicide, fall damage and other server-side death causes. PVE servers use it for rule enforcement, while PVP servers use it to explain deaths that did not belong in the killfeed.
It also stops PVE deaths from polluting PVP stats. A player dying to infected, mines, animals or their own mistake should be visible, but it should not look like another player earned a kill.
Connect Feed records players joining, disconnecting and reconnecting. Owners use it to see who came back after combat, who is repeatedly reconnecting and whether a player was online around the time of a report.
Reconnect posts are especially useful around raids, combat-log complaints and whitelist checks because they show timing without staff needing to download and search the full log first.
Unconscious Feed posts knockouts separately from full deaths. It gives staff a cleaner view of non-lethal fight outcomes, rubber-bullet style events, risky base raids and players being knocked out before a later kill or revive.
It also feeds knockout/uncon stats, so a player who downs people without finishing kills still leaves a combat trail.
Legion watches the server log files that Nitrado stores for the DayZ server. When a new line appears for a kill, hit, death, connect or unconscious event, Legion reads the useful parts of the line, matches the player records it already knows, formats the result and posts it to the assigned Discord channel.
Owners are not expected to read raw log syntax. The bot turns the log into a post with player names, time, item or weapon detail, distance when available, location output and links only when the location setting allows it.
The feed type is decided by the line itself. A player killing another player becomes Killfeed. Damage before a kill becomes Hit Feed. A non-player death becomes PVE Feed. A join, leave or reconnect becomes Connect Feed. A knockout or unconscious state becomes Unconscious Feed. That split is why owners can make public combat channels, private staff channels and stats updates without mixing every event into one unreadable stream.
Legion does more than print the final death line. It keeps nearby hit and death context together so the feed can explain the fight: weapon, distance, hit count, damaged body part, health/damage context where the log exposes it, assist candidates and the death category that should be posted.
| Tracked data | What Legion adds | Owner control |
|---|---|---|
| Landmine Kill | Trap deaths are treated as their own readable event, so staff and players can see mine deaths without pretending they were normal gun kills. | Killfeed/PVE channel assignment and location settings decide where it posts and how much position data is shown. |
| Fall Kill and Forced Suicide Kill | Environmental/self-inflicted/admin-forced death styles are kept separate from normal PVP, protecting KD, bounties and player stats from bad attribution. | PVE, moderation and staff-feed routing decide whether the result is public, staff-only or location-redacted. |
| Assists | Recent damage context can be used around the final kill so a player who helped damage the victim is not invisible just because they did not land the last blow. | Stats, leaderboard and public feed choices decide whether assists are visible gameplay credit or staff-side evidence. |
| Damaged parts and weapons | Hit Feed can preserve weapon, distance, body part or hit-area context and damage/health context where the logs provide it. | Hit Feed channel assignment and location privacy decide who sees the fight detail. |
| Setting | Controls | Use |
|---|---|---|
/settings channel assign |
Killfeed, PVE Feed, Hit Feed, Connections and Uncon Feed channel destinations. | Separates public kill posts from staff-only damage, PVE death, connection and knockout records. |
/settings configure locations |
killfeed, pve, hit,
connect and uncons location output.
|
Choose full map links for staff, near-only wording for safer public posts, no links for rule-sensitive channels or no location output at all. |
/settings configure logo and
/settings configure color
|
Server embed image and embed colour. | Keeps combat posts branded to the selected server instead of looking like generic bot output. |
/settings channel create |
Automatic channel creation for selected feed types. | Builds the Discord layout before feeds are assigned. |
Kill, hit, PVE, connect and unconscious output turns log activity into Discord posts staff and players can understand quickly.
Public feeds can stay clean while staff feeds keep the context needed for disputes, location checks and evidence review.
The same records can support stats, ranks, moderation, heatmaps, bounties and rule enforcement.
