Ulysses
Ulysses Stuff => General Chat & Help and Support => Topic started by: MikeyMatou on January 26, 2017, 07:00:40 AM
-
My ULib/ULX versions:
ULib v2.61
ULX v3.71
Game mode(s) I am having this problem on: DarkRP
Back so soon!
Well, I have an issue to do with admins. It is suggested everywhere that if you want a group to have admin access (so admin weapons, entities, certain addons, etc), make it inherit of admin. However, I am wanting another group to have those rights but not specifically inherit the commands from our admin rank.
I was thinking about trying stuff with IsAdmin and various things. Then I thought couldn't I just manually remove the permission from the groups.txt, but yeah forgot that won't work (well I can't find a way).
If there is anyway (even editing specific files, though I assume for some it's not recommended) to accomplish such?
Any help would be appreciated.
-
You could 'ulx groupdeny' the group of the permission but I'm not sure if it will work as a group that inherits from another group inherits permissions as well.
-
You could 'ulx groupdeny' the group of the permission but I'm not sure if it will work as a group that inherits from another group inherits permissions as well.
Yeah tried using groupdeny, but it only works for permissions that the group had itself, not what it inherited.
-
I did a bad. groupdeny will only remove existing accesses to a specific group, but not remove inherited access. I get confused because you can specifically remove access to a single command at a per-user level using userallow/userdeny, but the same does not apply for groups.
Again, this is a limitation of our inheritance system that we'd like to address in the future. You'll either have to have a branch in your inheritance chain (makes the can_target setup a bit more difficult), or rearrange your permissions/groups such that admin is below the group that has less access, then directly above that can be the group with more access. Hopefully that makes sense, it's a bit difficult to explain lol.
-
I did a bad. groupdeny will only remove existing accesses to a specific group, but not remove inherited access. I get confused because you can specifically remove access to a single command at a per-user level using userallow/userdeny, but the same does not apply for groups.
Again, this is a limitation of our inheritance system that we'd like to address in the future. You'll either have to have a branch in your inheritance chain (makes the can_target setup a bit more difficult), or rearrange your permissions/groups such that admin is below the group that has less access, then directly above that can be the group with more access. Hopefully that makes sense, it's a bit difficult to explain lol.
Is there no way to fix it then? I know editing some stuff in defines.lua and sh_ucl.lua you can get another rank to have IsAdmin, but then admin loses it...
The way you explained I am not entirely sure of.