Repository navigation
Anti Exploit Protection
This page explains the anti-exploit protections included in LederProtections.
LederProtections is designed to protect player builds not only from direct actions, but also from common bypass methods involving redstone, projectiles, explosions, fluids and automated systems.
Protection plugins need to handle more than simple block breaking.
Players may attempt to bypass protections using:
- pistons;
- sticky pistons;
- hoppers;
- dispensers;
- droppers;
- TNT;
- explosions;
- fire;
- lava;
- water;
- projectiles;
- fake players;
- inventory GUI tricks.
LederProtections includes checks for these types of behavior.
Anti-exploit checks apply when an action affects:
- a protected area;
- a block inside a protection;
- an entity inside a protection;
- an inventory inside a protection;
- an action crossing a protection boundary.
Boundary-crossing actions are especially important because they can allow players outside a protection to affect something inside it.
LederProtections protects its GUIs against common inventory manipulation tricks.
Examples:
| Interaction | Expected behavior |
|---|---|
| Shift-click | Blocked in plugin GUIs. |
| Number-key swap | Blocked in plugin GUIs. |
| Double-click | Blocked in plugin GUIs. |
| Dragging items | Blocked in plugin GUIs. |
| Dropping items | Blocked in plugin GUIs. |
| Offhand swap | Blocked in plugin GUIs. |
This helps prevent item duplication, item extraction and GUI desynchronization issues.
Spigot-compatible servers can sometimes show ghost-item behavior when inventory interactions are cancelled.
LederProtections includes extra inventory synchronization to reduce these issues.
Recommended tests:
| Test | Expected result |
|---|---|
| Shift-click inside GUI | Item is not taken. |
| Number-key swap inside GUI | Swap is cancelled. |
| Drag item through GUI | Drag is cancelled. |
| Close GUI after blocked click | Inventory remains correct. |
Pistons can be used to push blocks into protected areas.
LederProtections checks piston movement to prevent protection bypasses.
Expected behavior:
| Situation | Expected result |
|---|---|
| Piston pushes block into protection | Blocked |
| Piston pushes block out of protection | Blocked if crossing protected boundary |
| Piston moves blocks entirely outside protections | Allowed |
| Piston moves blocks entirely inside allowed context | Allowed depending on rules |
Sticky pistons can pull blocks out of protected areas.
Expected behavior:
| Situation | Expected result |
|---|---|
| Sticky piston pulls protected block out | Blocked |
| Sticky piston pulls block into protection | Blocked |
| Sticky piston operates outside protection | Allowed |
| Sticky piston operates within same allowed context | Allowed depending on rules |
Hoppers can be used to extract items from protected containers.
LederProtections checks hopper behavior to prevent unauthorized item movement.
Expected behavior:
| Situation | Expected result |
|---|---|
| Hopper extracts from protected chest | Blocked |
| Hopper pulls items across protection border | Blocked |
| Hopper works outside protections | Allowed |
| Hopper works within same allowed context | Allowed depending on rules |
Dispensers and droppers can be used for automation bypasses.
LederProtections checks dispenser and dropper behavior when it affects protected areas.
Expected behavior:
| Situation | Expected result |
|---|---|
| Dispenser interacts across protection border | Blocked |
| Dropper transfers across protection border | Blocked |
| Dispenser operates outside protections | Allowed |
| Dispenser operates within same allowed context | Allowed depending on rules |
Dispensers can fire arrows or other projectiles into protected areas.
LederProtections blocks dispenser-fired projectile damage when it crosses protection boundaries.
Expected behavior:
| Projectile case | Result |
|---|---|
| Dispenser outside shoots player inside protection | Damage blocked |
| Dispenser inside shoots player outside protection | Damage blocked |
| Dispenser in protection A shoots player in protection B | Damage blocked |
| Dispenser and target are in same protection context | Normal behavior |
| Dispenser and target are both outside protections | Normal behavior |
This prevents dispenser arrows from being used as a PvP or damage bypass.
Explosions can damage blocks inside protected areas.
LederProtections includes checks to prevent protected blocks from being damaged by explosion-related behavior.
Expected behavior:
| Explosion case | Expected result |
|---|---|
| TNT explodes near protection | Protected blocks remain safe |
| Creeper explosion affects protection | Protected blocks remain safe |
| Explosion outside reaches inside | Protected impact is blocked |
| Explosion outside protections | Normal behavior |
Fire can be used to damage or modify protected areas.
LederProtections can protect against unauthorized fire behavior.
Expected behavior:
| Fire case | Expected result |
|---|---|
| Unauthorized flint and steel use | Blocked |
| Fire charge used into protection | Blocked |
| Fire spreads into protected area | Blocked depending on rules |
| Fire outside protections | Normal behavior |
Fluids can cross protection boundaries and affect protected areas.
LederProtections checks fluid behavior to prevent unwanted modification.
Expected behavior:
| Fluid case | Expected result |
|---|---|
| Lava flows into protection | Blocked depending on rules |
| Water flows into protection | Blocked depending on rules |
| Fluid starts inside and flows outside | Blocked if crossing boundary |
| Fluid stays within same allowed context | Allowed depending on rules |
LederProtections can block PvP damage and related knockback behavior in protected areas.
Expected behavior:
| PvP case | Expected result |
|---|---|
| Visitor attacks protected player | Damage blocked |
| PvP denied inside protection | Knockback prevented |
| Repeated denied hits | Message spam reduced |
| PvP allowed by rules | Normal behavior |
Some plugins use fake players or simulated actors.
LederProtections includes protections for fake-player edge cases where possible.
Expected behavior:
| Fake-player case | Expected result |
|---|---|
| Fake player tries protected action | Rule engine checks action |
| Fake player causes PvP-like behavior | Denied if protection rules block it |
| Fake player causes repeated denied actions | Spam should be reduced |
Exact behavior can depend on the fake-player plugin.
Item pickup can be restricted inside protected areas.
Expected behavior:
| Situation | Expected result |
|---|---|
| Visitor picks up protected item | Blocked depending on rules |
| Member picks up item | Allowed depending on rules |
| Owner picks up item | Allowed |
| Bypass permission present | May bypass rules |
Boundary-crossing checks are important.
Examples:
| Action | Risk |
|---|---|
| Piston outside pushes block inside | Unauthorized block movement |
| Hopper outside pulls from chest inside | Item theft |
| Dispenser outside shoots inside | Damage bypass |
| Lava outside flows inside | Griefing |
| TNT outside damages inside | Explosion bypass |
LederProtections aims to block these cases while preserving normal behavior when actions do not affect protected areas.
Before production use, test:
| Test | Expected result |
|---|---|
| Visitor breaks block inside protection | Blocked |
| Visitor places block inside protection | Blocked |
| Visitor opens chest inside protection | Blocked |
| Piston pushes into protection | Blocked |
| Sticky piston pulls from protection | Blocked |
| Hopper extracts from protected chest | Blocked |
| Dispenser shoots arrow into protection | Damage blocked |
| Dispenser shoots from inside to outside | Damage blocked |
| TNT explodes near protection | Protected blocks remain safe |
| Lava flows into protection | Blocked depending on rules |
| Water flows into protection | Blocked depending on rules |
| Visitor attacks player inside protection | Damage and knockback blocked |
| Plugin GUI shift-click | Blocked |
| Plugin GUI number-key swap | Blocked |
Check that:
- the plugin is updated to the latest version;
- the internal rule engine is enabled;
- the action is actually inside or crossing a protection;
- the actor does not have bypass permission;
- another plugin is not overriding the event;
- WorldGuard and WorldEdit are loaded correctly.
Check:
- whether the redstone action crosses a protection boundary;
- whether the action occurs inside the same protection context;
- rule configuration;
- bypass permissions;
- other protection plugins.
Check:
- PvP rule configuration;
- player roles;
- protection location;
- bypass permissions;
- other combat plugins.
Check:
- the installed LederProtections version;
- whether the arrow was fired by a dispenser;
- whether the dispenser and target are in different protection contexts;
- whether the target has bypass or special permissions;
- console errors.
Recommended practices:
- Keep the plugin updated.
- Test protections after every major update.
- Avoid giving bypass permissions to normal players.
- Test automation systems near protection borders.
- Test GUIs on Spigot-compatible servers.
- Use
/lep checkafter configuration changes. - Keep backups before major server changes.