Feature hub

Legion Killfeed Features

Legion Killfeed is a DayZ Discord bot for console servers that turns Nitrado logs, server state, player records and owner settings into usable Discord workflows for staff and players.

Start with setup, then route the feature output.

Most Legion features rely on the same foundation: a connected Nitrado server, a linked Discord guild, assigned output channels and sensible location settings. Once that is in place, each feature can post its own records instead of pushing every record into one channel.

The grouped pages below are split by how owners actually use the bot: combat feeds for fights, placement feeds for base activity, player records for progression, maps for location visibility, moderation for evidence/enforcement, economy for linked-player money, tickets for private support and server tools for Nitrado/file work.

That is the point of using the bot instead of scattered helper tools: combat records, moderation evidence, status checks, economy actions and player-facing commands can all use the same server identity, channel routing and permission model.

What owners get from the full bot

Readable server evidence

Killfeed, PVE, hit, build, flag, connect and moderation output turn log activity into Discord records that staff can review without digging through raw files first.

Player systems that connect

Linked player identity lets stats, leaderboards, banking, bounties, tickets, Shoppi and staff lookups refer to the same Discord user and DayZ gamertag history.

Less manual Nitrado work

Setup, server status, restarts, file helpers, object output and generated signs reduce the repeated server-admin work that usually sits outside Discord.

Combat and activity

Killfeed, Hit Feed, PVE Feed, Connect Feed and Unconscious Feed turn combat, damage, death and connection logs into readable Discord posts, with per-feed location controls so public channels and staff channels do not need to show the same amount of detail.

Building, flags and movement

Build Feed covers placements, dismantles, pack/fold actions and base work. Glitch Feed can isolate watched item categories. Flag Feed and Teleport Feed keep territory and generated movement records separate from ordinary construction history.

Setup order that prevents broken feeds

  1. Add the Nitrado token. Legion needs the service connection before it can read logs, fetch status or work with files.
  2. Assign Discord and create channels. Feeds can parse correctly and still look missing when no destination channel is assigned.
  3. Configure location output. Staff channels can keep exact location detail while public channels can use near/no-link output.
  4. Separate noisy records. Put hits, PVE deaths, build records, glitch items, flags and moderation logs into channels staff can actually monitor.
  5. Turn on player-facing systems. Player stats, economy, bounties, tickets, Shoppi and maps work best after the backend routing is correct.

Feature dependencies owners should not ignore

Channel assignment controls visibility

A feature can be working internally while nothing appears publicly because the channel was never assigned.

Location settings control safety

Exact coordinates belong in staff channels on many servers; public feeds can use near/no-link output.

Player Linking improves everything

Stats, leaderboards, economy, bounties, Shoppi and player lookups are cleaner when Discord users are linked to gamertags.

Site search

Find pages, tools, and guides

Copyright