Overview

Everything lives under one root, /claim, with six sub-roots below it.

/claim                  the smart root, see Claim commands
├── chunk    …          add and remove land
├── block    …          the visual claim block
├── invite   …          the invitation flow
├── member   …          roles and per-member permissions
├── role     …          create and configure roles
├── warp     …          teleport points
└── admin    …          staff only

Two permissions per command

Almost every command is gated twice:

Both must pass. uxmclaims.admin skips both, and so does a uxmclaims.bypass.* node for the matching action. The full node list is in Ability permissions.

Only one command is gated by a plain Bukkit permission in plugin.yml: /claim reload, which needs uxmclaims.admin.

Which claim a command acts on

Commands that say "the current claim" resolve it in this order:

1. The claim selected with /claim select, if any.
2. The claim you are standing in.

If neither applies you get "No claim selected. Use /claim select or stand in a claim." /claim select with no argument opens a picker menu; /claim select <name> picks by name and is what makes remote administration possible.

Confirmation

Destructive actions route through a confirmation step, then /claim confirm or /claim cancel:

/claim ban is deliberately immediate: it exists for the moment someone is already causing damage.

Aliases

aliases.yml maps a short command onto a /claim subcommand. Four ship by default:

Tab completion follows the target command automatically. Add your own and run /claim reload. See aliases.yml.