Skip to content

Integrations

DEVKruidenier edited this page Nov 7, 2026 · 22 revisions

Integrations

All integrations are optional. LandWard works normally when none are installed.

Vanilla spawn protection and EssentialsX

Download: EssentialsX, including its optional AntiBuild module.

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: true

EssentialsX AntiBuild and Protect are soft dependencies. They apply their global build and interaction rules alongside LandWard; use WorldGuard for a shaped spawn region.

Economy: Vault

Download: Vault and an economy provider such as EssentialsX. LandWard uses Vault only when claim payments are configured as money; it keeps working when Vault or an economy provider is absent.

WorldGuard

Download: WorldGuard. WorldGuard requires WorldEdit.

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: true

BlueMap, Squaremap and Pl3xMap

Downloads: BlueMap, squaremap, and Pl3xMap.

When 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: true

Each 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.

Actual BlueMap claim overlay: chunk boundaries follow exact 16×16 chunks.

Plan

Download: Plan.

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: owned land with claimed chunks, and lands where the player is a member.
  • Per server: Player lands, Claimed chunks, Safe Zones, Safe Zone chunks, Unique land owners and Land memberships.

LandWard publishes a wide overview table, so Plan exposes LandWard as a clickable item in the left sidebar. The page contains the complete claim and Safe Zone statistics; no Plan files are modified.

Plan is optional. If Plan is not installed, LandWard simply starts without these statistics.

PlaceholderAPI

Download: PlaceholderAPI.

When PlaceholderAPI is installed, LandWard registers these placeholders:

Placeholder Returns
%landward_land_name% The player's owned land name, or none.
%landward_is_owner% true when the player owns a land; otherwise false.
%landward_owned_chunks% Number of chunks in the player's owned land, or 0.
%landward_member_lands% Number of other lands the player belongs to.
%landward_current_claim% Name of the land in the player's current chunk, or none.
%landward_current_owner% Owner name of the current claimed chunk, or none.
%landward_current_chunk_claimed% true when the player's current chunk is claimed; otherwise false.

LandWard registers this expansion automatically. You do not download it from eCloud.

Combat taggers

LandWard always has its own short-lived PvP-hit tracker, so combat protection works even when no combat plugin is installed. When PlaceholderAPI and a supported combat tagger are present, LandWard also checks the configured external placeholders. The default mappings are:

Combat tagger Placeholder Tagged value
CombatLogX %combatlogx_in_combat% true
DeluxeCombat %deluxecombat_in_combat% true
PvPManager %pvpmanager_combat_timeleft% a number greater than 0
EternalCombat %eternalcombat_opponent% a non-empty opponent name

With the following settings, tagged players can continue fighting each other inside a normal claim until their tag expires. Tagged players also cannot unclaim land. If an external placeholder is unavailable, LandWard treats the player as not tagged so a missing expansion never blocks a command.

integrations:
  combat-tag:
    enabled: true
    claim-pvp-bypass: true
    block-claim-abandon: true

Next: Configuration · Visual Guide

Clone this wiki locally