Build rights management

These commands change who may create levels on the server, and who administers it.

They exist so that nobody has to type LuckPerms commands by hand. Each one is a single intent carried out in full: promoting an administrator, for instance, grants the LuckPerms group and operator status in one action, because doing it in two is two chances to do half the job.

All five require the admin permission, and all five work on a player who is offline — a sanction you could only apply to someone standing in front of you would be no use against whoever logs off right after misbehaving.

ℹ️ LuckPerms holds all of it. Membership of the creator group is the right to build; the sanction is a permission node on the player. The plugin keeps no list of its own, so an administrator who prefers /lp gets exactly the same result — there is no second source of truth that could disagree.

What each command actually does

Nothing here is magic — each command is a fixed combination of the raw commands you would otherwise type yourself, in one step and without forgetting half of it.

Command	Equivalent to
giveCreator <player>	/lp user <player> parent add creator
sanction <player> "<reason>"	/lp user <player> parent remove creator /lp user <player> permission set leplayserverutils.creator false plus meta nodes recording the reason, its author and the date
pardon <player>	/lp user <player> permission unset leplayserverutils.creator plus removal of those meta nodes
promoteAdmin <player>	/lp user <player> parent add admin /op <player>
demoteAdmin <player>	/lp user <player> parent remove admin /deop <player> /lp user <player> parent add creator

Give the builder role

Grants the right to create levels to somebody who has not earned it through play.

• Type /. rights giveCreator <player>.
• Refused while the player is under sanction, and the refusal quotes the reason. This is not a formality: the sanction is a negative node on the player, which beats the positive one the group would bring, so adding them back to the group really would change nothing.

Sanction a builder

Bars a player from creating levels until further notice.

• Type /. rights sanction <player> "<reason>".
• The reason is mandatory and is shown to the player when they try to build. Without it they do not know what happened, and neither does the next administrator to look.
• The levels they have already published are untouched. The sanction targets the ability to create, not work that other players are already enjoying. If one particular level is the problem, deal with that level separately — they are two decisions and should not be coupled.

Lift a sanction

• Type /. rights pardon <player>.
• This does not hand the builder role back by itself. A player who earned the role is promoted again on their own once their proportion of solved levels is re-evaluated. A player who had been given it by hand needs /. rights giveCreator again — restoring it here would hand the right to somebody who never met the bar and whose grant nobody remembers.

Promote an administrator

• Type /. rights promoteAdmin <player>.
• Adds the admin LuckPerms group and grants operator, in one action.

Remove an administrator

• Type /. rights demoteAdmin <player>.
• Removes the admin group and operator status, and leaves the player in the creator group rather than dropping them to the default one. Somebody who has been an administrator has certainly earned the right to build, and taking that away too would be a second decision nobody asked for.

Audit trail

Every one of these actions is written to the server log, and announced on Discord when rightsAuditDiscordWebhookUrl is set in the plugin configuration. The message names the operator, the action, the player and the reason.