Repository navigation
Roles and Members
This page explains how protection ownership, members, co-owners, visitors and blocked players work in LederProtections.
Roles define what each player can do inside a protection.
LederProtections uses a role-based system to control access inside protected areas.
| Role | Description |
|---|---|
| Owner | Main owner of the protection. |
| Co-owner | Trusted player with elevated management access. |
| Member | Allowed player with normal access. |
| Visitor | Player without special access. |
| Blocked player | Player explicitly blocked from the protection. |
| Administrator | Staff member using administrative permissions. |
The owner is the player who owns the protection.
A player usually becomes the owner when they place a valid protection stone.
Owners can usually:
- manage members;
- manage co-owners;
- rename the protection;
- transfer the protection;
- upgrade the protection;
- set teleport points;
- configure protection rules;
- remove the protection;
- access protected blocks and interactions.
Some actions may depend on configuration and permissions.
A co-owner is a trusted player with elevated access inside a protection.
Co-owners can usually help manage the protection, depending on configuration.
Common co-owner abilities:
| Ability | Description |
|---|---|
| Access protection | Can interact with allowed protected blocks. |
| Manage members | Can add or remove normal members if allowed. |
| Edit rules | Can change some protection rules if allowed. |
| Use protection features | Can use protection features depending on configuration. |
Co-owners should only be trusted players.
A member is a player who has been granted normal access to a protection.
Members can usually:
- open allowed containers;
- use allowed doors, trapdoors, buttons or levers;
- interact with allowed protected blocks;
- build or break if the protection rules allow it.
Members normally cannot manage ownership or administrative settings.
A visitor is any player who is not the owner, co-owner or member of the protection.
Visitors are usually restricted by protection rules.
Depending on configuration, visitors may be blocked from:
- breaking blocks;
- placing blocks;
- opening containers;
- using doors or trapdoors;
- using buttons or levers;
- picking up protected items;
- damaging players;
- interacting with protected systems.
Blocked players are explicitly denied access to a protection.
This can be used when a player should not interact with a protection even if other rules would normally allow basic visitor behavior.
Blocked-player behavior depends on configuration, but it is generally stricter than visitor behavior.
Administrators are staff members with LederProtections admin permissions.
Important behavior:
| Command | Behavior |
|---|---|
/p |
Shows the administrator's personal protections only. |
/lep admin |
Opens the server-wide admin protection browser. |
Administrators do not automatically see all protections in /p.
This separation keeps the normal player GUI clean and prevents accidental confusion between personal protections and administrative tools.
When LederProtections checks what a player can do, it determines the player's relationship to the protection.
General priority:
| Priority | Role / Condition |
|---|---|
| 1 | Administrator bypass, if granted. |
| 2 | Owner. |
| 3 | Co-owner. |
| 4 | Member. |
| 5 | Blocked player. |
| 6 | Visitor. |
Exact behavior may depend on configuration and rule settings.
Players can manage protection members through the protection GUI.
Open the protection menu:
/p
Then select the protection and open the member management menu.
Depending on the GUI, members may be shown with player heads or player-related icons.
Owners and allowed co-owners can add members to a protection.
Typical flow:
- Open
/p. - Select the protection.
- Open member management.
- Add the player.
- Choose or confirm their role.
The target player must usually exist or be resolvable by the server.
Owners and allowed co-owners can remove members from a protection.
Typical flow:
- Open
/p. - Select the protection.
- Open member management.
- Select the member.
- Confirm removal.
Removal should update the protection immediately and persist safely.
Depending on configuration, owners and allowed co-owners can change a player's role.
Common role changes:
| From | To |
|---|---|
| Member | Co-owner |
| Co-owner | Member |
| Visitor | Member |
| Member | Removed |
Be careful when promoting players to co-owner because co-owners may have management access.
The owner can transfer a protection to another player if the feature is enabled and permitted.
Ownership transfer changes who controls the protection.
Before transferring, make sure the new owner is trusted.
Possible effects:
- the old owner may lose owner privileges;
- the new owner becomes responsible for the protection;
- member and co-owner lists may remain depending on implementation and configuration.
| Role | Suggested access |
|---|---|
| Owner | Full access. |
| Co-owner | Full trusted access. |
| Member | Build and interact. |
| Visitor | No build or container access. |
| Blocked player | No access. |
| Role | Suggested access |
|---|---|
| Owner | Full access. |
| Co-owner | Manage members and rules. |
| Member | Use farm and containers if allowed. |
| Visitor | View only. |
| Blocked player | No access. |
| Role | Suggested access |
|---|---|
| Owner | Full access. |
| Co-owner | Manage shop-related access. |
| Member | Restock or manage shop blocks if allowed. |
| Visitor | Interact only with allowed public systems. |
| Blocked player | No access. |
LederProtections separates normal player usage from administrative browsing.
| Feature | Command | Purpose |
|---|---|---|
| Personal protection menu | /p |
Shows protections where the player has a normal role. |
| Admin protection browser | /lep admin |
Shows server-wide protection data for staff. |
This means administrators can still use /p like normal players without mixing all server protections into their personal menu.
For normal players:
lederprotections.use
lederprotections.border
lederprotections.shop
lederprotections.upgrade
lederprotections.sethome
For administrators:
lederprotections.admin
lederprotections.admin.protections
lederprotections.info
lederprotections.update
For full trusted owner-level debugging:
lederprotections.bypass.rules
Do not give bypass permissions to normal players.
Recommended practices:
- Only promote trusted players to co-owner.
- Keep owner transfer restricted to trusted use.
- Do not give admin permissions to normal players.
- Do not give bypass permissions to normal players.
- Use
/lep adminfor staff review instead of relying on/p. - Review members before transferring a protection.
- Test member permissions after changing rules.
Check that:
- the player was added correctly;
- the player has the expected role;
- the protection rules allow that action;
- the player is not blocked;
- the protection data saved correctly.
Check that:
- the player is actually a co-owner;
- co-owner management permissions are enabled;
- the protection rules allow co-owner management;
- the player has any required plugin permission.
This is expected behavior.
/p is the personal protection menu.
Use this command instead:
/lep admin
Check that:
- the player is listed as blocked in the correct protection;
- the action is handled by LederProtections rules;
- the player does not have bypass permissions;
- the protection region exists and is loaded correctly.