Introduction

ExyliaProtections lets players protect land. A protection is a box of blocks with an owner, members, roles and flags, made by placing a core block or by selecting two corners. Everything an owner does with it — members, roles, flags, bans, the bank, plots, a public warp — is done from /protections, and most of it also from a command standing inside the land.

It is a premium plugin, sold through the Exylia store and installed through a licence loader. Protections used to be a module of ExyliaSurvivalCore; they are now this plugin, which reads the same data under new table names. See Migration.

What is included

Only the core of the plugin is on after a fresh install: protecting land, members, roles, flags, bans, lock, greetings, logs and border previews. Raids, the bank, upkeep, the market, rent, plots, upgrades, warps, perks, time and weather and merging each have a switch in submodules, all off. See Configuration.

Requirements

What each optional plugin adds is listed on Installation.

How a network sees protections

Every protection is one row in the database, and every server sharing that database keeps all of them in memory. A player's list and their limits count every server. Only the server a protection was made on enforces it, draws it and mirrors it to WorldGuard; the others list it and can teleport a member to it. With Redis configured, a change made on one server reaches the others at once.

How to read this documentation

Conventions

• Values marked as default are what the plugin writes the first time it starts. If the file already exists, your value is kept.
• Identifiers between < and > are variables. /protections warp <name> means /protections warp spawn, not /protections warp <spawn>.
• "The protection here" is the protection the player is standing in. Commands that act on land act on that one.
• Colours use ExyliaLib palette tokens ({primary}, {highlight}, {muted}), and & codes work too.