Non-allied / not partied players can damage other players' land claims.
Does anyone know of a fix or a setting I can change for this, or if this is a known glitch?
The replies you received are correct for normal land-claim damage behavior, but that is not the same issue we are investigating.
In 7 Days to Die, an LCB does not automatically make a base immune to damage. If the online/offline durability modifiers are finite, non-allied players can still damage claimed blocks. Setting LCB durability extremely high or infinite is how servers prevent block damage inside claims.
Our issue is different.
We are seeing cases where the claim state itself becomes inconsistent between players. Example symptoms:
- One player sees/hears land-claim protection, another player in the same area does not.
- A player can place blocks where another player is blocked.
- A player may see an ally’s claim as enemy-owned/red.
- The original owner can be blocked from building even though their own LCB is present.
- A new LCB can sometimes be placed while old claim protection still appears active.
That is not just “LCB damage is allowed.” That points to a per-player claim-state/ownership desync or stale claim record.
So to separate the two issues:
1. Non-allied players damaging claimed blocks = intended unless claim durability is set high/infinite.
2. Non-allied players placing/building inside another player’s active claim, or different players getting different claim states in the same location = possible bug/desync.
We already verified our LCB settings are loading correctly at runtime:
- LandClaimCount
- LandClaimSize
- LandClaimDeadZone
- LandClaimExpiryTime
- LandClaimDecayMode
- Online/Offline durability modifiers
So the remaining issue is not a simple serverconfig mismatch. It appears to be claim ownership/state desync, possibly save-state or V3.0 claim replication related.
