Wiki Release: 2026.09.5 · UltimateOutpost: 1.27.1 · Documentation branch: 1
UltimateOutpost permissions#
UltimateOutpost uses Bukkit permissions to control player and administrator command access. Test with a non-OP account because OP can mask missing permission nodes.
Player permissions#
The player command root is /outpost. Give individual nodes when you want fine-grained access, or use the player package declared by the plugin where appropriate.
uoutposts.player.help#
Shows help for the current command tree.
Related command: /outpost help
uoutposts.player.cancel#
Cancels a player-side interactive action.
Related command: /outpost cancel
uoutposts.player.stats#
Shows outpost statistics.
Related command: /outpost stats
uoutposts.player.events#
Shows event information; the configured branch exposes next and all.
Related command: /outpost events
uoutposts.player.info#
Shows details about an outpost.
Related command: /outpost info
uoutposts.player.loots#
Shows configured loot information.
Related command: /outpost loots
uoutposts.player.advantages#
Shows player-facing advantages or administratively manages advantage definitions, depending on the root command.
Related command: /outpost advantages
uoutposts.player.list#
Lists configured outposts.
Related command: /outpost list
uoutposts.player.abandon#
Releases/abandons an owned outpost through the supported ownership flow.
Related command: /outpost abandon
Administrator permissions#
The administrative root is /uoutpost. Grant these permissions only to staff who need the corresponding editing action.
uoutposts.admin.help#
Shows help for the current command tree.
Related command: /uoutpost help
uoutposts.admin.tp#
Teleports an administrator to an outpost.
Related command: /uoutpost tp
uoutposts.admin.reload#
Reloads UltimateOutpost configuration/runtime files.
Related command: /uoutpost reload
uoutposts.admin.wand#
Gives the outpost selection wand.
Related command: /uoutpost wand
uoutposts.admin.create#
Creates an outpost from the current selection/creation flow.
Related command: /uoutpost create
uoutposts.admin.move#
Moves a configured outpost.
Related command: /uoutpost move
uoutposts.admin.delete#
Deletes an outpost.
Related command: /uoutpost delete
uoutposts.admin.list#
Lists configured outposts.
Related command: /uoutpost list
uoutposts.admin.view#
Shows a configured outpost and its current settings.
Related command: /uoutpost view
uoutposts.admin.commands#
Manages event command actions.
Related command: /uoutpost commands
uoutposts.admin.loots#
Shows configured loot information.
Related command: /uoutpost loots
uoutposts.admin.keys#
Manages key-block behavior and key items.
Related command: /uoutpost keys
uoutposts.admin.seticon#
Changes the outpost icon.
Related command: /uoutpost seticon
uoutposts.admin.proximity#
Toggles or changes proximity behavior.
Related command: /uoutpost proximity
uoutposts.admin.setcapture#
Changes capture-related settings.
Related command: /uoutpost setcapture
uoutposts.admin.hologram#
Manages holograms through the active hologram integration.
Related command: /uoutpost hologram
uoutposts.admin.stats#
Shows outpost statistics.
Related command: /uoutpost stats
uoutposts.admin.extension#
Manages extension adapters.
Related command: /uoutpost extension
uoutposts.admin.adminmode#
Toggles administrative editing mode.
Related command: /uoutpost adminmode
uoutposts.admin.advantages#
Shows player-facing advantages or administratively manages advantage definitions, depending on the root command.
Related command: /uoutpost advantages
uoutposts.admin.maintenance#
Runs/opens supported maintenance operations without editing the database directly.
Related command: /uoutpost maintenance
uoutposts.admin.settings#
Manages outpost settings.
Related command: /uoutpost settings
uoutposts.admin.interactions#
Lists, views, toggles and configures interaction rules from interactions.yml.
Related command: /uoutpost interactions
Permission troubleshooting#
- Test with OP disabled.
- Confirm the exact permission node in the installed
commands.yml. - If the command works but an integration action does not, check the external plugin/integration separately.
- Do not grant the global wildcard just to fix one command; grant the smallest required node first.