Repository navigation
Integrations
All integrations are optional. LandWard works normally when none are installed.
LandWard can reserve the primary world's built-in server.properties
spawn-protection square, even when no protection plugin is installed. It can
be disabled here:
integrations:
vanilla-spawn-protection:
enabled: trueEssentialsX AntiBuild and Protect are soft dependencies. They apply their global build and interaction rules alongside LandWard; use WorldGuard for a shaped spawn region.
When WorldGuard is installed, LandWard refuses a claim that overlaps a protected WorldGuard region. This includes typical spawn regions.
integrations:
worldguard:
enabled: true
deny-any-overlap: trueWhen BlueMap, Squaremap or Pl3xMap is installed, LandWard publishes claims in a dedicated, toggleable marker layer. The layer refreshes after a chunk is claimed, unclaimed or renamed.
integrations:
bluemap:
enabled: true
squaremap:
enabled: true
pl3xmap:
enabled: trueEach map remains optional; LandWard never opens a web port. If you run more than one map plugin, assign a separate web port in each map plugin's own configuration. BlueMap may additionally require the server owner to accept its Mojang-resource download before it can render maps.

When Plan is installed and this setting is enabled, LandWard adds read-only claim statistics to the Plan web panel.
integrations:
plan:
enabled: true- Per player: owns a land, owned chunks, and member lands.
- Per server: number of lands and claimed chunks.
No additional LandWard database table is created for this integration. Plan is a soft dependency, so LandWard starts normally without it.
When PlaceholderAPI is installed, LandWard registers %landward_...% placeholders:
land_name, is_owner, owned_chunks, member_lands, current_claim,
current_owner and current_chunk_claimed.
LandWard registers its internal expansion automatically when PlaceholderAPI is installed. You do not download it from eCloud; eCloud is for independently distributed expansions.
LandWard has its own short-lived PvP-hit tracker, so the claim-combat safeguard works even when no combat plugin is installed. It can also read configured PlaceholderAPI values from CombatLogX, DeluxeCombat, PvPManager and EternalCombat when their matching PlaceholderAPI expansion is available.
With the following settings, two tagged combatants may continue their PvP encounter inside normal claims until their tag expires, while tagged players cannot unclaim land. An unresolved external placeholder is treated as not tagged, so a missing expansion cannot lock players out of a command.
integrations:
combat-tag:
enabled: true
claim-pvp-bypass: true
block-claim-abandon: trueNext: Configuration · Visual Guide