Repository navigation
Permissions
alexisleder edited this page Sep 27, 2026
·
5 revisions
| Permission | Default | Purpose |
|---|---|---|
lederprotections.use |
true | Basic player features. |
lederprotections.warps |
true | Open and visit the public directory. |
lederprotections.shop |
true | Use the stone shop. |
lederprotections.border |
true | Show protection borders. |
lederprotections.sethome |
true | Set allowed teleport homes. |
lederprotections.upgrade |
true | Upgrade owned protections. |
lederprotections.info |
op | Runtime and compatibility information. |
lederprotections.update |
op | Update notifications. |
lederprotections.admin |
op | Main administrator permission and child permissions. |
lederprotections.admin.protections |
op | Global admin browser. |
lederprotections.admin.migrate |
op | ProtectionStones migration. |
lederprotections.admin.export |
op | Native export. |
lederprotections.admin.import |
op | Native import. |
lederprotections.bypass.rules |
op | Bypass the internal rule engine. |
Stone permissions follow the configured type ID, for example
lederprotections.stone.4. Default bundled permissions are provided for types
4, 8, 16, 32 and 64.
Global limits can use lederprotections.limit.<number> or
lederprotections.limit.unlimited. Per-type limits can use patterns such as
lederprotections.limit.x8.3 or lederprotections.limit.type.8.3, depending on
the configured limit rules.
Grant admin, import, migration and bypass permissions only to trusted staff.
lederprotections.bypass.rules is a technical bypass; it does not make a player
an owner/member in Public API role queries.