Repository navigation
FAQ
This page answers common questions about LederProtections.
LederProtections is a modern protection-stone plugin for Minecraft servers.
It lets players protect their builds using configurable protection stones, GUIs, WorldGuard regions, role-based rules, upgrades, economy features and anti-exploit protection.
Yes.
LederProtections is distributed as a free plugin.
The source code is currently private.
Not currently.
The source code is private while the project continues to mature.
The plugin may become open source in the future under clear terms.
LederProtections 1.4.0 supports:
Minecraft 1.21.x
Minecraft 26.1-26.3
Minecraft 1.21.x requires Java 21. Minecraft 26.1+ requires Java 25. Older versions before 1.21 are not officially supported.
LederProtections targets:
| Server software | Status |
|---|---|
| Spigot 1.21.x | Supported; baseline compile target |
| Spigot 26.x | Compiled successfully against API 26.3 |
| Paper 1.21.x and 26.x | Supported when a stable build exists; recommended |
| Purpur/Pufferfish | Supported when the fork and required dependencies support that Minecraft version |
A staging-server smoke test is recommended before production use.
Yes.
LederProtections uses WorldGuard as the region backend.
Yes.
WorldGuard requires WorldEdit, and LederProtections depends on WorldGuard working correctly.
Only if you want economy features.
Vault is needed for:
- protection shop purchases;
- paid protection upgrades;
- teleport costs.
If you do not use economy features, Vault is optional.
No.
Vault is only a bridge between plugins.
You still need a Vault-compatible economy plugin.
Only if you want to use LederProtections placeholders in other plugins.
LederProtections can run without PlaceholderAPI.
Players create protections by placing a valid protection stone in the world.
If the area is valid, LederProtections creates a WorldGuard-backed protection and assigns ownership to the player.
LederProtections can prevent protection overlap.
It is recommended to keep overlap prevention enabled.
This depends on configuration.
Common behavior:
| Setting | Behavior |
|---|---|
| Remove region on break | The protection is removed. |
| Return stone on break | The protection stone is returned. |
| Keep protection | The protection remains depending on configuration. |
Yes, if upgrades are configured.
Upgrade paths are configured in stones.yml.
Example:
x4 → x8 → x16 → x32 → x64
Yes.
Paid upgrades require Vault and a compatible economy plugin.
/p opens the player's personal protection menu.
It shows protections where the player has a normal role, such as owner, co-owner or member.
No.
Administrators do not automatically see every server protection in /p.
Use this command for administrative browsing:
/lep admin
This keeps the player menu clean and prevents administrators from mixing their personal protections with all server protections.
LederProtections includes GUI hardening against common inventory tricks such as shift-click, number-key swaps, double-click, dragging and dropping.
If you find a GUI issue, report it with reproduction steps.
Check that:
- the shop is enabled;
- Vault is installed;
- an economy plugin is installed;
- the player has permission;
- the player has enough money;
- the player has inventory space.
Check that:
- upgrade costs are configured;
- Vault is installed;
- an economy plugin is installed;
- economy support is enabled.
Check that:
- teleport cost is enabled;
- the cost is greater than
0; - Vault is installed;
- an economy plugin is installed;
- the teleport actually completes.
Teleport cost should not be charged if teleport is cancelled.
No.
It only checks Modrinth and notifies administrators when a newer version is available.
No.
It does not download plugin jars automatically.
Yes.
In config.yml:
update-checker:
enabled: falseThis can happen if you are testing a local version before it is published on Modrinth.
It can also happen if Modrinth has not updated yet.
Yes.
LederProtections includes checks for piston-based boundary bypasses.
Yes.
LederProtections includes checks to prevent unauthorized hopper extraction from protected inventories.
Yes.
Dispenser-fired projectile damage is blocked when it crosses protection boundaries.
LederProtections includes explosion protection checks for protected areas.
Always test TNT and explosion behavior after changing protection rules or other explosion-related plugins.
LederProtections can block PvP damage and related knockback behavior depending on protection rules.
Check:
- Java 21 with Minecraft 1.21.x, or Java 25 with Minecraft 26.1+;
- a supported Minecraft 1.21.x or 26.x server build;
- WorldEdit installed;
- WorldGuard installed;
- no duplicate LederProtections jars;
- console errors.
Check:
- the player has permission;
- the plugin loaded correctly;
- there are no console errors;
- the command is not overridden by another plugin.
Check:
- the player has permission for that stone;
- the stone exists in
stones.yml; - the area does not overlap another protection;
- the player has not reached a protection limit;
- WorldGuard and WorldEdit are working.
Check:
- whether the protection stone was broken;
- configuration for removing regions on break;
- WorldGuard region data;
- LederProtections data;
- backups;
- console errors.
Check:
- PlaceholderAPI is installed;
- the server was restarted;
- LederProtections registered its expansion;
- the placeholder is typed correctly;
- the plugin using the placeholder supports PlaceholderAPI.
Include:
- server software and version;
- Minecraft version;
- LederProtections version;
- WorldGuard version;
- WorldEdit version;
- Vault version, if used;
- PlaceholderAPI version, if used;
- economy plugin, if used;
- output of
/lep info; - output of
/lep version; - console errors;
- steps to reproduce the issue.