Skip to content

Permissions

GreatNPC uses Fabric Permissions API checks. A compatible permissions provider can grant or deny nodes explicitly; otherwise each check uses its specified fallback.

Administration commands

These nodes fall back to Minecraft operator permission level 2:

Node Used by
greatnpc.reload reload, reload force, autoreload.
greatnpc.list list.
greatnpc.spawn Humanoid/Pokémon spawn.
greatnpc.info info.
greatnpc.validate validate.
greatnpc.export export and overwrite.
greatnpc.test Administrator test battle.
greatnpc.history View player battle history.
greatnpc.reset reset, resetfirst, resetbattle, and preset-manager history resets.
greatnpc.where Locate loaded NPCs by trainer.
greatnpc.tp Teleport command.
greatnpc.edit Editor commands, editor opening, and preset-manager access.
greatnpc.debug Toggle debug logging.
greatnpc.sethome Set NPC home.
greatnpc.remove Remove NPC command.
greatnpc.migrate Legacy/Easy NPC migration commands.

greatnpc.config is checked at level 2 by the command branch, then at level 3 by Main Config itself. Without an explicit provider grant, opening or changing Main Config therefore requires operator level 3.

Tools, files, and menus

Node Fallback Purpose
greatnpc.tools Operator level 2 Use GreatNPC administration items and tool requests.
greatnpc.edit.files Operator level 2 Write shared team/preset files and manage preset categories.
greatnpc.trainers Granted Use /trainers and compatibility commands.
greatnpc.menu.teleport Denied Use teleport buttons in the trainer menu. This is separate from greatnpc.tp.
greatnpc.mecanicdebug Granted Run the stuck-transformation repair on the player's own Pokémon.

Tool access, editor access, shared-file writing, and history-reset access are different checks. Grant the specific nodes required by the intended workflow. For example, an NPC editor who should not modify shared files needs greatnpc.edit and the applicable tool access, without a grant for greatnpc.edit.files.

Per-trainer permissions

The preset's permission field is an additional requirement for normal battles. Its fallback is denied, so players need an explicit grant when a permission string is configured.

{
  "permission": "myserver.gym.rock"
}

A dialogue/trade action can also use a condition of type permission. The condition's value is the required node, with a denied fallback. Permission checks are additional to command tags, prerequisites, party rules, and rematch restrictions.

menu_permission controls whether a trainer appears in the trainer menu. Category permissions come from the Main Config category-permission mapping. These visibility checks use operator level 2 as fallback when a node is configured.

For example, the category-permission field can contain:

gyms=myserver.menu.gyms;elite=myserver.menu.elite

The category name comes from menu_category when set, otherwise from the trainer ID's category grouping. A menu visibility permission does not by itself prohibit challenging a visible world NPC; configure the battle permission if the challenge must also be gated.

Example with LuckPerms

If LuckPerms is installed, these are standard LuckPerms command examples:

/lp group default permission set greatnpc.trainers true
/lp group builders permission set greatnpc.tools true
/lp group builders permission set greatnpc.edit true
/lp group builders permission set greatnpc.edit.files false
/lp group gymmembers permission set myserver.gym.rock true

Group names are examples. Other providers have their own command syntax; GreatNPC requires the permission nodes, not a particular provider's management UI.