Permissions
Four nodes, three of them on by default.
| Node | Default | Grants |
|---|---|---|
corejobs.use |
true | /jobs, and the /farmpoints subcommands |
corejobs.shop.use |
true | Opening and buying from the farmpoints shop |
corejobs.ranking.claim |
true | Claiming monthly ranking rewards |
corejobs.admin |
op | Everything under /corejobs: reload, farmpoints, job, boost, shop, papi, resetranking |
Typical setup
Nothing to do. Players get the first three nodes, staff with op get admin.
Negate corejobs.use for the default group, grant it to a members rank so new joins cannot earn until they are verified.
Grant corejobs.admin to your staff rank instead of handing out op.
corejobs.admin includes /corejobs resetranking confirm and /corejobs farmpoints set. Give it to the same people you would trust with an economy command.
Notes on the current build
corejobs.ranking.claim is declared but not enforced
The node exists and defaults to true, so nothing changes in practice: everyone can claim their own staged reward. The claim button does not check the node in this build, so negating it does not currently block a claim. Treat it as reserved.
Per-job permission nodes
An older comment in jobs.yml mentions a corejobs.job.<id> node per job. No such check runs in this build. Every player can work every job.
Checking what a player has
Most permission plugins expose a check command, for example:
/lp user <player> permission check corejobs.use
If /jobs prints the no permission line, that is corejobs.use missing. If the menu opens but the shop button does nothing, that is corejobs.shop.use.
