You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the commands-allow-op config value in LuckPerms is set to false AND the config value auto-op is true AND a player has the permission luckperms.autoop, they can use all LuckPerms commands.
Reproduction Steps
Change the following values according to this in the config.yml
I've taken a look at the source code and figured that the reason this doesn't work is actually because if apply-bukkit-default-permissions is false, the commands-allow-op option is ignored as it is implemented using default permissions.
Some possible solutions are:
Implement an edge case into the OP-Processor that denies LuckPerms permission if commands-allow-op is false
Description
If the
commands-allow-op
config value in LuckPerms is set tofalse
AND the config valueauto-op
istrue
AND a player has the permissionluckperms.autoop
, they can use all LuckPerms commands.Reproduction Steps
Change the following values according to this in the config.yml
Expected Behaviour
A player with just the
luckperms.autoop
permission should not be able to use any LuckPerms commandsServer Details
git-Paper-392 (MC: 1.20.4)
LuckPerms Version
v5.4.130
Logs and Configs
No response
Extra Details
This might be expected behavior, but if so I believe it really shouldn't be.
The text was updated successfully, but these errors were encountered: