Repository navigation
Home
LederProtections is a protection-stone plugin for Minecraft 1.21.x and 26.x. It uses WorldGuard and WorldEdit for regions and adds GUI management, role-based rules, economy, upgrades, safe teleports, public warps, holograms, diagnostics and anti-exploit checks.
| Component | Version |
|---|---|
| LederProtections | 1.5.0 |
| Public API contract | 1.0 |
| Public Maven artifact | com.alexisleder:lederprotections-api:1.0.0 |
Minecraft 1.21.x uses Java 21. Minecraft 26.1 and newer uses Java 25. Spigot and compatible Paper-based forks are supported when the server, WorldEdit and WorldGuard all support the selected Minecraft version. Paper is recommended when a stable build exists. Folia is not currently supported.
Version 1.5.0 adds customizable menus, /p home, clickable rule inspection,
configuration cleanup and immediate entry/exit notices. No resource pack is bundled.
Read Release 1.5.0, GUI Themes, External Resource Packs and Configuration Files.
Check the download page for artifact availability; documentation publication does not
by itself publish the JAR to Modrinth. See Compatibility for the verification scope.
- Configurable protection stones backed by WorldGuard.
- Personal
/pGUI and global/lep adminbrowser. - Owner, co-owner, member, visitor and blocked roles.
- Fine-grained rules for building, containers, doors, entities, PvP and more.
- Vault shop, upgrades and teleport costs when an economy is installed.
-
/warpspublic protection directory with categories, search and favorites. - Native Bukkit
TextDisplayholograms with global and per-protection controls. - Internal persistent PlaceholderAPI expansion with complete player, region, public-directory and hologram metadata.
- Versioned public Java API for integrations such as sell wands and addons.
- Refined GUI icons, optional category skin heads and cleaner protection holograms.
- bStats charts for aggregated adoption and compatibility metrics (plugin ID
34348). - Migration, export/import, diagnostics, repairs, audit logs and safe backups.
| Dependency | Required | Purpose |
|---|---|---|
| Java 21 or 25 | Yes | Java 21 for Minecraft 1.21.x; Java 25 for Minecraft 26.1+. |
| WorldEdit | Yes | WorldGuard dependency and region operations. |
| WorldGuard | Yes | Protection-region backend. |
| Vault + economy plugin | No | Shop, upgrade and teleport costs. |
| PlaceholderAPI | No |
%lederprotections_*% placeholders. |
- Read Installation and Dependencies.
- Configure Protection Stones and Permissions.
- Review Configuration and Rules System.
- Start the server, then run
/lep versionand/lep check. - Test a protection on a staging server before updating production.
| Command | Purpose |
|---|---|
/p |
Personal protection menu. |
/p home <name or ID> |
Teleport to an owned/shared protection. |
/warps |
Public protection directory. |
/p shop |
Protection-stone shop. |
/p border |
Border preview. |
/lep admin |
Server-wide admin browser. |
/lep hooks |
Optional integration status. |
/lep check |
Data and region diagnostics. |
/lep reload |
Reload configuration, registries and optional hooks. |
See Commands for migration, repair, export and import commands.
External plugins should use Public API, not private implementation classes.
The API exposes immutable snapshots, access roles, safe-location searches,
lifecycle events, command extensions and silent action checks such as
canOpenContainer. This lets a sell-wand plugin deny a sale before it reads or
removes protected inventory contents.
The public contract remains API 1.0 in the separate
LederAPI repository;
LederProtections 1.5.0 does not change that contract.
The plugin embeds bStats and adds no custom charts or player/protection data.
The bStats library sends its standard technical metrics with a pseudonymous
server identifier. Server owners can disable bStats globally in
plugins/bStats/config.yml by setting enabled: false. See Dependencies
for details.
LederProtections cannot automatically control every third-party plugin: that plugin must call the public API before performing its protected action.
Include /lep version, /lep info, /lep check, server software, dependency
versions and relevant console errors when reporting a problem.