Skip to content

Protection and Warps

DEVKruidenier edited this page Nov 17, 2026 · 4 revisions

Protection settings and named warps

These features are available from LandWard 1.0.3.0.

Environment settings

Open your land settings, then Environment and damage. Warps have their own button directly in the land's main menu. Administrators can open these settings for a selected player land or for the Safe Zone in /claimadmin. The owner or an authorized administrator may change them. Member access remains in the separate Access and members menu, with its existing nine controls.

Every environmental rule belongs to the whole land. Player damage settings apply equally to owners, members and visitors; they are not individual member rights.

Rule New player lands New Safe Zones
Fire spread, ignition and burning blocks Denied Denied
Player fall damage Allowed Denied
TNT block damage, including TNT minecarts Denied Denied
Other explosion block damage Denied Denied
Explosion damage to players Allowed Denied
Fire damage to players Allowed Denied
Lava damage to players Allowed Denied
Mob changes to blocks Denied Denied
Water flow within the land Allowed Allowed
Lava flow within the land Allowed Allowed

Other explosions include creepers, ghasts, withers and block explosions such as beds/respawn anchors. Block damage and player damage have independent switches. The player-damage switch does not grant permission to damage animals or entities. Fire protection includes lava/lightning ignition, ongoing spread and burning, including burn events where the original ignition block is unknown.

Water/lava crossing between different lands or between claims and wilderness remains blocked in both directions, even when internal flow is allowed. Piston and hopper protection remain separate. The mob block-change switch does not grant non-mob entity placement rights; existing falling-block protection is retained. Normal crop growth is not controlled by this switch. LandWard never overrides world gamerules, WorldGuard or an event already cancelled by another plugin. Disabled worlds have no LandWard gameplay protection.

Existing claims and configuration

On upgrade, fire spread/burning is intentionally denied to protect existing buildings. Existing explosion/block protection and survival damage behavior are retained. This means an existing Safe Zone retains its previous player damage behavior; change it in its Environment menu if damage should be disabled.

player-claims.environment and admin-claims.environment define defaults for new lands only. In those sections, true allows the named effect and false denies it. Per-land choices are stored in the database and survive reloads, restarts and owner transfers. New config/language keys are merged without overwriting custom values.

Named player-land warps

Owners use Warps in their land's main menu to create a destination at their precise current position, including world, coordinates and facing direction. The position must be inside a chunk of that land. Enter the name in the native anvil field and confirm the output item. Names contain 1–24 letters, numbers, spaces, underscores or hyphens; surrounding whitespace is trimmed and duplicate names are rejected without regard to case. Rename and delete actions are in the selected warp's menu; deletion requires confirmation.

Owners and current members may travel to that land's warps. Members access them from the Member lands overview. Visitors cannot use them. Administrators with landward.admin can access the selected land's warp list through /claimadmin. Administrators may travel there but do not manage an owner's named destinations. Safe Zones have environmental settings but do not have player-land warps.

Limits

teleportation.warps.base-limit defaults to 3. If a player has one or more positive numeric permission nodes such as landward.warps.5 and landward.warps.10, the highest numeric node wins. The base limit is used only when no numeric node is present. A limit of 0 prevents creation. Explicit landward.warps.unlimited grants unlimited warps; it is not granted to operators by default. Wildcard strings are not interpreted as numeric or unlimited nodes by LandWard.

Warps belong to the land, so owner transfers preserve them. When the new owner has a lower limit, existing warps stay usable, but additional creation is blocked until the count is below the applicable limit. Large lists have red previous-page and blue next-page panes.

Warmup and safety

teleportation.warp-delay-seconds and teleportation.admin-warp-delay-seconds both default to 2. Setting either to 0 removes that warmup. Administrators do not automatically skip it. Position movement cancels waiting; looking around does not. Actual damage, combat tagging, logout, loss of membership, a removed/changed warp, land deletion or a disabled/unavailable destination also stops the pending travel.

Access, world activation, destination ownership and safety are checked again when the teleport executes. LandWard requires an already loaded world. Previously generated destination chunks can be loaded without generating new terrain; unavailable or ungenerated chunks are rejected. The player needs solid support and clear standing space, using actual collision shapes so carpets, slabs and low indoor ceilings are checked at their precise height. Fire, lava, suffocation and other known hazards. Unsafe or unavailable targets fail with localized feedback; no fallback teleport is attempted. Existing land-owner teleport remains available separately.

Persistence and cleanup

SQLite and MySQL/MariaDB store precise warps and environmental overrides. Both live migration directions and version-4 backups include them. Older backups remain readable. Unclaiming a destination chunk removes its warps in the same database transaction; player/admin full land deletion removes all warps. Pending teleports revalidate these changes before execution. Main-thread synchronized creation and unclaim prevent a warp being created into a concurrently removed chunk within the same running LandWard instance.

Clone this wiki locally