Repository navigation
Rules‐System
LederProtections includes a custom rule engine on top of WorldGuard.
WorldGuard is used as the region backend, but LederProtections controls gameplay permissions through its own role-based rule system.
Using only WorldGuard flags can be too broad.
For example, build: deny may block too many interactions.
LederProtections allows more precise control per role and per action.
Rules can be configured for:
- Owner
- Co-owner
- Member
- Visitor
- Blocked
- Admin
Rules can control actions such as:
- block breaking
- block placing
- container opening
- door usage
- button usage
- lever usage
- trapdoor usage
- fence gate usage
- item pickup
- item drop
- PvP
- animal damage
- entity interaction
- hopper interaction
- redstone interaction
- ender pearl access
- projectile access
Rules are displayed in a friendly way in the GUI.
The plugin avoids showing technical labels like:
ALLOW
DENY
NON_MEMBERS
to normal players when possible.
Open:
/p
Then:
- Right-click a protection.
- Open management.
- Open rules.
- Select a role.
- Configure actions.
Rules can be reset from the GUI using the reset button.
This restores default behavior for that role.
Owners and admins have high-level control.
Admins with:
lederprotections.admin
can bypass restrictions.
Blocked players are evaluated with high priority.
This prevents a blocked player from keeping access because they were also previously added as a member.
The rule engine is evaluated server-side.
LederProtections does not trust the client.
This helps prevent bypasses through:
- hacked clients
- fake GUI clicks
- renamed items
- external interactions
- cross-border mechanics