permissions.json

Defines ranks, the permissions each rank holds, rank inheritance, chat-prefix metadata, and the operator rank that must keep full access.

Operator stays operator

Do not remove * from the operator rank. Validation restores it because the server needs a guaranteed full-access recovery rank.

Concepts

  • Ranks can inherit from other ranks.
  • Wildcards are supported by the permission logic.
  • The rank management UI is the preferred way to create or delete ranks.
  • /config exposes permissions, but rank creation should stay in the rank editor to avoid duplicate systems.

Common fields

FieldMeaning
versionConfig schema version.
defaultRankIdRank used when a player has no known rank. Default: user.
operatorRankIdRank that must keep full operator access. Default: operator.
aliasesLegacy rank aliases. Defaults: player -> user, admin -> operator.
ranks[].idStable lower-case rank id.
ranks[].displayNameHuman-readable rank name. Max 48 characters.
ranks[].priorityDisplay and sort priority, clamped between -10000 and 10000.
ranks[].chatPrefixOptional chat prefix. Max 20 characters.
ranks[].chatPrefixColorOptional hex color for prefix.
ranks[].chatNameColorOptional hex color for player name.
ranks[].chatMessageColorOptional hex color for message text.
ranks[].inheritsParent rank ids whose permissions are inherited.
ranks[].permissionsPermission nodes and wildcards granted to the rank.

Default ranks

  • user: default player rank, no permissions.
  • operator: operator rank, must keep *.
  • player: legacy alias for user.
  • admin: legacy alias for operator.

Permission syntax

  • * grants everything.
  • Exact nodes such as jobs.manage grant one capability.
  • Section wildcards such as jobs.* grant every node in that section.
  • Wildcards are only valid as * or as the final segment (for example moderation.*).
  • Rank ids and permission segments use lower-case letters, numbers, _, and -.

Supported section wildcards:

  • admin.*
  • permissions.*
  • spawn.*
  • players.*
  • economy.*
  • inventory.*
  • moderation.*
  • whitelist.*
  • tickets.*
  • logs.*
  • stats.*
  • server.*
  • jobs.*
  • shop.*
  • npcs.*
  • map.*
  • government.*
  • tools.*
  • vehicles.*
  • rewards.*
  • theme.*
  • social.*
  • backend.*
  • addons.*

Supported permission nodes

SectionNodes
Adminadmin.access, admin.mode, admin.mode.settings, admin.teleport.position, admin.telemetry.dump, admin.telemetry.reset, admin.config.view, admin.config.edit, admin.config.reload, admin.config.reset
Permissionspermissions.ranks.manage, permissions.ranks.assign
Spawnspawn.entities
Playersplayers.view, players.name.set, players.job.set, players.health.set, players.armor.set, players.hunger.set, players.kill, players.respawn, players.teleport.to, players.teleport.here, players.props.cleanup, players.god, players.weapon.give
Economyeconomy.view, economy.money.set, economy.bank.set
Inventoryinventory.view, inventory.item.give, inventory.backpack.set, inventory.backpack.clear, inventory.hotbar.remove, inventory.hotbar.clear, inventory.hotbar.clip.set
Moderationmoderation.view, moderation.warn, moderation.kick, moderation.ban, moderation.mute, moderation.jobban, moderation.jail, moderation.revoke
Whitelistwhitelist.view, whitelist.toggle, whitelist.add, whitelist.remove, whitelist.kick
Ticketstickets.view, tickets.claim, tickets.resolve, tickets.close, tickets.teleport
Logslogs.view
Statsstats.view
Server healthserver.health.view
Jobsjobs.manage
Shopshop.manage
NPCsnpcs.manage
Mapmap.doors.manage, map.glass.manage
Governmentgovernment.manage
Toolstools.manage
Vehiclesvehicles.manage, vehicles.spawn
Rewardsrewards.manage
Themetheme.manage
Socialsocial.manage
Backendbackend.manage Studio only
Addonsaddons.manage
backend.* is reserved for Lithera Studio

backend.* and backend.manage back Lithera Studio backend operations. Community servers should not grant, document, or rely on these permissions. The node is listed here only so existing config files do not look mysterious.

Reload

Use litherarp.permissions_reload after manual edits.