Repository navigation
Borders
This page explains how protection border previews work in LederProtections.
Borders help players visualize the limits of their protections using particles.
A protection border is a visual preview of the protected area.
It helps players understand where their protection starts and ends.
Common uses:
- checking the size of a protection;
- confirming if a build is inside the protected area;
- checking the result after an upgrade;
- verifying protection placement;
- helping staff inspect protection boundaries.
The main border command is:
/p border
This command shows or hides the visual border of the current or nearby protection, depending on context and configuration.
The border preview is shown only to the player who requested it.
Other players should not see the particles unless they also enable their own border preview.
This prevents visual spam and keeps the feature clean for multiplayer servers.
To view a protection border:
- Stand inside or near a protection.
- Run:
/p border
- The protection border should appear using particles.
- Run the command again to hide it, if supported.
Expected behavior:
| Situation | Expected result |
|---|---|
| Player is inside a protection | Border preview is shown. |
| Player is near or selecting a protection | Border preview may be shown depending on context. |
| Player has no protection context | Plugin should show a message. |
Player runs /p border again |
Border preview may toggle off. |
| Protection is upgraded | Border should reflect the new size. |
| Protection is removed | Border should stop or become unavailable. |
Border preview may require permission.
Common permission:
lederprotections.border
Recommended for normal players:
lederprotections.border
Protection borders are designed as a personal preview.
| Viewer | Can see border |
|---|---|
Player who used /p border
|
Yes |
| Other nearby players | No |
| Administrators nearby | No, unless they enable their own preview |
| Console | No |
This keeps borders useful without creating unnecessary particle spam for everyone.
Particles can have a performance impact if used excessively.
LederProtections is designed so border previews are temporary and player-specific.
Recommended practices:
- avoid permanent global borders;
- avoid showing borders to every player at once;
- keep border previews temporary;
- use borders only when players need to inspect an area.
After placing a protection stone:
/p border
Use the border to confirm that the protected area covers your build.
After upgrading a protection, use:
/p border
This helps confirm that the new radius was applied correctly.
Players and staff can use borders to see how close protections are to each other.
This is useful when diagnosing placement issues or explaining why an overlap was denied.
Administrators can inspect protection boundaries when investigating issues.
Useful commands:
/lep admin
/p border
/lep check
After updating or changing configuration, test:
| Test | Expected result |
|---|---|
Use /p border inside a protection |
Border appears. |
Use /p border outside a protection |
A clear message appears. |
Use /p border after upgrading |
Border uses the new size. |
Use /p border after removing protection |
Border is no longer shown. |
| Nearby player watches | Nearby player does not see your border. |
| Restart server and use border | Border still works normally. |
Check that:
- the player is inside or near a valid protection;
- the player has permission;
- particles are enabled in the client settings;
- the protection exists and is loaded;
- there are no console errors.
Check that:
- the protection radius is correct;
- the stone type is configured correctly;
- the protection was upgraded successfully;
-
/lep checkreports no problems; - the server was restarted after major configuration changes.
Borders should normally be player-specific.
If other players appear to see the border:
- confirm they did not also run
/p border; - check for other plugins creating particle borders;
- test with only LederProtections and required dependencies if needed.
If border particles cause performance issues:
- reduce how often players use the feature;
- avoid enabling borders for many players at once;
- check server TPS;
- check client particle settings;
- make sure the server is not overloaded by other plugins.
Recommended practices:
- Use borders after placing a new protection.
- Use borders after upgrading a protection.
- Use borders when explaining protection limits to players.
- Keep borders temporary and player-specific.
- Do not use border previews as a replacement for proper protection diagnostics.
- Use
/lep checkif protection data seems incorrect.