-
Notifications
You must be signed in to change notification settings - Fork 0
Defining levels
Permission level is used to describe the permissions a player or a command executor has.
In Java Edition some client-side features are hardcoded behind this permission check.
There are permission levels from 0 to 4. Levels are incremental, meaning level n + 1 allows anything level n allows.
| Level | Name | Explanation |
|---|---|---|
| 0 | All | This is what all players have by default. |
| 1 | Moderator | - |
| 2 | Gamemaster | Access to the Game mode switcher, F3+N and Operator Utilities |
| 3 | Admin | - |
| 4 | Owner | - |
See the Minecraft Wiki for more information.
By default, OperatorLevels uses permissions to define the levels. The permissions are in the following format: operatorlevel.level.x.
For example to give a player access to the game mode switcher you'd want to give them the permission operatorlevel.level.2.
Note
You may need to run the /operatorlevel reload command after modifying the permissions for the changes to apply.
OperatorLevel also includes the ability to define operator levels using LuckPerms' meta system instead of permissions. This is more performant than the permission check and is recommended to be used over the permissions.
To use this feature you must enable the luckPermsMeta config option.
# Use LuckPerms' meta system instead of permissions to define levels.
luckPermsMeta: trueImportant
Remember to reload the plugin after changing the configuration.
This is done almost the same way as setting permissions and can be done using both command or the LuckPerms' web editor.
For example the command giving the group admin operator level 4 would look like this:
/lp group admin meta set operatorlevel 4
Or by using the web editor:

Note
You may need to run the /webhooklogger reload command after making changes to the meta for the level to update.
This is especially true when making meta changes to the groups.