NoPvP - PvE Player Damage Blocker
NoPvP - PvE Player Damage Blocker A lightweight server-side PvP damage blocker for DayZ PvE servers. NoPvP is designed for community and private PvE servers that want reliable protection against player-versus-player damage while keeping normal survival gameplay intact. When a player attempts to damage another player, the damage is cancelled server-side before it is applied. The mod can also notify the attacker… (more)
NoPvP - PvE Player Damage Blocker A lightweight server-side PvP damage blocker for DayZ PvE servers. NoPvP is designed for community and private PvE servers that want reliable protection against player-versus-player damage while keeping normal survival gameplay intact. When a player attempts to damage another player, the damage is cancelled server-side before it is applied. The mod can also notify the attacker in-game and log blocked PvP attempts for server staff. Core Features Blocks direct player-versus-player damage Blocks supported indirect PvP damage from placed or thrown items Blocks supported grenade, explosive, landmine, claymore, and trap damage caused by another player Tracks ownership of dangerous placed/thrown items Persistent ownership storage for restart-safe explosive and item tracking Helps prevent players from shooting another player's carried grenades or explosives to cause PvP damage Optional protection from self-damage caused by your own grenades or explosives Keeps normal PvE damage working Supports DayZ Expansion AI and other AI/PvE enemies when they do not use real player identities Optional attacker notification when PvP damage is blocked Optional server-side logging of blocked PvP attempts JSON configuration generated automatically Admin/API methods for integration with admin tools or custom server mods Signed PBO included for server signature verification PvE Damage Still Works NoPvP is built to block player-caused PvP damage, not normal survival damage. Zombies Animals AI enemies Weather Environmental hazards such as sandstorms and extreme heat Hunger Thirst Sickness Fall damage Other normal PvE damage sources Supported Maps NoPvP is map-agnostic. It hooks DayZ's server-side damage pipeline instead of map-specific content, so it works the same way on every terrain. Chernarus Livonia Sakhal (Frostline DLC) Nasdara (Badlands DLC, game update 1.30) Community and custom maps using the standard DayZ damage system Generated Server Files $profile:NoPvP\NoPvPConfig.json $profile:NoPvP\NoPvPOwnership.json Important Config Options enablePvPBlock = 1 blockIndirectPlayerDamage = 1 persistIndirectDamageOwnership = 1 protectCarriedExplosivesFromPvP = 1 protectPlayersFromOwnExplosives = 1 notifyAttacker = 1 logBlockedAttempts = 1 Installation Subscribe to the mod. Add the mod to your server launch parameters or host panel mod list. Make sure the included .bikey is present in your server keys folder. Start the server once to generate the config files. Adjust the JSON settings if needed. Restart the server after making config changes. Example Launch Parameter -mod=@NoPvP Recommended Server Settings verifySignatures = 2 BattlEye = enabled Server owners should also use active moderation and regular log review. Compatibility Notes NoPvP blocks supported player damage through DayZ's server-side damage calculation flow. Grenade launchers, custom explosives, AI mods, and third-party weapon mods depend on how those mods report damage to DayZ. If DayZ exposes the attacker, projectile, explosive item, or tracked owner through the normal damage event, NoPvP can block it. If another mod creates completely unattributed damage, no server-side script can always determine who caused it. Important Disclaimer No mod can guarantee complete protection against every possible cheat, exploit, engine edge case, or third-party mod conflict. NoPvP is intended to provide simple, configurable, server-side protection against player killing for Pv
Not analyzed yet
modperf has not read this mod's scripts, so there is no report and it is left out of any stack it appears in. 13 live servers in the crawl publish it.
The worker downloads the mod from the Workshop and reads its Enforce Script — nothing is executed. Usually a few minutes. This page then shows the report.