LuckPerms

LuckPerms

41.4k Downloads

OP with WorldGuard

Guest1131 opened this issue · 15 comments

commented

Hey,

I found a bug on LuckPerms with WorldGuard.

In the LuckPerms config.yml, I activated the "auto-op: true".
Which allows you to automatically assign OPs to a group or user, which receives permission "luckperms.autoop", and so far everything ok.

In WorldGuard in the config.yml I set "op-permission: false", which also allows who and OP, not to have WorldGuard permissions.

But the bug is not working, if luckperms and on the server, as soon as I removed the plugin luckperms, WorldGuard also blocks OP, if the plugin LuckPerms and on the server, WorldGuard no longer blocks OP.

I contacted the developer of WorldGuard, and he told me that the problem could be in luckperms, which could assign * instead of OP.

How can I fix it?

commented

Going to try to reproduce

commented

I use WorldGuard 7 on spigot 1.13.2, but I do not think this makes the difference.
It is a problem of LuckPerms not of WorldGuard.

Because if I remove the LuckPerms plugin, Worldguard blocks OP, if the option op-permission: false.
If instead of luckperms and on the server, WorldGuard no longer blocks OP.

commented

I think you're getting the WorldGuard op-permission option confused with deop-everyone-on-join and block-in-game-op-command.

The op-permission setting, when set to true, will allow server operators access to WorldGuard even if they don't have the permission for it - when it's false, the system just works as normal with permissions - if they have the perm, they can use the command, otherwise they can't.

If you don't want OPs to be able to use WorldGuard, then yes, set op-permission to false, and ensure they don't have any WorldGuard or wildcard (*) permissions assigned to them.

commented

There's no point in denying permission.

How do I deny WorldGuard.* to the OP?

You can only deny on a group or player, not on OP.

commented

I don't want OPs, has WorldGuard permission, for security reasons

That's fine, but simply setting op-permissions to false won't do that. By default, Bukkit gives operators access to all permissions - which is what's happening here.

How do I deny WorldGuard.* to the OP?
You can only deny on a group or player, not on OP.

Just deny it for all players (the default group)

commented

Yes, but as I have already told you, it only happens if LuckPerms is installed, if no luckperms is not installed, OP and locked by op-permission: false

commented

Ok I see the issue, seems to be related to LP's implementation of the isPermissionSet method.

commented

My testing shows this as being fixed in 4.3.87 - https://luckperms.github.io/

Thanks for reporting the issue, please re-open if it's still not fixed. :)

commented

That's not the problem.

Op-permission: false, only works if I remove luckperms from the server.

So the problem is in luckperms.

And I have not * on worldguard

Can't you fix it?

commented

Try setting worldguard.* to false for your admin users.

commented

I speak of the op, not of groups. I can not add permissions to the OP

commented

It seems that Luckperms, sees OP as *

commented

I don't want OPs, has WorldGuard permission, for security reasons

commented

Then do what Luck suggested and deny worldguard.*

commented

Okay, thank you very much :)