7 Days to Die Land Claim Block Settings: Size, Count, Expiry and Decay
Land claim blocks decide what a griefer can and can't do to a base. If your server is PvE, PvP or a mix, the LandClaim settings in serverconfig.xml are where you tune that.
The names and defaults here come from the community wiki's server page, which describes Alpha 20.6 (checked November 21, 2026). The game has changed since then. Our serverconfig guide covers V3.x, so treat these as a map and check the comments in your own file before relying on a number.
On this page
The settings
| Setting | Default | What it does |
|---|---|---|
LandClaimCount | 1 | Maximum land claims per player |
LandClaimSize | 41 | Size of the protected area per claim block, in blocks. Must be an odd number. |
LandClaimDeadZone | 30 | Minimum distance between claim blocks, unless the players are friends |
LandClaimExpiryTime | 7 | Days a player can be offline before their claims expire and lose protection |
LandClaimDecayMode | 0 | How offline claims fade: 0 slow (linear), 1 fast (exponential), 2 none (full protection until expiry) |
LandClaimOnlineDurabilityModifier | 4 | Multiplier for how hard claimed blocks are to damage while the owner is online. 0 means no damage at all. |
LandClaimOfflineDurabilityModifier | 4 | The same, while the owner is offline. 0 means no damage at all. |
LandClaimOfflineDelay | 0 | Minutes after logout before the offline modifier takes over |
What the claim block does
The wiki's Land Claim Block page says the protected area is 41 by 41 by default and extends the full height of the map. It reaches 20 blocks out in each direction from the block. That page also says the size was raised to 41 in Alpha 16, and that the block can't be placed too close to another player's claim.
It also notes that only three claim blocks can be active at once, and that placing a fourth deactivates the oldest. It doesn't say whether that limit is configurable, and it reads differently from LandClaimCount on the server page, so don't assume the two are the same rule. Test it on your own version.
Tuning for the way you play
- Friendly PvE server. Raise
LandClaimExpiryTimeif people take weeks-long breaks, and set decay mode to 2 so a base keeps full protection until it expires. - Hardcore raid server. Lower the offline durability modifier, or lower expiry. A modifier of 0 makes blocks undamageable, which is the opposite of raiding.
- Crowded server. Raise
LandClaimDeadZoneto spread bases out. - Quick-logout loopholes. The delay is 0 by default, so offline rules apply the moment the owner leaves. Set
LandClaimOfflineDelayabove 0 if you want a grace period.
Changing them on ChicagoServers
- Open the file
Go to the Configs tab and open
serverconfig.xml. - Edit the values
Find the LandClaim lines and change the number inside
value="". - Save and restart
Click Save, then Restart. Changes apply when the game starts.
If a setting you want isn't in your file, your version may name it differently or not support it. Don't add lines you can't find in the file's own comments.
Frequently asked questions
How big is a 7 Days to Die land claim?
The wiki's server page lists <code>LandClaimSize</code> with a default of 41 blocks, and it must be an odd number. The wiki's claim block page says the zone extends the full height of the map.
How long does a land claim last when the owner is offline?
The documented default is 7 days (<code>LandClaimExpiryTime</code>), after which the claims lose protection.
What does LandClaimDecayMode do?
It controls how offline claims fade: 0 is slow and linear, 1 is fast and exponential, 2 is none, so full protection lasts until expiry.
Can I make claimed blocks undamageable?
A durability modifier of 0 means no damage at all, according to the wiki's description. Use it with care, because it removes raiding.
Are these settings the same in the latest version?
Not necessarily. The names and defaults come from a page describing Alpha 20.6, so check the comments in your own serverconfig.xml.