How to Make a 7 Days to Die PvP Server (V3 Settings Guide)

Make a 7 Days to Die PvP server: PlayerKillingMode, land claims and offline raid settings in serverconfig.xml, plus what moved to the SandboxCode in V3.

Updated Oct 3, 2026 · 6 min read

On this page

To make a 7 Days to Die PvP server, set PlayerKillingMode in serverconfig.xml to 3 (kill everyone, the default) or 2 (kill strangers only), then tune the land claim lines that decide how hard bases are to raid: LandClaimCount, LandClaimSize, LandClaimOnlineDurabilityModifier and LandClaimOfflineDurabilityModifier. Since V3.0, drop on death and player block damage are in the SandboxCode, not the XML. All of these apply to an existing save after a restart.

What you can change on an existing world vs what needs a new one

Change Existing save? Where
Who can kill whom (PlayerKillingMode) Yes, after a restart serverconfig.xml
Land claim count, size, durability, expiry Yes, after a restart serverconfig.xml
Bedroll protection Yes, after a restart serverconfig.xml
Drop on death, block damage, loot, blood moons Yes, after a restart SandboxCode (V3)
World size, seed or map No, needs a new world serverconfig.xml

7 Days to Die survivor firing a flaming weapon at a zombie in a snowy fire lookout camp

Step 1: Back up and stop the server

Back up the save folder (Saves/<world>/<GameName>/) and serverconfig.xml. Then stop the server with shutdown from the console or the panel, so it saves cleanly.

Step 2: Choose the player killing mode

<property name="PlayerKillingMode" value="3"/>
Value Mode Who can hurt whom
0 No Killing Nobody, a PvE server
1 Kill Allies Only Only players you are allied with, for friendly duels
2 Kill Strangers Only Anyone except your allies, the common PvP choice for groups
3 Kill Everyone Everyone, including allies (default)

"Allies" are the players you have added as friends in the game. Mode 2 is the usual choice for team based PvP, because friendly fire inside a group is off while everyone else is fair game.

Step 3: Set land claim protection

Land claim blocks protect an area from other players. These lines decide how hard raiding is:

<property name="LandClaimCount" value="3"/>
<property name="LandClaimSize" value="41"/>
<property name="LandClaimDeadZone" value="30"/>
<property name="LandClaimExpiryTime" value="7"/>
<property name="LandClaimDecayMode" value="0"/>
<property name="LandClaimOnlineDurabilityModifier" value="4"/>
<property name="LandClaimOfflineDurabilityModifier" value="4"/>
<property name="LandClaimOfflineDelay" value="0"/>
Key What it does PvP advice
LandClaimCount Land claims each player may place 1 to 3. More claims mean bigger fortresses
LandClaimSize Size of the protected area, in blocks (41 is common) 41
LandClaimDeadZone Minimum distance between claims of players who are not friends 30 or more, stops players claiming right next to an enemy
LandClaimExpiryTime Days a player can be offline before their claims stop protecting 3 to 7
LandClaimDecayMode How offline protection fades: 0 linear, 1 exponential, 2 full protection until expiry 0
LandClaimOnlineDurabilityModifier How much harder blocks in a claim are while the owner is online. 0 means indestructible 4 for raiding, or 2 for easier raids
LandClaimOfflineDurabilityModifier The same while the owner is offline. 0 means indestructible 0 to stop offline raiding entirely
LandClaimOfflineDelay Minutes after logging off before offline protection starts 5 to 10, so nobody logs off mid raid to save their base

The most important decision on a PvP server is offline raiding. Setting LandClaimOfflineDurabilityModifier to 0 makes claimed bases indestructible while the owner is offline, so raids only happen when the defenders can fight back. Leave it at a number like 4 if you want full raiding at any hour.

Step 4: Bedroll and spawn rules

<property name="BedrollDeadZoneSize" value="15"/>
<property name="BedrollExpiryTime" value="45"/>

Bedrolls are spawn points. On a PvP server, players camping a bedroll to kill someone as they spawn is a common complaint, which is a rules question more than a setting. The deadzone only stops zombies spawning near it.

Step 5: Drop on death and block damage (the SandboxCode)

This is the gotcha that catches people with old configs. In V3.0, The Fun Pimps moved about 30 gameplay properties out of serverconfig.xml into the single SandboxCode. For PvP the important ones are:

  • DropOnDeath: what a killed player drops (everything, toolbelt, backpack or nothing)
  • BlockDamagePlayer: how much damage players do to blocks, the main raiding speed setting
  • AirDropMarker: whether air drops show on the map, which decides how contested they are

If your serverconfig.xml still has <property name="DropOnDeath" .../> or BlockDamagePlayer, those lines are ignored without any error. The server quietly uses whatever the SandboxCode says, or Adventurer defaults when there is no code. To change them, open Sandbox Options on the new game screen in 7 Days to Die, set the values, copy the generated code and paste it as the SandboxCode value (or the Sandbox code setting in our panel). The 7 Days to Die wiki's V3 SandboxCode guide lists every moved property. More detail is in how to change 7 Days to Die server settings.

Step 6: Start the server and test

Start the server and check the console for errors in serverconfig.xml. A broken XML line (a missing quote or slash) can stop the server loading the file. Then test with a friend who is not on your friends list: you should be able to hurt each other in modes 2 and 3.

Common problems

  • Players cannot hurt each other: PlayerKillingMode is 0, or it is 2 and you are friends. Check the mode, and test with someone who is not an ally.
  • Drop on death or block damage did not change: you edited the old XML line, which V3 ignores. Change it in the SandboxCode.
  • Bases cannot be raided at all: LandClaimOnlineDurabilityModifier or LandClaimOfflineDurabilityModifier is 0, which makes claimed blocks indestructible.
  • Bases raided overnight: offline protection is low. Set LandClaimOfflineDurabilityModifier to 0 or a high number.
  • Settings reset after restart: the server was running when you edited, or the panel passes that value on the launch line. Stop, edit, start.

Running a PvP server on GamezServers

On a 7 Days to Die server from GamezServers you edit serverconfig.xml in the file manager, after a one click Backup. The server name, description, password, player count, world, seed, size, save name and Easy Anti-Cheat are panel settings passed on the launch line, so change those in the panel. The killing mode and land claim lines in the XML are yours. Paste your SandboxCode into the Sandbox code setting. The Crossplay server type lets PC, PlayStation and Xbox players fight together, up to 8 players and without mods. For more admin tools, see 7 Days to Die admin commands.

FAQ

How do I turn on PvP in 7 Days to Die?

PvP is on by default with PlayerKillingMode set to 3. Set it to 2 to protect your friends, or 0 to turn PvP off.

What does Kill Strangers Only mean in 7 Days to Die?

You can hurt anyone except players on your friends list. It is the common setting for team PvP.

How do I stop offline raiding in 7 Days to Die?

Set LandClaimOfflineDurabilityModifier to 0 in serverconfig.xml, so blocks in a land claim cannot be damaged while the owner is offline.

Why does DropOnDeath in serverconfig.xml not work anymore?

Since V3.0 it is part of the SandboxCode. Old XML lines for it are ignored, so set it in Sandbox Options and paste the new code.

Skip the setup. Your own 7DTD server.

$9.99USD first month

Then $19.99/mo. Just trying it? $5.00 for 3 days

Keep reading