DayZ Killfeed
Live events from your DayZ server directly in Discord
The DayZ Killfeed module connects TeraOne to your Nitrado DayZ server (PC, PS4/5, or Xbox). Kills, deaths, connects, disconnects, and other player events appear automatically as Embeds in a Discord channel. All event types are filterable — you decide what gets shown.
Requirements
- A Nitrado DayZ server (PC, PlayStation, or Xbox)
- A Nitrado account with access to the developer portal
- Correct Nitrado log settings (see step 2)
Step-by-step setup
Step 1: create a Long-Life Access Token (LLAT)
Open the Nitrado developer portal at https://server.nitrado.net/deu/developer/index and create a new LLAT. Choose a descriptive name (e.g. "TeraOne-Bot") and set the expiry to the maximum (2 years recommended). Copy the token immediately — it is only shown once.
Step 2: check Nitrado log settings
In the Nitrado game server panel under Settings → General, the following options must be set correctly:
- Set "Log-Ausgabe reduzieren" to OFF (this is Nitrado's "Reduce log output" toggle — very important!)
- "Admin Log" → ON
- "Server Log" → ON
- "Gebäude-Log" (building log) → ON
- "Platzierungs-Log" (placement log) → ON
- "Spielerliste-Log" (player list log) → ON
Step 3: add the token in the TeraOne dashboard
Open Dashboard → DayZ Killfeed → "Tokens" tab. Click "Add token", enter a label, and paste the LLAT. Save.
Step 4: add a server
Open the "Servers" tab. Click "Add server". Select your token from the dropdown — the Nitrado service list loads automatically. Select the game server, assign a slug (URL-friendly short name, 2–32 characters, lowercase letters and hyphens only), and a display name.
Step 5: configure the kill channel and events
Select a Discord channel for the Killfeed. Enable the desired event types (default: all except connect/disconnect/unknown).
Event types
| Type | Default | When triggered |
|---|---|---|
pvp | ON | Player kills player |
pve | ON | Animal or environment kills player |
bleed | ON | Death by bleeding |
fall | ON | Fall damage death |
suicide | ON | Self-inflicted death |
vehicle | ON | Vehicle accident |
explosion | ON | Explosion damage |
hypothermia | ON | Death by cold |
hunger | ON | Death by starvation |
thirst | ON | Death by dehydration |
connect | OFF | Player connects |
disconnect | OFF | Player disconnects |
unknown | OFF | Unrecognised event type |
Separate channels per event type
You can configure a separate Discord channel for each event type. Useful for routing connects and disconnects to a dedicated #connect-log without cluttering the kill channel. Without an override, all events go to the configured kill channel.
Adaptive polling interval
TeraOne queries the Nitrado API adaptively based on recent activity on the server:
| Server status | Poll interval |
|---|---|
| Hot (last event < 5 min) | ~30 seconds |
| Warm (< 15 min) | ~60 seconds |
| Cool (< 60 min) | ~3 minutes |
| Cold (>= 60 min or never) | ~10 minutes |
Intervals include a ±5 second jitter so that multiple servers on the same token do not poll simultaneously.
Rate limits
The Nitrado API allows approximately 30 requests per minute per token. TeraOne is capped at 25 requests/minute to leave a buffer for other Nitrado applications.
Public Leaderboard
When enabled, the kill Leaderboard is publicly accessible at the following URL:
tera-one.de/:locale/dz/:guildId/:slugExample: tera-one.de/en/dz/123456789/my-server
Troubleshooting
- No events in the Killfeed
- Check step 2: are all log settings correct on Nitrado? In particular: "Log-Ausgabe reduzieren" (Reduce log output) must be OFF. Change the setting and restart the server.
- "Token expired" or "Unauthorized" error
- Create a new LLAT in the Nitrado developer portal. Enter it in Dashboard → Tokens → edit token. The old token is invalid immediately.
- Events arrive very late (10+ minute delay)
- The server is in cold-poll mode (no activity in the last hour). As soon as new events arrive, TeraOne automatically switches to hot mode (~30 s interval).
- Server migration (new Nitrado service ID after moving)
- Delete the old server in the dashboard and create a new one with the new service ID. The slug can remain the same.
- Killfeed posts to the wrong channel
- Check channel overrides: if you have configured channels per event type, the override takes precedence over the default kill channel.
Frequently asked questions
- Does the module work for PS4/5 and Xbox DayZ servers on Nitrado?
- Yes, Nitrado provides the same API for all platforms. The setup process is identical.
- Can I manage multiple Nitrado servers with one token?
- Yes, one LLAT has access to all game servers in your Nitrado account. In the dashboard you can register multiple servers under the same token.
- Is there a limit to how many DayZ servers I can manage per Discord server?
- Maximum 10 servers per Discord server.
- Are kills captured that happened while TeraOne was briefly offline?
- No. TeraOne reads the current logs on each poll — already-processed logs are not reported again, but events from an offline period are skipped.