Skip to content

Rules‐System

Alexisleder edited this page May 29, 2026 · 1 revision

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.


Why a Custom Rule Engine?

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.


Roles

Rules can be configured for:

  • Owner
  • Co-owner
  • Member
  • Visitor
  • Blocked
  • Admin

Actions

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

Rule Results

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.


GUI Rule Management

Open:

/p

Then:

  1. Right-click a protection.
  2. Open management.
  3. Open rules.
  4. Select a role.
  5. Configure actions.

Resetting Rules

Rules can be reset from the GUI using the reset button.

This restores default behavior for that role.


Owner and Admin Access

Owners and admins have high-level control.

Admins with:

lederprotections.admin

can bypass restrictions.


Blocked Priority

Blocked players are evaluated with high priority.

This prevents a blocked player from keeping access because they were also previously added as a member.


Security

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

Clone this wiki locally