Repository navigation
Permissions
ErikEdits edited this page Nov 1, 2026
·
1 revision
With LuckPerms or another permission mod, every command has a node.
| Node | Default without a permission mod |
|---|---|
justquests.command.<name>: list, categories, stats, leaderboard, progress, accept, abandon, claim, team, discord
|
everyone |
justquests.admin.<name>: reload, reroll, mainquests, difficulty, generator, test, admin
|
operators (level 2) |
The permission of a quest, for example myserver.vip
|
operators (level 2) |
justquests.admin.* gives all operator commands.
Give a quest a permission:
{
"title": "VIP Quest",
"permission": "myserver.vip",
"objectives": [
{ "type": "justquests:reach_level", "level": 10 }
],
"rewards": []
}Players without the node don't see it in /quest list, in the quest book or in tab completion.
NeoForge and Forge learn the quest nodes when the server starts, so a node added while the server runs works after the next restart. Fabric needs no restart.
The Fabric builds bundle fabric-permissions-api.
The plugin adds open, track, bossbar, book and goal to the player nodes. Its operator commands are reload, reroll, mainquests, difficulty, generator, npc, test and admin.
Modrinth · CurseForge · Discord · Issues
Getting started
Writing quests
Running a server
Addons
Help