Deny access from inheriting groups

[JackYack13]

So let's say I have two groups. Group A has fewer permissions than group B, and group B inherits from group A. But let's say that group A has an access that I want to deny form group B. I know this can probably be done by editing the files, but is there any way to do it in the XGUI? If no, then it might be a feature which could be added in one of the next revisions.

[Megiddo]

This existed in previous versions but was removed to make configuration simpler. I suppose it could be added back in without much hassle... I'll think about it.

[JamminR]

If I remember correctly, troubleshooting why a lower group could do something (or not do something) a higher group could often caused more trouble here than not. With the way ULib now allows for individual group specific permissions, which in its own right is/can be reasonably complicated (but awesomely robust!), I think adding inheritance would only complicate it more.

[LuaTenshi]

Well what I would do is just restrict the command so it can only be used on "!*".

Because if

* = Everyone

and

! = not

then

!* = No-one

so in that way the command is disabled for that person because they cant target any one.

(I will try that to see if my theory works. Then  I will come back and post here.)

[Stickly Man!]

If * = Everyone and ! = not, then !* would be Not Everyone (which is different from no-one). Basically it means you can target single or multiple players, but you can't target everyone at once.

[Megiddo]

My mind is blown... and I created the targeting system. X|

I think your idea might actually work, HellFox, though I certainly never intended it to be used that way. I seem to remember a few exceptions programmed into the targeting system. Like I think I might have made it so you can always target yourself, not sure though.

[JackYack13]

Well what I would do is just restrict the command so it can only be used on "!*".

Because if

* = Everyone

and

! = not

then

!* = No-one

so in that way the command is disabled for that person because they cant target any one.

(I will try that to see if my theory works. Then  I will come back and post here.)

If I did that, then the users would still see the commands in the xgui / help and I don't want them to. Also, my problem is not just about commands like kick, jail, ban etc, but also commands without any arguments and other custom permissions I made for my server which are not commands. The reason I need this is for example to create groups that inherit from "admin" (so they can do stuff from other addons which is admin only, for example use the PlayX player) and not be able to use other admin commands (like one of my custom commands "cleardecals").

[Stickly Man!]

You should be able to split the inheritance path. If I am remembering correctly anything that inherits from "admin" will get the privileges from third party mods. So you could set it up such that admin is a dummy group that gains no extra ulx permissions, then have two other groups, say respected and superadmin that both inherit from admin. Both of these groups should be able to use stuff like PlayX, and then you can assign each group their own individual permissions as you see fit.