PVE records

PVE Feed for DayZ Console Servers

Post non-player deaths and PVE context in their own feed instead of mixing survival deaths into the PVP kill record.

Separate from Killfeed

PVE Feed is for deaths that are not player-versus-player kills.

Infected, animals, falls, bleeding, traps, environment, vehicle context, and other non-player causes belong here when the logs identify them.

If a player kills another player on a PVE server, Killfeed records the kill and Autoban/Base Radars handle the rule enforcement.

PVE death post
PVE death records keep rule enforcement separate from normal PVP noise.

Separate PVE death records

PVE communities need clean records. Staff should be able to separate survival deaths from combat reports instead of forcing every death into one public killfeed channel.

It also helps mixed-rule servers explain what happened: PVE Feed for non-player deaths, Killfeed for player kills, Base Radars for zone exceptions, and Autoban for rule enforcement.

Owner commands

Assign the PVE Feed to the Discord channel where those death records belong. Use /settings configure locations with the pve option to decide how much map detail should be shown.

Use /settings autoban config only when the server should automatically enforce PVE Mode. Use /settings autoban whitelist for trusted accounts that should not trigger the whole-map rule.

Before turning on bans

  • Do not turn on automatic bans until your channels and location settings are correct. Test with staff first.
  • For a mixed PVE/PVP server, set the Base Radar zone rules before enabling whole-map Autoban.
PVE death embed

PVE deaths stay out of the PVP killfeed.

This is the actual job of the page: a non-player death record that staff can review separately from player-kill messages.

Unconscious feed example

Uncon and hit context can support review.

Unconscious and damage context can help staff understand a report, but the PVE Feed itself should stay focused on PVE death records rather than every combat detail.

Channel

/settings channel assign

Assign the PVE Feed to the channel where staff or players should see non-player death records.

Location display

/settings configure locations

Set the pve option based on how much location detail the server wants to expose in PVE death posts.

Enforcement

/settings autoban config

Use this only when the PVE rule should trigger automatic bans. Use Base Radars for PVP zones and other exceptions.

Location choices explained

/settings configure locations controls how much map information Legion shows in feed posts. Use it to balance player excitement against base privacy and rule enforcement.

  • On shows location information for that feed when Legion can calculate it.
  • Off hides location information for that feed.
  • Both is for owners who want both readable location text and the linked location style where supported.
  • Near gives players an approximate area instead of exposing the exact spot.
  • No Link keeps location text but removes the clickable map link.
  • Near No Link is the privacy-heavy option: approximate area text without the clickable map link.

For public player channels, Near or Near No Link hides exact positions. For staff-only channels, exact or linked locations give staff the coordinates needed for review.

Base Radar zone bans

Use /base radar create, not separate custom-zone pages.

Create a radar with coords, zone_owner, optional channel and role settings, and only the ban toggles that match the area rule. X,Z plus a radius creates a circular radar. X,Z;X,Z;X,Z creates a polygon radar when three or more coordinate pairs are provided.

Use /base radar edit to change the owner, channel, shape, role, location display, ping setting, and ban toggles later. Use /base radar whitelist for players who should be exempt from that specific zone's bans.

Base Radar ban toggles

Use these when a PVE server has marked PVP zones or protected areas with separate rules.

Toggle Turn it on for Leave it off for
ban_on_build Protected bases, no-build areas, staff-only structures. Normal bases where owners or faction members build inside the radar.
ban_on_kill No-kill areas, PVE protection zones, restricted event spaces. Allowed PVP zones. This is the key setting for PVE maps with marked PVP areas.
ban_on_death One-life style zones where the victim is banned after dying inside the radar. Normal PVE anti-kill rules where the killer should be handled with ban_on_kill.
ban_on_entry Restricted zones where entering is the offence. Faction bases, trader zones, or arenas where entry only needs an alert.
ban_on_logout Small restricted areas where logging out inside the zone breaks the rule. Large zones where normal disconnects would catch innocent players.
location Radar posts that should include location detail. Public channels where exact locations expose bases or hidden event areas.
base_ping Radar posts that should mention the assigned role. Quiet staff logs or high-volume zones where pings would spam Discord.

Commands and options

Copy the command name, then fill in the Discord options listed under it. Discord shows the option fields after the command is selected.

/settings configure locations
  • feature location options: choose how each supported feed shows coordinates.
  • Choices include On, Off, Both, Near, No Link, and Near No Link where supported.
/settings autoban config
  • mode: choose Kill, Death, or Off. Kill bans the killer for PVE anti-kill rules. Death bans the player who died for one-life style rules. Off leaves the map-wide autoban rule disabled.
/settings autoban whitelist
  • setting: Add, Remove, or View.
  • gamertag: optional unless adding or removing players; use commas for more than one gamertag.
/settings channel assign
  • channel: choose the Discord channel that should receive the feature posts.
  • feature/feed choice: choose the Legion feed or output type being assigned.
/base radar create
  • coords: X,Z for a circle, or X,Z;X,Z;X,Z for a polygon.
  • radius: used for a circle radar.
  • zone_owner: owner name shown for the radar.
  • zone_channel: optional Discord channel for alerts.
  • zone_role: optional role to ping.
  • location: Exact, Near, No Link, Near No Link, or Off depending on how much location detail should show.
  • ban_on_build, ban_on_kill, ban_on_death, ban_on_entry, ban_on_logout, ban_on_disconnect: turn on only the bans that match that area rule.
  • base_ping: controls whether the configured role/channel is pinged.
/base radar edit
  • Select the existing radar, then change owner, channel, shape, role, location display, pings, or ban toggles.
/base radar whitelist
  • setting: Add, Remove, or View.
  • gamertag: player name or comma-separated player names for that radar exception list.

Related features

Autoban Base Radars Hit Feed Killfeed Moderation

Site search

Find pages, tools, and guides

Copyright

© 2022-2025 Legion Killfeed. All Rights Reserved.

This website and its content, including but not limited to text, graphics, images, logos, icons, and software, are the property of Legion Killfeed and are protected by Australian and international copyright laws.

Rights Reserved: No part of this website may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the copyright owner, except in the case of brief quotations embodied in legitimate critical reviews and certain other non-commercial uses permitted by copyright law.

Disclaimer: All trademarks, logos, and service marks displayed on this site are the property of their respective owners. Use of these marks does not imply any affiliation with or endorsement by them.

Australian Copyright Law: This copyright notice is governed by the laws of Australia. Unauthorized use of this material is strictly prohibited and may result in civil and criminal penalties.

Legal & Privacy