Repository navigation
Permissions
Marvin Honé edited this page Nov 3, 2026
·
3 revisions
| Permission | Default | Allows |
|---|---|---|
skin.command.player |
everyone | all commands for yourself (the four below) |
skin.command.edit |
everyone | /skincreator edit |
skin.command.choose |
everyone | /skincreator choose |
skin.command.reset |
everyone | /skincreator reset |
skin.command.default |
everyone | /skincreator default |
skin.command.* |
OP | all commands, also for other players |
skin.command.edit.other |
OP | /skincreator edit <player> |
skin.command.choose.other |
OP | /skincreator choose <player> |
skin.command.reset.other |
OP | /skincreator reset <player> |
skin.command.default.other |
OP | /skincreator default <player> |
To take a command away from players, set its permission to false in your permission plugin (e.g. LuckPerms).
You can rename the permissions in the language file (plugins/SkinCreator/locale/messages_<language>.yml, keys Permission_Command_...). Renamed permissions are only granted to OPs by default, so you have to give them to your players yourself.
You can also use your own permissions in the Dashboard:
-
Skin parts of custom skin packs can require one or more permissions, e.g.
myserver.vip. A player only sees the part in the editor if they have all of them. -
Skin slot permissions give players a different number of skin slots, e.g.
myserver.vip→ 20 skins. See Server Settings.
These permissions don't have to exist in any plugin. Just give them to your players in your permission plugin. The plugin sends the player's permissions when they run /skincreator edit, so after changing a player's permissions they have to run /skincreator edit again.